Hi Binti, No, we were unable to resolve it. We were also experiencing quite frequently from another known issue "IllegalStateException: Cache has been closed or destroyed: cache" so we decided to move on and drop Ignite altogether. We finished the transition in production a couple of weeks ago. I'm sorry I can't be of much help, D.
2016-08-20 1:31 GMT+02:00 bintisepaha [via Apache Ignite Users] < [email protected]>: > Hi, we are seeing similar issues too with ignite 1.5.0. Were you guys able > to resolve it? we use distributed caches in full-sync mode and also a few > replicated caches. > > Thanks, > Binti > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-users.70518.x6.nabble.com/One- > failing-node-stalling-the-whole-cluster-tp5372p7183.html > To unsubscribe from One failing node stalling the whole cluster, click > here > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5372&code=ZC5sb3Blei5qQGdtYWlsLmNvbXw1MzcyfDIwNTkzNjQ3OTE=> > . > NAML > <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/One-failing-node-stalling-the-whole-cluster-tp5372p7188.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
