Re: Enable Native persistence only for one node of the cluster

service is hosted. Let me know if this makes sense or if you see any red flags. Thanks, Krish -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Enable Native persistence only for one node of the cluster

Is it possible to have a cluster topology where native persistence is enabled only for one node and all other nodes use in-memory cache store *without *native persistence? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Execute Ignite Jobs with semaphore

aphore = this.ignite.semaphore( "123" , 1 , true, > true); > boolean acquired = semaphore.tryAquire(); > if (acquired) { >  // run logic >semaphore.release(); > } > } Thanks, Krish -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Execute Ignite Jobs with semaphore

t will push the task to the end of the queue and pick up the next job. What do you think about this approach? Thanks, Krish -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Execute Ignite Callable Jobs with set priorities

ilya.kasnacheev wrote > This means that Ignite prioritizing is a poor fit for you and you may need > to roll out your own, perhaps based on IgniteQueue. Does ignite provide priority queue implementation of IgniteQueue interface? Thanks, Krish -- Sent from: http://apache-ignite-users.70

Re: Execute Ignite Callable Jobs with set priorities

Thanks Stephen and Ilya, As mentioned in job scheduling documentation, collisionAPI will take care of job scheduling when jobs arrive at destination node. Lets say I use PriorityQueueCollisionSpi and send three jobs with priorities 5, 7 and 10 to one node, then that node will execute job with