Re: Exception when Ignite server starts up and also when a new node joins the cluster

Hi Agura. You can try with this configuration <http://apache-ignite-users.70518.x6.nabble.com/file/n13797/ignite-config.xml> but it is with out write behind I have been using jdk7 (build 1.7.0_45-b18) on Red Hat Linux 7.3. Regards Jaipal -- View this message in context: http://

Exception when Ignite server starts up and also when a new node joins the cluster

I am getting the following exception when starting Ignite in server mode(2.0) and from then Ignite is stopping all the caches. Exception in thread "main" class org.apache.ignite.IgniteException: Attempted to release write lock while not holding it [lock=7eff50271580, state=0002 2639

Re: Failed to wait for initial partition map exchange

Val, It doesn't look like a memory issue.We are using explicit locking (lock entry , do processing and then unlock).Under high load, When we bring down one of the Ignite Server nodes and then again add it back to the cluster,We are getting this issue.We observed the exceptions like Failed to wait

Re: Failed to wait for initial partition map exchange

Hii val, I tried recommended settings and configurations. still I observe this issue and it can be reproduced easily. Is there any fix available to this issue. Regards Jai -- View this message in context:

Re: Failed to wait for initial partition map exchange

We are facing the similar issue with 1.9 version..Is there any recommended configuration parametres to overccome this issue -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tp6252p12028.html Sent from the Apache

Apache Ignite WriteBehind Guarantee during a Graceful Shutdown

Listeners or shutdown hooks etc..). Regards, Jaipal