Re: Apache Ignite is how to ensure the data's consistency between multiple server？

On Tue, Mar 1, 2016 at 2:34 AM, 上帝已死 <527901...@qq.com> wrote: > PS: Cache mode is Replicated. > > Same documentation that Christos suggested applies to both, partitioned and replicated caches. Also, please take a look at the transaction documentation here:

Re: Date compare fetch in the Query

*Config:* CacheConfiguration cacheConfig = new CacheConfiguration<>(cacheName); cacheConfig.setCacheMode(CacheMode.PARTITIONED); cacheConfig.setMemoryMode(CacheMemoryMode.OFFHEAP_TIERED);

Re: What will happen when one ignite node down and cache mode is Partitioned

I use nginx to do load balancing on serveral tomcat and I hope my server can be horizontal expand.So I have 2 choice : 1. Config cache mode to REPLICATED. 2. Config cache mode to PARTITIONED and backup to >=1. Is that right?Which one is better? -- View this message in context:

Re: Date compare fetch in the Query

Can you provide the full test that you're running? Did you check the logs for exceptions? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Date-compare-fetch-in-the-Query-tp3308p3326.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: What will happen when one ignite node down and cache mode is Partitioned

So it means all node's memory size must bigger than twice of all the cache's data size when backup is 1? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/What-will-happen-when-one-ignite-node-down-and-cache-mode-is-Partitioned-tp3295p3324.html Sent from the

Re: What will happen when one ignite node down and cache mode is Partitioned

So it means All the data size must bigger than twice of all node memory size when backup is 1? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/What-will-happen-when-one-ignite-node-down-and-cache-mode-is-Partitioned-tp3295p3323.html Sent from the Apache Ignite

Re: Date compare fetch in the Query

No Filter is not happening p.getUpdatedDate().before(get1HourBefore()) --- Both are java.util.Date Objects -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Date-compare-fetch-in-the-Query-tp3308p3322.html Sent from the Apache Ignite Users mailing list archive

Re: 答复: How can I only get the local data(Internet mail)

On Mon, Feb 29, 2016 at 5:27 PM, smilehong(洪利平) wrote: > thank you, and you means that use Query.setLocal(true) can achieve this > goal ? > As Denis suggested, using SQL directly is the best option, as the query will be broadcast within the cluster automatically. If you

Re: Version issue with concurrent cache updates (EntryProcessor)

Oh, I see now what you mean, IGNITE-1018 has escaped my view. Then, until IGNITE-1018 is fixed, the only guaranteed approach is to wait on a CDL. Here is the pseudo-code that I have in mind: LifecycleBean or after Ignition.start(): // Populate your node local map CountDownLatch init =

Re: IgniteCache: How to receive Load Re-balance notifications?

Hi Kamal, Can you please elaborate more on your use case? Why do you need to listen to these events and what are you trying to achieve? -Val -- View this message in context:

Re: class org.apache.ignite.binary.BinaryObjectException: Failed to register class.

Hi Dmitry, Can you please properly subscribe to the mailing list so that community receives email notifications? Follow the instruction here: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 Dmitry wrote > . > > Caused by: class

Re: Date compare fetch in the Query

Hi, Can query itself doesn't do any comparisons, it simply calls the filter you provided. Does this happen? Did you verify that the filter is implemented correctly (e.g., that get1HourBefore() returns the correct value for comparison)? -Val -- View this message in context:

Re: Version issue with concurrent cache updates (EntryProcessor)

Myron, What approach did you use initially to initialize the node local map? IgniteNode is considered to be fully functional as soon as Ignition.start() method returns control, so any operations done on NodeLocalMap after the node start should be considered to be run concurrently with

Re: "Failed to send message"

In a considerable manner, because the idea is to resize the cluster dynamically launching new grid nodes in order to steal jobs starving in waiting status. In wondering if it is would be enough to remove this check:

RE: SQL query performance

Hi Shaomin, If you're doing a benchmark, you should run the code that you're going to measure. The warm up happens on JVM level, it's not about Ignite and its caches at all. -Val -- View this message in context:

Re: changed cache configuration and restarted server nodes. Getting exception.

One observation. Everything works fine if i do not add any QueryIndex to QueryEntity. Seems like problem is due to old QueryIndex metadata instance being somehow used by client nodes even though all caches on all nodes were destroyed and all server nodes restarted. vinshar wrote > Hi Vladimir, >

Re: Version issue with concurrent cache updates (EntryProcessor)

Hello Team, Seems like I've found the root cause of such behavior. My EntryProcessor is getting local node resource (actually spring bean). But since resource injection is not supported for EntryProcessor yet (please correct me if I am wrong) I have made a workaround of getting named grid

