ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: Stop the node but keep the process
Date Thu, 12 Nov 2015 11:56:28 GMT
Alexander, I dont think this should stop the entire cluster? It should stop
local node for particularly that Ignite instance.

--Yakov

2015-11-12 14:39 GMT+03:00 Alexandre Boudnik <alexander.boudnik@gmail.com>:

> You've right.
>
> grid.close() will shutdown entire cluster. It is way too much.
> Take care,
> Alexandre "Sasha" Boudnik
>
> call me via Google Voice:
> 1(405) BUDNIKA
> 1(405) 283-6452
>
>
>
> On Thu, Nov 12, 2015 at 3:18 AM, Anton Vinogradov
> <avinogradov@gridgain.com> wrote:
> > Alexandre,
> >
> > As far as I undesrtand "grid" is an Ignite instance.
> > Could you please check that grid.close(); works correct in this case?
> >
> > On Thu, Nov 12, 2015 at 11:03 AM, Alexandre Boudnik
> > <alexander.boudnik@gmail.com> wrote:
> >>
> >> Hello,
> >>
> >> In my cluster, each node is running as web application. When web
> >> application has been stopped and servlet context has been destroyed,
> >> it needs to terminate the Ignite node. Unfortunately,
> >>
> >>
> >>
> grid.cluster().stopNodes(Collections.singletonList(service.grid.cluster().localNode().id()));
> >>
> >> terminates the entire jvm by calling System.exit().
> >>
> >> Could you advise how to terminate/exclude the node from cluster but to
> >> keep the web server process, and to be able to restart the node?
> >>
> >> Take care,
> >> Alexandre "Sasha" Boudnik
> >>
> >> call me via Google Voice:
> >> 1(405) BUDNIKA
> >> 1(405) 283-6452
> >
> >
>

Mime
View raw message