CEPH filesystem development
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Roman Hlynovskiy <roman.hlynovskiy@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: ceph stability
Date: Thu, 20 Dec 2012 08:31:22 -0600	[thread overview]
Message-ID: <50D3213A.2080401@inktank.com> (raw)
In-Reply-To: <CAD5ewrryqXEDv_HDGK8RettDmi7LwH_eEOCNCx_1jduj61_=cA@mail.gmail.com>

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.

>
> http://ceph.com/docs/master/architecture/ says:
> -----
> The Ceph filesystem service is provided by a daemon called ceph-mds.
> It uses RADOS to store all the filesystem metadata (directories, file
> ownership, access modes, etc), and directs clients to access RADOS
> directly for the file contents. The Ceph filesystem aims for POSIX
> compatibility. ceph-mds can run as a single process, or it can be
> distributed out to multiple physical machines, either for high
> availability or for scalability.
>
> High Availability: The extra ceph-mds instances can be standby, ready
> to take over the duties of any failed ceph-mds that was active. This
> is easy because all the data, including the journal, is stored on
> RADOS. The transition is triggered automatically by ceph-mon.
> Scalability: Multiple ceph-mds instances can be active, and they will
> split the directory tree into subtrees (and shards of a single busy
> directory), effectively balancing the load amongst all active servers.
>
> Combinations of standby and active etc are possible, for example
> running 3 active ceph-mds instances for scaling, and one standby
> intance for high availability.
> -----
>
>   I saw cases while standby mds took over traffic from the active one.
> Looks like it's working. Would you please clarify.

I don't think there is anything that would prevent even active-active 
MDS setups to work, it's just that it may not be stable.

>   I tried to disable 2 standby mds and happily reproduced the problem )
> so, it's something else. I will try playing with mds log level and
> provide more accurate details.

Good info!  Btw, regarding the bug tracker, if you make an account and 
go to the "fs" project, you should see a "new issue" link.

>
> thanks!
>
>
> 2012/12/19 Mark Nelson <mark.nelson@inktank.com>:
>
>>
>>
>> A quicky side-node:  multi-mds solutions aren't being supported in
>> production right now.  Not sure if your stat problems below are related, but
>> you may want to try starting out with a single mds and see if the problem
>> goes away.  If so, there may be some hints in the mds logs regarding what's
>> going on.  Bug reports are welcome!
>>
>>>
>>> [osd.0]
>>>       host = ceph-node01
>>>
>>> [osd.1]
>>>       host = ceph-node02
>>>
>>> [osd.2]
>>>       host = ceph-node03
>
>
>
>
> --
> ...WBR, Roman Hlynovskiy
>


  reply	other threads:[~2012-12-20 14:31 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 [this message]
2012-12-21 10:07       ` Amon Ott
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=50D3213A.2080401@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox