ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bintisepaha <binti.sep...@tudor.com>
Subject Re: System.exit() not exiting cleanly (locked on IgnitionEx$IgniteNamedInstance)
Date Tue, 28 Jun 2016 16:09:19 GMT
Denis, is it ok to delete this file while the cluster is up? or this folder?
servers and clietns might be connected to it.

I posted another question for the community trying to understand the use of
the work directory. Could you please respond to that?

This lock.file has not been updated since Apr 13, the first time we used
ignite in production. the size of the file is 0 KB.

Also it is hard for us to understand why this started happening after 3
months, we were running smoothly until now. and now System.exit() or
Ignite.stop() both don't work randomly. For 2 days we were good, by passing
-DIGNITE_NO_SHUTDOWN_HOOK=true, now even that is not a reliable solution.
Its does not work each time.

is System.exit() or Ignite.stop(grid, false) not a good solution? Should we
be using Ignite.close()? or Ignite.stop(grid, true) to kill all the current
running jobs.


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/System-exit-not-exiting-cleanly-locked-on-IgnitionEx-IgniteNamedInstance-tp5814p5967.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message