RE: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Hi Michael, Thanks for the reminder. I was (or thought I was) actually doing this in an ancestral constructor of my class, but the pattern I was using at the time used a c# static method so the constructor was never hit and the client server was never started Once I modified it to use the

Re: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Hi Raymon, Activator should start an ignite node, which will connect to the server node, but this node should be client node. Instead of IIgnite ignite = Ignition.TryGetIgnite(“MyGrid”); use: Ignition.ClientMode = true; IIgnite ignite = Ignition.Start(config); Then you can activate cluster.

RE: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Hi Michael, I wrote a simple application to act as an activator for a grid. As this is just a POC, it’s simply a form with a button on it that does this: // Get an ignite reference to the named grid IIgnite ignite = Ignition.TryGetIgnite(“MyGrid”);

RE: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Sorry, adding a question: 4. This raises a more general coordinate question: You can’t create or locate a cache in the grid until the grid is active (when using Ignite persistence). Which means you need to stall any logic in the server nodes that wants to do this until the grid is marked as

RE: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Hi Michael, Some more questions: 1. Can I set the grid active once all primaries are active, but before all backups are active? Or do I need to have the entire cluster running before setting active to true? 2. Is there an assumption that the cluster size is static and known at

Re: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Hi again, Checkout the email on dev list: "Cluster auto activation design proposal" https://issues.apache.org/jira/browse/IGNITE-5851 As you can see this feature is targeted to 2.2. Thanks, Mikhail. 2017-08-03 6:58 GMT+03:00 Raymond Wilson : > Michael, > > > > Is

Re: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Hi Raymond, Unfortunately right now there's no auto-activation, restarting cluster is like rare event that should be controlled manually. However you can listen for EVT_NODE_JOINED event, when all nodes in place you can activate a cluster. And you only need this if you have ignite persistence

RE: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Michael, Is there a reference implementation in Ignite 2.1 for an agent that listens to topology changes to decide when to set active to true? Thanks, Raymond. *From:* Michael Cherkasov [mailto:michael.cherka...@gmail.com] *Sent:* Thursday, August 3, 2017 1:25 AM *To:*

Re: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

>Does this mean we have to listen to events of server nodes going up and down and activate and deactivate the cluster? No, you need to deactivate cluster when you going to shutdown the whole cluster. And when you return cluster back to online, you need to wait when all nodes are in place and

Re: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Does this mean we have to listen to events of server nodes going up and down and activate and deactivate the cluster? On Wed, Aug 2, 2017 at 3:18 PM, Michael Cherkasov < michael.cherka...@gmail.com> wrote: > when all nodes are up, so in latest topology snapshot you can see servers > count ==

Re: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

when all nodes are up, so in latest topology snapshot you can see servers count == servers count you run, then cluster can be activated. 2017-08-02 0:51 GMT+03:00 Raymond Wilson : > Hi Mikhail, > > > > Thanks for the clarifications. > > > > Yes, I knew setting active

RE: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Hi Mikhail, Thanks for the clarifications. Yes, I knew setting active was only required when using the persistence layer, which is the topic of the question J I was interested if there were best practices or approaches for determining when the grid had fully initialized. I realise this is

Re: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Hi Raymond, Ignite cluster is inactive on startup only if persistence is enabled. This is done to avoid unnecessary partition exchanges between nodes, for example, if you have 3 nodes and 1 backup enabled and you start only 2 of 3 nodes, then they will treat the third node as dead and start

Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

Hi, I am experimenting with a POC looking into using the Ignite persistence layer. One aspect of this is setting the grid to be ‘Active’ after all cache grid nodes have instantiated. In practical terms, what is the best practice for ensuring the cluster is running and in a good state to