Arun,

1. First option - you'll get something like this

Method threw 'org.apache.ignite.IgniteException' exception: Can not perform the operation because the cluster is inactive. Note, that the cluster is considered inactive by default if Ignite Persistent Store is used to let all the nodes join the cluster. To activate the cluster call Ignite.active(true).
2. active(false) is synchronous. You can consider that the cluster is deactivated when ignite.cluster().active(false) call returned. 3. Every node in cluster has unique consistent ID. It should remain unchanged after node restart. By default, it's generated automatically from something like host:port, but you can override it via IgniteConfiguration#setConsistentId. This is necessary because {$IGNITE_HOME}\work\db and {$IGNITE_HOME}\work\db\wal has subfolders with names of consistent IDs ever started locally. If you change consistent ID, old Ignite Native Persistence files won't be found and node will start from scratch.

Best Regards,
Ivan Rakov

On 19.02.2018 15:22, arunkjn wrote:
Hi Ivan,

Thanks for you reply.

I have some follow up questions.
1. What is the behaviour of cluster when it is in
ignite.cluster.active(false) state? Does it throw error when a cache seek
operation is performed? Or does it wait for cluster to become active again?
2. How can I reliably know if cluster has become inactive before taking
backup? Is cluster.active(false) a synchronous operation?
3. What do you mean by "consistent ID of your nodes"? Can you please
elaborate?

Thanks,
Arun



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Reply via email to