Igniters, I would propose to make this a feature of Visor CLI.
Recently we’ve 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’t 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-and-cluster-activation-td20821.html That’s the second — Denis > On Aug 21, 2017, at 11:44 AM, Valentin Kulichenko > <valentin.kuliche...@gmail.com> wrote: > > +1 > > -Val > > On Mon, Aug 21, 2017 at 9:06 AM, Yakov Zhdanov <yzhda...@apache.org> wrote: > >> Guys, >> >> 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. >> >> 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. >> >> Thoughts? >> >> --Yakov >>
