Re: Performance issue on Ignite ODBC API

Hi Igor, Thanks for the detailed information. As suggested, Will check our configuration and code. With regards, Agneeswaran -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Performance-issue-on-Ignite-ODBC-API-tp5908p6007.html Sent from the Apache Ignite Users

Re: IgniteCache remove cache data, repeated calls to the'deleteAll'CacheStore method many times, which is the reason?

Hi, Please see my answer in this discussion http://apache-ignite-users.70518.x6.nabble.com/Put-IgniteCache-data-call-CacheStore-persistent-method-of-confusion-tp5984.html

Re: Web Console Beta 2 release

Just checked it out, looks awesome! Very nice and easy way to configure, manage, and query Ignite clusters. On Tue, Jun 28, 2016 at 1:41 AM, Alexey Kuznetsov wrote: > Igniters! > > I'd like to announce that we just pushed Ignite Web Console Beta 2 to > master branch and deployed new version at h

IgniteCache remove cache data, repeated calls to the'deleteAll'CacheStore method many times, which is the reason?

When the'remove'/'removeAll'method is called, the IgniteCahce method is called. alled multiple times, what is the reason? config: Execution process:

Re: Performance issue on Ignite ODBC API

Agneeswaran, I have tested and profiled ODBC using data from odbc-example and I can see that 1 million rows, 3 string columns each retrieved by ODBC in ~8 seconds on first run, and in less than ~5 seconds on second run. Actually, ODBC driver always retrieving data by pages of size 1024 rows so it

Re: How I can be sure that Near cache works and configured properly

We are talking about near cache on client nodes? or both server and clients? I think we could add smth. to visor cmd to collect info about near caches. I will think a little and post my thoughts here a bit later. On Wed, Jun 29, 2016 at 9:21 PM, Denis Magda wrote: > Hi, > > Presently you can use

Re: How I can be sure that Near cache works and configured properly

Hi, Presently you can use CacheConfiguration.getNearCacheConfiguration() to see whether a near cache is configured on the node. There is no any stats that is available over Mbeans or visor cmd. Alexey Kuznetsov, Igniters, do we have any plans on this? Probably there is already a feature request

Re: Performance issue on Ignite ODBC API

Agneeswaran, Let me have a look. I will profile the code and will tell you results. Best Regards, Igor On Wed, Jun 29, 2016 at 4:48 PM, Agneeswaran < agneeswaran.ponnuraman...@nielsen.com> wrote: > Hi Igor, > > Using Java API we can fetch the data within ~5 seconds but in C++ it took > ~4 > min

Re: Ignite work directory usage?

I would also add that if you start several nodes on the same physical machine then the nodes will use the same working directory by default. However, to my knowledge, this doesn’t lead to any conflicts or issues. — Denis > On Jun 29, 2016, at 3:16 PM, Alexei Scherbakov > wrote: > > Hi, > >

Re: Performance issue on Ignite ODBC API

Hi Igor, Using Java API we can fetch the data within ~5 seconds but in C++ it took ~4 minutes. Will it possible to fetch the data, let say 500-1000 records at once. Could you please suggest us. Thanks, Agneeswaran -- View this message in context: http://apache-ignite-users.70518.x6.nabble.

Re: log4j on server node (log no print)

You should enable Log4j2 logger on both client and server side by adding the following to the nodes’ configurations ... ... Path to log4j2 config may vary. After that you need to use @LoggerResource annotation inside of your task to avoid seria

Re: System.exit() not exiting cleanly (locked on IgnitionEx$IgniteNamedInstance)

Thanks for your response. We are disabling shmem this weekend in production as per your advice. Will let you know how that helps next week. The issue started happening after 3 months of smooth running, so we were curious to understand how it became a problem suddenly. -- View this message in c

Re: Put IgniteCache data call CacheStore persistent method of confusion

Hi, Seems that you’re using the write-behind mode. Such behavior is not reproduced in the write-through mode on my side. Is it so? In the write-behind mode updates are propagated a bit later to the store and they are propagated in batches which leads to the usage of ‘writeAll’ rather then ‘wri

Re: Creating cache with CacheLoaderFactory on client node brings exception org.apache.ignite.IgniteCheckedException: Failed to find class with given class loader for unmarshalling (make sure same vers

Thank you very mach!Everything works well. On Jun 29, 2016 5:29 PM, "Denis Magda" wrote: > Hi, > > How do you start a remote node? Do you use ignite.sh or ignite.bat script > that is delivered in Apache Ignite release bundle? > > If so in the release bundle you will see “lib” folder where you can

Re: Ignite start-up connection timeout?

Hi, Seems that multicast doesn’t work on your side and you just need to use TcpDiscoveryVmIpFinder listing IP addresses of all the nodes that will form the cluster. Refer to this documentation [1] for more info. As I see from this log the node has started and ready for the usage. Change your l

Re: Continuous Query

Hi Alex, All the local listeners that satisfy remote filters’ conditions will be notified. However there is one to one relationship between remote filter and local listener meaning that if you have 4 CQs then 4 remote filters will be executed and 4 local listeners notified if needed. What happ

Re: Creating cache with CacheLoaderFactory on client node brings exception org.apache.ignite.IgniteCheckedException: Failed to find class with given class loader for unmarshalling (make sure same ver

Hi, How do you start a remote node? Do you use ignite.sh or ignite.bat script that is delivered in Apache Ignite release bundle? If so in the release bundle you will see “lib” folder where you can put you jars and ignite.sh/bat will add to to the class path automatically. Alternatively you can

Re: System.exit() not exiting cleanly (locked on IgnitionEx$IgniteNamedInstance)

Binti, please see the answers below > Denis, is it ok to delete this file while the cluster is up? or this folder? > servers and clietns might be connected to it. Delete the whole folder after the cluster is down. > is System.exit() or Ignite.stop(grid, false) not a good solution? Should we > be

Re: Ignite work directory usage?

Hi, Ignite uses work directory as a relative directory for internal write activities, on example, logging. Every Ignite node (server or client) has it's own work directory independently of other nodes. Generally you should not change it without reasons. Was it helpful ? Maybe you got more spec

log4j on server node (log no print)

Here is my configuration client node 1: IgniteBean 2: log4j2 dependency on the client node

Re: Non-cluster mode

Hi Val, I've pushed a demo to https://github.com/ps4os/ignite_offheap_test The issue is that I can't reproduce it consistently. As soon as I get the OutOfMemoryError, I can reproduce it. And I can reproduce it with a restart in between. The demo contains a Readme as well as some TODOs and comments

Re: Re: argument type mismatch of oracle TIMESTAMP field when call loadCache

Hello Bob. We create issue to fix that problem. You can watch it on page: https://issues.apache.org/jira/browse/IGNITE-3394 On Wed, Jun 29, 2016 at 7:34 AM, 胡永亮/Bob wrote: > sorry, the infomation is not in detail. > > My ignite's version is new release version: 1.6. > > ---