hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Boudnik <...@apache.org>
Subject Re: ssh'ing around the cluster
Date Fri, 26 Feb 2016 05:03:50 GMT
On Fri, Feb 26, 2016 at 10:53AM, Lei Chang wrote:
> Hi Konstantin,
> 
> If I understand correctly, what you requested is in current hawq code base.
> To init hawq, "hawq init cluster" is one way, you can also use "hawq init
> master" and "hawq init segment" on all cluster nodes. Master and segments
> are decoupled in 2.0.

Ah, nice. Let me try that. Thanks!

> 
> Cheers
> Lei
> 
> 
> On Fri, Feb 26, 2016 at 9:40 AM, Konstantin Boudnik <cos@apache.org> wrote:
> 
> > Guys,
> >
> > more revelations about the way Hawq is designed to work with the service
> > bootstraps, config management, and so on. Looking into hawq_ctl and
> > observing
> > the behavior of 'hawq init cluster' I see that a number of operations is
> > intended to be initiated from presumably, a master node, and carried on all
> > the nodes of a hawq cluster via the means or ssh (or rsync). While doing so
> > might be a convenient shortcut for the development environment, it isn't as
> > much in a real deployment. For one, it requires password-less SSH access
> > between nodes, which isn't (generally speaking) how data centers might
> > operate.
> >
> > Perhaps a better way of separating the concerns here is to have isolated
> > functions to perform only local-node operations, and a wrapper to run the
> > same
> > functionality on the all remote nodes, via ssh or else. If such split is
> > done,
> > then an orchestration mechanism (such as a state machine similar to Puppet
> > or
> > Chef), would execute the scripts on separate nodes in full isolation. And
> > if
> > so desired in a dev environment, the current functionality would be
> > available
> > as well.
> >
> > Thoughts? Regards,
> >   Cos
> >

Mime
View raw message