hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Barr <dave.b...@gmail.com>
Subject Re: About puppet and fabric (WAS: operational overhead for HBase)
Date Thu, 18 Aug 2011 03:17:35 GMT
On Wed, Aug 17, 2011 at 4:45 PM, Jean-Daniel Cryans <jdcryans@apache.org> wrote:
>> I'm currently evaluating the use of Puppet for Hadoop/HBase automated
>> deploys and Fabric looks a lot simpler and more descriptive.  I'm
>> curious how well Fabric would work in its own right without Puppet for
>> automate installs?
>
> I'll let my puppet masters answer that.

Hi!  :)

Using puppet for hadoop/hbase deploys is a fine option.

The downside of puppet is that it's not very efficient in deploying.
It checksums every file it is told about, and being written in Ruby,
checksumming isn't fast. If you want rapid pushes, rsync will be
faster (but less elegant).  But if you can kick off puppet runs in
parallel, you probably don't care too much how slow an individual box
is to update.

Having a pull model is nice because you can just bring a new node
online and bam, you'll know the correct files will be there.  You
don't have to remember to push it.

The downside of puppet is of course you can't really control when
changes go out, and you can't easily test changes without putting
complexity at the puppet level.

--Dave

Mime
View raw message