Re: Version issue with concurrent cache updates (EntryProcessor)

Myron, This is a known usability issue, see [1]. You need to set atomicWriterOrderMode to PRIMARY in order to make entry processors to work correctly. I will cross-post this mail to devlist in order to raise the ticket priority. [1] https://issues.apache.org/jira/browse/IGNITE-2088 --AG

Re: Cache entries getting cleared

Hi Moiz, This happens due to several reasons: - you're using peer-class-loading feature [1] that allows to load a class definition from remote nodes if a class is missed locally. - in your case a remote node loads Model class from the node that created TEST cache and has its class locally; -

Re: SQL query result variation

Hi Syed, I'm not sure I understand you data model, but the problem here is that Ignite supports distributive aggregate functions in SQL only at the top level query. I mean *sum(bal)* will work correctly always, but *min(balance) *will run on each node separately (in general all the sub-queries

Re: SQL query result variation

Thanks Sergi, The model provided in the example is just a simplified version of our production model which I am evaluating on ignite. One of our production query is a two-level query as in the example. I have two follow-up questions then: 1. Most of our queries are two level nested and the outer

Re: Version issue with concurrent cache updates (EntryProcessor)

Hmm, doing the same but with: atomicWriteOrderMode=PRIMARY writeSynchronizationMode=PRIMARY_SYNC causes: [atomic.GridDhtAtomicCache] - Unexpected exception during cache update java.lang.AssertionError: Invalid version for inner update [entry=GridDhtAtomicCacheEntry [super=GridDhtCacheEntry

Re: SQL query result variation

1. SQL in partitioned cache works the following way: Ignite splits top level query into 2 separate queries - one for "map" phase and another one for "reduce". All the "map" queries are executed on all the data nodes, the results are combined together on the node which initiated the query and those

Re: New Apache Ignite Server on-demand

Thanks Val, You answered my question :) -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/New-Apache-Ignite-Server-on-demand-tp2887p2911.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cache entries getting cleared

I've not noted that the cache was cleared when some of the server nodes left the topology. Was the cache data inserted from all the nodes or from specific nodes only (including the crashed one)? -- Denis On 2/9/2016 6:32 PM, Syed Moizuddin wrote: Thanks Denis, I will refer the docs. I had

Re: SQL query result variation

Thanks Sergi. I somehow had this intuition and started with the affinity-collocation earlier and got into some issues. Could you please review this question of mine (posted earlier) in the current