From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Wido den Hollander <wido@widodh.nl>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Ceph on just two nodes being clients - reasonable?
Date: Wed, 19 Jan 2011 13:14:43 +0100 [thread overview]
Message-ID: <4D36D5B3.4040601@wpkg.org> (raw)
In-Reply-To: <1295437286.2255.25.camel@wido-desktop>
On 19.01.2011 12:41, Wido den Hollander wrote:
> Hi Thomas,
>
> I think the answer is Yes and No on this question, the devs might have
> another approach for your situation.
>
> If you would do this, you would have a MON, MDS and OSD on every server,
> in theory that would work. Mounting would be done by connecting to on of
> the MON's (doesn't matter which one).
>
> But Ceph requires, well, advises a odd number of monitors (Source:
> http://ceph.newdream.net/wiki/Designing_a_cluster )
>
> So you would require a third node which is running your third monitor to
> keep track of both nodes.
>
> My advise, for two nodes, use something like DRBD in Primary<> Primary
> and use a cluster filesystem like OCFS2.
Currently, I'm running glusterfs in such a scenario (two servers, each
being also clients), but I wanted to give ceph a try (glusterfs has some
performance issues with lots of small files), also because of its nice
features (snapshots, rbd etc.).
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2011-01-19 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 10:33 Ceph on just two nodes being clients - reasonable? Tomasz Chmielewski
2011-01-19 11:30 ` DongJin Lee
2011-01-19 11:41 ` Wido den Hollander
2011-01-19 11:55 ` would you recommend me a solution to store xen-imgfile Longguang Yue
2011-01-19 17:06 ` Sage Weil
2011-01-19 12:14 ` Tomasz Chmielewski [this message]
2011-01-19 15:57 ` Ceph on just two nodes being clients - reasonable? Gregory Farnum
2011-01-19 16:21 ` Tomasz Chmielewski
2011-01-19 17:55 ` Colin McCabe
2011-01-19 20:03 ` Tommi Virtanen
2011-01-19 21:09 ` Colin McCabe
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=4D36D5B3.4040601@wpkg.org \
--to=mangoo@wpkg.org \
--cc=ceph-devel@vger.kernel.org \
--cc=wido@widodh.nl \
/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.