Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E019C200D0D for ; Fri, 25 Aug 2017 23:36:19 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8D24D16D52D; Fri, 25 Aug 2017 21:36:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D2D8816D52A for ; Fri, 25 Aug 2017 23:36:16 +0200 (CEST) Received: (qmail 3569 invoked by uid 500); 25 Aug 2017 21:36:15 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 3558 invoked by uid 99); 25 Aug 2017 21:36:15 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Aug 2017 21:36:15 +0000 Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com [209.85.220.180]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C90701A00DF for ; Fri, 25 Aug 2017 21:36:14 +0000 (UTC) Received: by mail-qk0-f180.google.com with SMTP id k126so5004171qkb.4 for ; Fri, 25 Aug 2017 14:36:14 -0700 (PDT) X-Gm-Message-State: AHYfb5i68wTUucbWYGMGUoB4VoYw7qqRtevEiuDQJU9adGmg3HQLy4DU saCH5zbNi1q/c1XMucuc9MT/QR3OIwn7 X-Received: by 10.233.237.136 with SMTP id c130mr16113908qkg.107.1503696973867; Fri, 25 Aug 2017 14:36:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.34.6 with HTTP; Fri, 25 Aug 2017 14:35:33 -0700 (PDT) In-Reply-To: References: <638B1A0F-5042-496E-8213-ED6521A59F84@apache.org> From: Dmitriy Setrakyan Date: Fri, 25 Aug 2017 14:35:33 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Shell script to stop Ignite node To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="94eb2c09830efa455d05579abb1c" archived-at: Fri, 25 Aug 2017 21:36:20 -0000 --94eb2c09830efa455d05579abb1c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 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 a= s > 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, sta= rt > scripts in /etc/init.d, work directory in /var/lib/ignite, logs in > /var/log/ignite/. It will significally reduce the efforts to install Apac= he > Ignite for newbies ("just add the reporsitory and run package manager") > > > > On Tue, Aug 22, 2017 at 2:16 AM, Dmitriy Setrakyan > 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 wrote= : > > > > > Igniters, > > > > > > I would propose to make this a feature of Visor CLI. > > > > > > Recently we=E2=80=99ve added the script to control a cluster activati= on [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 clus= ter 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=E2=80=99s the second > > > > > > =E2=80=94 > > > 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 > > > 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 > --94eb2c09830efa455d05579abb1c--