From: Josh Durgin <josh.durgin@inktank.com>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: OSD network failure
Date: Fri, 16 Nov 2012 17:56:06 -0800 [thread overview]
Message-ID: <50A6EEB6.2020400@inktank.com> (raw)
In-Reply-To: <CAJH6TXixnqBgxOdk3UD2Tr4RTC5_RYnfXW9wmuHjD5ZD6G2OCQ@mail.gmail.com>
On 11/15/2012 01:51 AM, Gandalf Corvotempesta wrote:
> 2012/11/15 Josh Durgin <josh.durgin@inktank.com>:
>> So basically you'd only need a single nic per storage node. Multiple
>> can be useful to separate frontend and backend traffic, but ceph
>> is designed to maintain strong consistency when failures occur.
>
> Probably i've not exaplained well.
> I'll have multiple nics, one for frontend, one for backend used as ODS
> sync network.
> What happens in case of backend network failure? The frontend network
> is still ok, OSD is
> still reachable but is not able to sync datas.
Ah, ok. By default, the OSDs use the backend network for heartbeats,
so if it fails, they will notice and report peers they can't reach as
failed to the monitors, and the normal failure handling takes care
of things.
If you're worried about consistency, remember that a write won't
complete until it's on disk on all replicas. If you're interested
in the gory details of maintaining consistency, check out the peering
process [1].
Josh
[1] http://ceph.com/docs/master/dev/peering/
next prev parent reply other threads:[~2012-11-17 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 14:15 OSD network failure Gandalf Corvotempesta
2012-11-15 8:40 ` Josh Durgin
2012-11-15 9:51 ` Gandalf Corvotempesta
2012-11-17 1:56 ` Josh Durgin [this message]
2012-11-19 14:22 ` Gandalf Corvotempesta
2012-11-19 22:19 ` Gregory Farnum
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=50A6EEB6.2020400@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gandalf.corvotempesta@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.