From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [Patch 2/7] tabled: add <Cell> element
Date: Wed, 20 Jan 2010 14:51:08 -0500 [thread overview]
Message-ID: <4B575EAC.4040609@garzik.org> (raw)
In-Reply-To: <20100114211126.79c3fd91@redhat.com>
On 01/14/2010 11:11 PM, Pete Zaitcev wrote:
> Make the cell configurable. Among other things we need this for is
> that you cannot migrate a tabled over when DB format changes, short
> of running 2 CLDs.
>
> We also add a few thoughts to the documentation, prompted by re-reading
> of the document while adding the clause for<Cell>.
>
> Signed-Off-By: Pete Zaitcev<zaitcev@redhat.com>
>
> ---
> doc/etc.tabled.conf | 7 +++++++
> doc/setup.txt | 40 +++++++++++++++++++++++++++++++++++++---
> server/cldu.c | 4 ++++
> server/config.c | 11 +++++++++++
> server/server.c | 2 +-
> server/tabled.h | 1 +
> 6 files changed, 61 insertions(+), 4 deletions(-)
Strictly speaking, this is wrong, but I applied so that we may make
forward progress.
The definition of a "cell" (or "cel") is everything within a single CLD
namespace.
It is a design requirement that any number of separate tabled instances
may be run within a single cell. The differentiating factor is
pathname. Thus, one tabled instance may store files in
cld://cld.mysite.com/table1/
and a totally separate, parallel instance of table may store its files in
cld://cld.mysite.com/table2/
Provisioning another tabled instance should be as simple as creating a
new directory in CLD, and running the tabled/chunkd nodes.
Thus, the user interface should be CLD hostname + pathname, not "cell name."
Jeff
next prev parent reply other threads:[~2010-01-20 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 4:11 [Patch 2/7] tabled: add <Cell> element Pete Zaitcev
2010-01-20 19:51 ` Jeff Garzik [this message]
2010-01-20 20:13 ` Pete Zaitcev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B575EAC.4040609@garzik.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.