From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [Patch] tabled: parse Chunk parameters in CLD v2 Date: Sun, 16 Aug 2009 09:32:37 -0400 Message-ID: <4A880A75.6020107@garzik.org> References: <20090816071033.1bcab0ae@redhat.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090816071033.1bcab0ae@redhat.com> Sender: hail-devel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Pete Zaitcev Cc: Project Hail List Pete Zaitcev wrote: > diff --git a/test/start-daemon b/test/start-daemon > index 590da92..203e392 100755 > --- a/test/start-daemon > +++ b/test/start-daemon > @@ -20,10 +20,10 @@ fi > cld -d data/cld -P cld.pid -p 18081 -E > chunkd -C $top_srcdir/test/chunkd-test.conf -E > > -# 3 is enough, but we like to let chunkd to come up eary and register with CLD > +# 3 is enough, but we like to let chunkd to come up early and register with CLD > sleep 7 > > -../server/tabled -C $top_srcdir/test/tabled-test.conf -E > +../server/tabled -C $top_srcdir/test/tabled-test.conf -E -D > > sleep 3 > Thinking out loud... I occasionally wonder about a TCP control channel for tabled, to be used for various administration purposes. tdbadm is not as useful when replication is active, unless tdbadm becomes the db4 master -- undesirable when the cluster is active. An alternative, already employed by bind utility rndc(8), is to create an authenticated TCP-based control channel, to be used for various administrative purposes. In tabled's case, we could use such a channel for * database maintenance activities, while database cluster is active * querying server startup status, so that you know _precisely_ when tabled is active. That would permit you to eliminate the various "sleep 3" and "sleep 7", I hope? Regards, Jeff