ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Kozlov <skoz...@gridgain.com>
Subject Re: Shell script to stop Ignite node
Date Sat, 26 Aug 2017 20:16:40 GMT
Sure, Dmitriy

Filed the issue [1]

[1] https://issues.apache.org/jira/browse/IGNITE-6191

On Sat, Aug 26, 2017 at 12:35 AM, Dmitriy Setrakyan <dsetrakyan@apache.org>
wrote:

> Huge +1
>
> We badly need Linux specific installation packages. Sergey, can you file a
> ticket?
>
> D.
>
> On Tue, Aug 22, 2017 at 12:51 AM, Sergey Kozlov <skozlov@gridgain.com>
> wrote:
>
> > Hi
> >
> > Looks like we're trying reinvent a bicycle.
> >
> > First we have to admit that current installation procedure is very poor
> > ("unzip and run"). As result we need scripts to manage Apache Ignite
> > process(es)
> >
> > We should to move to better integration under *nix system (at least),
> > namely:
> >
> > 1. Provide a script to *nix for start/stop/restart/reload Apache Ignite
> as
> > system service (a deamon). At the beginning we can focus on Ubuntu and
> > RedHat (CentOS)
> >
> > 2. Provide the start confugration for Apache Ignite where provide
> > non-spring options like number of Apache Ignite instances, JVM options,
> > work/log directories etc (at might be ini file)
> >
> > 3. Provide platform-adopted packages (*.pkg, *deb) in the own repository
> > that will install (upgrade) Apache Ignite in proper directories, for
> > instance: configuration in /etc/ignite/config, visorcmd in /usr/sbin,
> start
> > scripts in /etc/init.d, work directory in /var/lib/ignite, logs in
> > /var/log/ignite/. It will significally reduce the efforts to install
> Apache
> > Ignite for newbies ("just add the reporsitory and run package manager")
> >
> >
> >
> > On Tue, Aug 22, 2017 at 2:16 AM, Dmitriy Setrakyan <
> dsetrakyan@apache.org>
> > wrote:
> >
> > > Completely agree. Why do we have Visor CLI join the cluster at all? It
> > > should be issuing REST requests to the cluster remotely. Essentially,
> > every
> > > command should be a REST request/response.
> > >
> > > Is this possible?
> > >
> > > D.
> > >
> > > On Mon, Aug 21, 2017 at 12:25 PM, Denis Magda <dmagda@apache.org>
> wrote:
> > >
> > > > 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.kulichenko@gmail.com> wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > -Val
> > > > >
> > > > > On Mon, Aug 21, 2017 at 9:06 AM, Yakov Zhdanov <
> yzhdanov@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
> > > > >>
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Sergey Kozlov
> > GridGain Systems
> > www.gridgain.com
> >
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message