Re: 回复：how does Ignite Client restart ContinuousQuery when Ignite cluster failed and restart

Try using Near cache , looks like it perfectly fits what are you have described, you may even use your expiry policy form distributed cache to be in sync. For restarting client refer to documentation: Reconnecting a client

回复：how does Ignite Client restart ContinuousQuery when Ignite cluster failed and restart

- 发件人：akurbanov 发送时间：2018年9月6日(星期四) 20:45 收件人：user 主　题：Re: how does Ignite Client restart ContinuousQuery when Ignite cluster failed and restart Hello, Can you clarify what is "local cache" in your use-case? What are you using as a client for Ignite? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: how does Ignite Client restart ContinuousQuery when Ignite cluster failed and restart

Hello, Can you clarify what is "local cache" in your use-case? What are you using as a client for Ignite? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

how does Ignite Client restart ContinuousQuery when Ignite cluster failed and restart

I have 2 ignite cluster nodes on 2 AWS servers,both starting as server model.In my client,I use ContinuousQuery to listen to the Ignite events that i config and update my local cache data when event happens. I meet a problem when using this way to synchronize my local cache with ignite clust