Hello, Return type of methods (setDataExchange and setMetricsProvider) look strange, I recomment ask the question in Ignite developer list. May be this interface requires review.
If you need to stop or any other activity from server nodes from client instance, you always can send task to it. Any distributed closure can be executed on remote node [1] (for example, System.exit(), or safer decision with local Ignite Ignition.localIgnite() and others). [1]: https://apacheignite.readme.io/docs/distributed-closures On Wed, Aug 24, 2016 at 12:09 AM, SaschaC <[email protected]> wrote: > oh, one follow-up question: > > as I use Ignite inprocess within a another clustered product (Druid), I > would like to disallow the Ignite management console or other Ignite nodes > to shut those ignite nodes down that are working inprocess as plugins > within > the outer product as this would also shutdown the Druid node that runs > ignite. > > I hoped that the shutdown command could be overwritten or otherwise be > deactivated but I see that the command is implemented by sending a > distributed closure around, so there doesn't seem to be a way to deactivate > this feature. To my understanding, if an Ignite node is in client mode, it > should not be under the control of such management commands just like a > webserver cannot shut-down a browser. > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Howto-setup-a-single-node- > standalone-Ignite-tp7197p7252.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov
