ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Govorukhin <dmitriy.govoruk...@gmail.com>
Subject Re: Control.sh script and cluster activation
Date Tue, 15 Aug 2017 07:56:27 GMT
Denis,

1. control.sh have help parameter. If you try enter ./control.sh --help,
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 <dmagda@apache.org> wrote:
>
> > Dmitriy,
> >
> > I see you contributed control.sh script that activates a cluster after a
> > restart. Honestly, I’m a bit confused by it:
> >
> > 1. How to use it? I could find out that there are some of the parameters
> > but the ‘help’ 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’t we
> > use existing visorcmd script?
> >
> > 3. Why the script called “control.sh”?
> >
> > —
> > Denis
>

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