Re: Register Contentious query quit slow

1. *For Ignite cluster initialization, here is the log * [2017-11-22T08:01:56,975][INFO ][main][IgniteKernal] Non-loopback local IPs: 10.41.91.200 [2017-11-22T08:01:56,975][INFO ][main][IgniteKernal] Enabled local MACs: 286ED488CFC0 [2017-11-22T08:03:36,496][INFO

Transport compression (not store compression)

Hi Igniters, I see there is a lot of discussion in certain threads about compression. This seems to have diverged into conversations about object versus field compression, and even throwing encryption into the mix. For my use case, I am not interested in compressing the cache stored in memory,

Unable to read all the entries in present single cache using Streamer

Hi, I am using following code to read all the entries of a cache in map using below code. IgniteCache cache = cache(cacheName, false); Map map1 = new HashMap<>(); cache.forEach(action ->map1.put(action.getKey(), action.getValue()));

Cache size changes unexpectedly

Hi, We have a cluster of 4 nodes. On start of the cluster we load our caches. In of our cache we are load around 2 million entries. We also monitor cache size at regular interval. The behavior we are noticing is that after initial load the cache size seems to be correct for few mins. But then

Re: Spring Integration

Hi, I finally found the solution to this puzzle. By setting the class loader to the configuration after I initialize Ignite to that of the Spring Service, it solves the issue. I simply had to add the following line: ignite.configuration().setClassLoader(MySpringService.class.getClassLoader())

Re: Failed to start near cache (a cache with the same name without near cache is already started

Hi, Near caches are transparent for you - there is no user API to get reference to or work with near caches. The purpose of a near cache is to "cache the cache", that is to be a local cache for a distributed cache. Ignite transparently fills near cache with the most recent data when you work with

Spring Integration

Hi, I am trying to use ignite with a spring boot application. Yet, when invoking an Ignite Service, it is materialized in the process with a different class loader than the one that was used to create the beans and the integration is therefore impossible. Has anyone seen this issue? Is

Re: Local node failure starts cluster-wide procedure

Hi Val, Thanks for the response. I am trying to figure out the reason why the node was not able to restart when the logs suggest it is attempting. I looked for the 'Restarting JVM...' log in the Ignite code and found it in GridDiscoveryManager$DiscoveryWorker class (pasted below). As per the

Re: Replicated In-memory synchronized cache with Oracle SE

Hello, Yes, in case of your Oracle database is updated by other applications directly, you need to propagate these updates into Ignite cluster on your own somehow. Apache Ignite doesn't provide that functionality out of the box. However, it can be easily implemented. Please check this article:

Re: spark lookup against shared RDD

Any response on the below questions for using index on spark shared rdd will be really appreciated. Thank you. On Tue, Nov 21, 2017 at 4:45 AM, roshan joe wrote: > Below is the use-case I am trying to solve using Spark shared Rdd: > > I have a json dataset which is

Re: Failed to start near cache (a cache with the same name without near cache is already started

Hi Alex, Thank you for your reply. But I am not quite clear about how to create near cache for TableA and TableB? Thanks, Sherry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Error running ignite in YARN

Hi, Anyone might help a newbie ramping up with Ignite on YARN? Thanks, Juan On Sun, Nov 19, 2017 at 7:34 PM, Juan Rodríguez Hortalá < juan.rodriguez.hort...@gmail.com> wrote: > Hi, > > I'm trying to run ignite on AWS EMR as a YARN application, using zookeeper > for node discovery. I have

Re: Failed to start near cache (a cache with the same name without near cache is already started

Hi, Near caches are configured per cache and not per query. You cannot start different near caches for the same distributed cache. Start separate near caches for TableA and TableB.

Re: Register Contentious query quit slow

Does initialization finish fast, when you start just two nodes in a single DC without the third one? Bad network can significantly affect performance and stability of the whole cluster. So, it's not recommended to have nodes, that are geographically separated from each other, or have a poor

WAL size control

Hello all, I’m having an issue understanding how to control/limit the size of the WAL as well as why I’m consuming so much WAL space. I’m currently migrating a project from redis to ignite and as part of the first phase, its pretty much lift and shift without optimizing for ignite. In this

Failed to start near cache (a cache with the same name without near cache is already started

Hi there, I have an issue with near cache. I deploy an ignite cluster on server side and run a ignite client in my local. I would like to use NearCache for my local client. Lets say, I have 4 Near cache configuration which corresponding to 4 cache "CacheA", "CacheB", "CacheC",and "CacheD". And

Re: Issues with multiple kafka connectors, questions regarding ignite caches

Hi, 1. IgniteSinkTask source code shows that Ignite Kafka Connector has this "feature" that stopping any task

Re: Register Contentious query quit slow

Re: SqlQuery with Cassandra cache

I was starting to think that was the case. Thanks for the help and verifying that for me, Val. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ODBC insert of decimal value throws an exception

Looks like a bug. Can you provide code how you feel the parameter value so I can reproduce it? Best Regards, Igor On Tue, Nov 21, 2017 at 3:50 PM, Kenn Thompson wrote: > You bet, thanks for looking. > > > > [06:48:40] Topology snapshot [ver=1, servers=1, clients=0,

RE: ODBC insert of decimal value throws an exception

You bet, thanks for looking. [06:48:40] Topology snapshot [ver=1, servers=1, clients=0, CPUs=8, heap=1.0GB] [06:49:18,662][SEVERE][client-connector-#52][ClientListenerNioListener] Failed to parse client request. java.lang.ArrayIndexOutOfBoundsException: 0 at

Re: Node unable to join cluster

Hi Josephine! Make sure, that TcpDiscoveryVmIpFinder has address of the local node on the list. Otherwise the first node won't be able to start, because discovery SPI won't find any nodes. Also note, that TcpDiscoverySpi has localAddress and localPort properties. Try setting them according to

spark lookup against shared RDD

Below is the use-case I am trying to solve using Spark shared Rdd: I have a json dataset which is periodically being saved to a shared RDD in Streaming App-1 using "saveValues" as below. val sharedRdd: IgniteRDD[String, String] = igniteContext.fromCache[String, String](cachecfg)

Re: Register Contentious query quit slow

Hi! It's hard to tell, what causes such long startup time. What do logs say? Try enabling debug log and watching, what nodes are doing all that time. Please let me know if you find something. I don't think, that peer class loading causes it, because it only works for compute jobs and a few more

Re: affinityRun and affinityCall trace

Thanks Val. I thought so but worth giving it a shot :) Luqman -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Node unable to join cluster

Hi, I have setup ignite instances on two different VMs and I'm trying to create a cluster using Static IP discovery using TcpDiscoveryVmIpFinder. I have a couple of questions: 1. Do I need to give loopback address or public IP for the node to start before trying to connect to the other node

Re: Register Contentious query quit slow

BTW, the deployment mode I use is PRIVATE, does it matter? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Register Contentious query quit slow

Hi there, I have write an app with contentious query feature and pack as a single jar, as depend on some 3rd party lib so it's quite big, 40M. For local cluster, the app start quit fast and can be startup within 20 secs. But after add one more cross region node, this app need around 10 mins to

Re: Initial query resent the data when client got reconnect

Mike, double checked Mongodb way, their ObjectID only provide a unique ID, sorry for my info. But there is open source project provide the auto increment feature for mongodb. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ComputeTask is including Nodes for ComputeJobs prematurely

Chris, If it's exactly the thing that you want to achieve, you can start Ignite twice. First time - to get contents of the "admin cache", and second time, after all initialization is finished - to accept compute jobs. To avoid compute jobs from being executed by the first node, you can run them

Re: ODBC insert of decimal value throws an exception

Hi, can you provide full stack trace for the error? Best Regards, Igor On Tue, Nov 21, 2017 at 12:41 AM, kenn_thomp...@qat.com < kenn_thomp...@qat.com> wrote: > I have a table defined as such and created via passing to an ODBC > Connection: > > CREATE TABLE IF NOT EXISTS TestTable (RecId