Date compare fetch in the Query

Hi, I am trying to fetch the records based on the dates: Below is the Query: ScanQuery dataScanQuery = new ScanQuery((k, p) -> p.getUpdatedDate().before(get1HourBefore())); [JavaObject] - has Date field, i am trying to fetch the records using date

Re: changed cache configuration and restarted server nodes. Getting exception.

Hi Vladimir, I am able to reproduce problem and it's not intermittent. Exception occurs everytime. I am attaching class with main method which replicates the issue ans also attaching logs. IgniteProblemTest.java

ignite cache-api licensing issue

As apache-ignite implements JCache API JSR-107 it depends on cache-api-1.0.0.jar. However, JCache API is licensed under a “Specification License” https://github.com/jsr107/jsr107spec/blob/master/LICENSE.txt which pretty much invalidates any open source licensing of implementation providers.

Re: IgniteCache: How to receive Load Re-balance notifications?

Pavel, I'd like to receive notifications when a node left / joined the cluster. Gone through discovery notifications. But, In my application it would be more appropriate to receive notification after re-balance / a backup partition in a node becomes primary. On Tue, Mar 1, 2016 at 9:36 PM,

Re: What will happen when one ignite node down and cache mode is Partitioned

You can access the data as primary node is up. When cache mode is set to partitioned, each node acts as primary node for some partitions and as backup node for other partitions. Refer https://apacheignite.readme.io/docs/cache-modes#partitioned-mode On Tue, Mar 1, 2016 at 8:26 PM, 上帝已死

Re: IgniteCache: How to receive Load Re-balance notifications?

Vladimir, I had included the re-balance event types in *example-default.xml. *I'm able to receive REBALANCE notifications when cache mode is set to partitioned. Does re-balancing won't trigger when cache mode is replicated ? -- Kamal On 29-Feb-2016 7:07 PM, "Vladimir Ozerov"

Re: What will happen when one ignite node down and cache mode is Partitioned

If I have 2 nodes and backup is 1，what will happen when the backup node is down？ -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/What-will-happen-when-one-ignite-node-down-and-cache-mode-is-Partitioned-tp3295p3301.html Sent from the Apache Ignite Users mailing

Re: What will happen when one ignite node down and cache mode is Partitioned

Do not be a part of the cache cannot be obtained? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/What-will-happen-when-one-ignite-node-down-and-cache-mode-is-Partitioned-tp3295p3299.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: What will happen when one ignite node down and cache mode is Partitioned

Ignite will re-balance data between remaining nodes. On Tue, Mar 1, 2016 at 2:03 PM, 上帝已死 <527901...@qq.com> wrote: > What will happen when one ignite node down and cache mode is Partitioned > > > > -- > View this message in context: >

RE: SQL query performance

Thank you very much Val. In terms of the warning up, do I need to warm up every cache, or warning up on one cache will produce 0ms on all caches? Shaomin -Original Message- From: vkulichenko [mailto:valentin.kuliche...@gmail.com] Sent: 26 February 2016 18:56 To: user@ignite.apache.org

What will happen when one ignite node down and cache mode is Partitioned

What will happen when one ignite node down and cache mode is Partitioned -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/What-will-happen-when-one-ignite-node-down-and-cache-mode-is-Partitioned-tp3295.html Sent from the Apache Ignite Users mailing list archive

Re: Apache Ignite is how to ensure the data's consistency between multiple server？

PS: Cache mode is Replicated. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-is-how-to-ensure-the-data-s-consistency-between-multiple-server-tp3288p3294.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Apache Ignite is how to ensure the data's consistency between multiple server？

If you use full sync mode for backups, then the client node will wait for write or commit to complete on all participating remote nodes (primary and backup). This is the most restrictive configuration but will guarantee data consistency. In addition if you use transactions for any grid

Re: Apache Ignite is how to ensure the data's consistency between multiple server？

How does Apache Ignite ensure the data between multiple server is consistency in anytime? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-is-how-to-ensure-the-data-s-consistency-between-multiple-server-tp3288p3291.html Sent from the Apache Ignite

Re: "Failed to send message"

Hi Valentin, I've checked and it is not a client node because the GridDiscoveryManager reports in the log "servers=2, clients=0" and I've launched only two instances. Also, as cluster group I'm using the default one i.e. tasks are executed with Ignite#compute() method. I'm starting to think

Apache Ignite is how to ensure the data's consistency between multiple server？

Apache Ignite is how to ensure the data's consistency between multiple server？Especially, in the case of high concurrency. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-is-how-to-ensure-the-data-s-consistency-between-multiple-server-tp3288.html