Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
From: Denis Magda <dmagda@apache.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Shell script to stop Ignite node
Date: Mon, 21 Aug 2017 12:25:19 -0700
References: <CAGcMBHiyHjq4dKA_PvY=irzgtWqRN8edf3NwYWs18wihyg8nQQ@mail.gmail.com>
 <CABuYRcpVeO7Xit7oLTm+SUFNCebeXerjTdw0aocFwTvDcuKqMA@mail.gmail.com>
To: dev@ignite.apache.org
In-Reply-To: <CABuYRcpVeO7Xit7oLTm+SUFNCebeXerjTdw0aocFwTvDcuKqMA@mail.gmail.com>
Message-Id: <638B1A0F-5042-496E-8213-ED6521A59F84@apache.org>
archived-at: Mon, 21 Aug 2017 19:25:24 -0000

Igniters,

I would propose to make this a feature of Visor CLI.

Recently we=E2=80=99ve added the script to control a cluster activation =
[1] explaining that Visor CLI is not flexible for that. If we keep =
moving this way at some point there will be the whole zoo of scripts.

Why don=E2=80=99t we improve Visor CLI letting it connect to the cluster =
in the simplest way and embed the proposed feature in it?

[1] =
http://apache-ignite-developers.2346864.n4.nabble.com/Control-sh-script-an=
d-cluster-activation-td20821.html
That=E2=80=99s the second=20

=E2=80=94
Denis

> On Aug 21, 2017, at 11:44 AM, Valentin Kulichenko =
<valentin.kulichenko@gmail.com> wrote:
>=20
> +1
>=20
> -Val
>=20
> On Mon, Aug 21, 2017 at 9:06 AM, Yakov Zhdanov <yzhdanov@apache.org> =
wrote:
>=20
>> Guys,
>>=20
>> Currently to stop node on a particular server (not using visor or web
>> console) I need to run "jps" and then "kill" with a pid.
>>=20
>> What if we create ignite-stop.sh which will display the list of =
started
>> nodes on local host and allow user to choose one to stop. Also it =
should
>> support --all param to stop all and probably a signal.
>>=20
>> Thoughts?
>>=20
>> --Yakov
>>=20