client reconnect working?

Hi, We have a bunch of ignite nodes in the client mode (NOT the thin clients), that are connected to a 2 node ignite cluster. These clients stay connected indefinitely unless there is a failure of some sort. So every once in a while, sometime a few hours or even days, the client loses the conn

Re: cache <- Db [ raised exception...]

- it's working - but i m going to search if i can define multiple cacheSession With != source cache 1 Link to DB 1 cache 2 link To DB 2 Cheers -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: cache <- Db [ raised exception...]

new exception = new re-search : vHibernate: select definition0_.code as code1_0_0_, definition0_.currency as currency2_0_0_, definition0_.eliot_id as eliot_id3_0_0_, definition0_.eliot_type as eliot_ty4_0_0_ from DEFINITION definition0_ where definition0_.code=? [22:30:57,459][SEVERE][sys-#101][Gri

Re: Cache misses with complex cache keys that have fields not relevant for hashCode/equals

Hello! I don't think there is a better solution. Ignite uses binary representation of key to build its B+ tree. If some non-transient field is different then it is a different key, even if it is not used in hashCode. Regards, -- Ilya Kasnacheev пт, 21 июн. 2019 г. в 14:48, Axel Faust : > Mayb

Canceling a running query on ignite

Hello All, When we run a complex SQL query on ignite cluster from a client, not clear on what is expected? Does it run forever or can we specify a timeout? Is there a way it can be canceled so that it does not bring the server down? Thanks

Re: cache <- Db [ raised exception...]

I change strategy by setting cacheStoreSessionListener to my ignit config => ignite cluster sta

Re: Ignite Visor Cache command hangs indefinitely.

How to turn it off? Also i think i know what may have been the visor issue. I was connecting to cluster not specifying ports 47500..47509. But once I added that it seems more stable. I can even see the wifi node and everything. On Fri, 21 Jun 2019 at 06:01, Ilya Kasnacheev wrote: > Hello! > >

cache <- Db [ raised exception...]

Hello, i try to load data from my dB into my cache : config sample : __ ...

Unsubscribe

Please Unsubscribe me. Regards, Nick Kalbali

Re: Cache misses with complex cache keys that have fields not relevant for hashCode/equals

Maybe the term "complex" is a bit misleading. I used it to differentiate the kind of composite key used from the trivial, e.g. String/Long keys that might be used for simple entity lookups. In my immediate case, the key is a small immutable object with two hash relevant fields + one non-hash releva

Re: Cache misses with complex cache keys that have fields not relevant for hashCode/equals

Hello! Usually it is not wise to have large complex keys, especially ones that you do not control. Can cause all sorts of issues. You can declare your key Externalizable, though, and have control over its marshalling. That, or Binarylizable. Then you get to decide how everything is processed. R

Re: Apache Ignite 2.7.5 requirements for AWS

There’s no one-size-fits-all answer unfortunately. How much data do you have? Do you use a lot of SQL? A lot of compute? What are your resilience requirements? For an “average” deployment I’d start looking at the “Memory optimised” instances (r5 and r5a). Of course, no one has an average deploy

Re: Ignite Visor Cache command hangs indefinitely.

Hello! It is recommended to turn off failure detection since its default config is not very convenient. Maybe it is also fixed in 2.7.5. This just means some operation took longer than expected and Ignite panicked. Regards, чт, 20 июн. 2019 г., 19:28 John Smith : > Actually this hapenned when

Re: Can we avoid the PME when restarts a node in cluster.

Hello! 2.7.5 definitely did not include it and there is no set date for 2.8. Regards, пт, 21 июн. 2019 г., 6:50 Justin Ji : > 2.7.5 may not include the feature~ > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: Sudden cluster failure

Hello! Does it eventually recover? Right now it seems like network issues, such as having idle connections closed. Regards, пт, 21 июн. 2019 г., 10:54 Nikita Kuzin : > Hi. > > We updated Ignite to 2.7.0 > > And still having same issue: > > > [01:05:14,454][INFO][grid-timeout-worker-#55%ITLXCLKA

Apache Ignite 2.7.5 requirements for AWS

Hi All, Does anyone have recent experience of deploying Apache Ignite on AWS EC2 instance cluster? There is much variance in the AWS EC2 instance types in terms of number of CPUs (therefore performance), memory availability and network bandwidth. Ultimately costs would increase with the higher spe

Re: Sudden cluster failure

Hi. We updated Ignite to 2.7.0 And still having same issue: [01:05:14,454][INFO][grid-timeout-worker-#55%ITLXCLKAPR-server09f69d67-ce6e-4d42-a41f-70e3d1a86382%][IgniteKernal%ITLXCLKAPR-server09f69d67-ce6e-4d42-a41f-70e3d1a86382] FreeList [name=ITLXCLKAPR-server09f69d67-ce6e-4d42-a41f-70e3d1a863