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 B2A002004F3 for ; Tue, 15 Aug 2017 10:33:01 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B0F7916665A; Tue, 15 Aug 2017 08:33:01 +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 0125B166659 for ; Tue, 15 Aug 2017 10:33:00 +0200 (CEST) Received: (qmail 23872 invoked by uid 500); 15 Aug 2017 08:32:59 -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 23861 invoked by uid 99); 15 Aug 2017 08:32:59 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2017 08:32:59 +0000 Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id DB4261A00A2 for ; Tue, 15 Aug 2017 08:32:58 +0000 (UTC) Received: by mail-qk0-f177.google.com with SMTP id a77so1264598qkb.0 for ; Tue, 15 Aug 2017 01:32:58 -0700 (PDT) X-Gm-Message-State: AHYfb5jw4y/ZpDvo2lbYvmwkW1T22Sk+oHutbRYpCiBRK8Xbvo5OkxfX MR/CTCr/p+pouGuIhMsLoEIkJc/HEPpg X-Received: by 10.233.237.2 with SMTP id c2mr5107731qkg.107.1502785977421; Tue, 15 Aug 2017 01:32:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.34.6 with HTTP; Tue, 15 Aug 2017 01:32:16 -0700 (PDT) In-Reply-To: References: <82616AF7-6502-42E9-8123-5FDF5AB4E57D@apache.org> From: Dmitriy Setrakyan Date: Tue, 15 Aug 2017 01:32:16 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Control.sh script and cluster activation To: dev@ignite.apache.org Cc: Dmitriy Govorukhin Content-Type: multipart/alternative; boundary="001a114f4b3c5ba0930556c6a0a5" archived-at: Tue, 15 Aug 2017 08:33:01 -0000 --001a114f4b3c5ba0930556c6a0a5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Added one more suggestion below. BTW, if there is no ticket, let's create one and copy all the suggestions there. On Tue, Aug 15, 2017 at 1:13 AM, Dmitriy Setrakyan wrote: > Guys, > > Where is the ticket for adding control.[sh|bat] script to the bin folder? > I cannot find any mention of it. Was there a discussion on the dev list? > > Here are the issues I am seeing with the script: > > 1. It could be named better. Perhaps the name "cluster-ops" or > "cluster-switch" would be better. We should rename it in the next rele= ase. > 2. typing any bad command, e.g. "control bla" should provide a > standard usage message explaining correct syntax (see any other comman= d > under bin folder) > 3. failure to connect to the cluster results in a long stack trace... > instead, it should provide a standard error message, suggesting possib= le > reasons for it. > > 4. Whenever trying to connect to a cluster, the script should print out a message "Connecting to ip-address:port ...". Otherwise, it looks like it is just hanging. > D. > > On Tue, Aug 15, 2017 at 12:59 AM, Dmitriy Govorukhin < > dmitriy.govorukhin@gmail.com> wrote: > >> Valentin, >> >> We have jira issue for this IGNITE-5586 >> >> >> On Tue, Aug 15, 2017 at 10:56 AM, Dmitriy Govorukhin < >> dmitriy.govorukhin@gmail.com> wrote: >> >> > >> > Denis, >> > >> > 1. control.sh have help parameter. If you try enter ./control.sh --hel= p, >> > result is an example of how to use it, >> > "Example: --host {ip} --port {port} --{activate/deactivate} or without >> > command --host {ip} --port {port} then will print status" >> > >> > 2. Visorcmd will start daemon node and join in topology, it is quite >> long >> > time(as you know nodes joining in series) and requires resources. >> > Main goal was create some point for activation, fast and lightweight, >> > script does not start node. >> > >> > 3. Historically, the first name(control.sh - controls cluster >> > state active/inactive). Have any idea for another name? >> > >> > On Tue, Aug 15, 2017 at 2:25 AM, Valentin Kulichenko < >> > valentin.kulichenko@gmail.com> wrote: >> > >> >> Agree that this is confusing. I think this functionality should be a >> part >> >> of Visor CLI tool (likely a new command there). >> >> >> >> -Val >> >> >> >> On Mon, Aug 14, 2017 at 4:21 PM, Denis Magda >> wrote: >> >> >> >> > Dmitriy, >> >> > >> >> > I see you contributed control.sh script that activates a cluster >> after a >> >> > restart. Honestly, I=E2=80=99m a bit confused by it: >> >> > >> >> > 1. How to use it? I could find out that there are some of the >> parameters >> >> > but the =E2=80=98help=E2=80=99 is not implemented. Please fix this = and provide a >> >> > description for every parameter you introduced. >> >> > >> >> > 2. Why did we decide to create a specific script for that? Why can= =E2=80=99t >> we >> >> > use existing visorcmd script? >> >> > >> >> > 3. Why the script called =E2=80=9Ccontrol.sh=E2=80=9D? >> >> > >> >> > =E2=80=94 >> >> > Denis >> >> >> > >> > >> > > --001a114f4b3c5ba0930556c6a0a5--