All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amon Ott <ao@m-privacy.de>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: Roman Hlynovskiy <roman.hlynovskiy@gmail.com>,
	ceph-devel@vger.kernel.org
Subject: Re: ceph stability
Date: Fri, 21 Dec 2012 11:07:55 +0100	[thread overview]
Message-ID: <50D434FB.4020909@m-privacy.de> (raw)
In-Reply-To: <50D3213A.2080401@inktank.com>

Am 20.12.2012 15:31, schrieb Mark Nelson:
> On 12/20/2012 01:08 AM, Roman Hlynovskiy wrote:
>> Hello Mark,
>>
>> for multi-mds solutions do you refer to multi-active arch or 1 active
>> and many standby arch?
> 
> That's a good question!  I know we don't really recommend multi-active
> right now for production use.  Not sure what our current recommendations
> are for multi-standby.  As far as I know it's considered to be more
> stable.  I'm sure Greg or Sage can chime in with a more accurate
> assessment.

We have been testing a lot with multi-standby, because a single MDS does
not make a lot of sense in a cluster. Maybe the clue is to have only one
standby, making SPOF a DPOF?

Up to 0.55 with some of Yan's fixes, Ceph has been too instable whenever
it came to MDS failover. As long as the same MDS has been kept active,
it was quite stable.

We are really hoping for 0.56 with the additional MDS fixes and also
fixed kernel 3.8 code. We have been waiting to replace our existing
cluster fs with CephFS for at least one and a half years, but it has
never been stable enough in our setup with standby MDS and takeover, let
alone multi-active. We do not want to risk a complete cluster failure.

Amon Ott
-- 
Dr. Amon Ott
m-privacy GmbH           Tel: +49 30 24342334
Am Köllnischen Park 1    Fax: +49 30 99296856
10179 Berlin             http://www.m-privacy.de

Amtsgericht Charlottenburg, HRB 84946

Geschäftsführer:
 Dipl.-Kfm. Holger Maczkowsky,
 Roman Maczkowsky

GnuPG-Key-ID: 0x2DD3A649

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-12-21 10:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19  9:03 ceph stability Roman Hlynovskiy
2012-12-19 10:08 ` Joao Eduardo Luis
2012-12-19 10:58   ` Roman Hlynovskiy
2012-12-19 12:11     ` Joao Eduardo Luis
2012-12-19 13:26 ` Mark Nelson
2012-12-20  7:08   ` Roman Hlynovskiy
2012-12-20 14:31     ` Mark Nelson
2012-12-21 10:07       ` Amon Ott [this message]
2013-01-05  0:37         ` Gregory Farnum
2012-12-19 15:40 ` Sage Weil
2012-12-20  8:02   ` Roman Hlynovskiy
2012-12-20 15:20     ` Sam Lang
2012-12-21  4:49       ` Roman Hlynovskiy

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=50D434FB.4020909@m-privacy.de \
    --to=ao@m-privacy.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.nelson@inktank.com \
    --cc=roman.hlynovskiy@gmail.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.