From: Josh Durgin <josh.durgin@dreamhost.com>
To: huang jun <hjwsm1989@gmail.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: osd down after adding OSDs
Date: Tue, 09 Aug 2011 10:15:10 -0700 [thread overview]
Message-ID: <4E416B1E.5040904@dreamhost.com> (raw)
In-Reply-To: <CABAwU-ZVhwSRyZgy9n1EG7gUWpxgcH97YnKjPjQn4C+TvomALQ@mail.gmail.com>
On 08/08/2011 06:29 PM, huang jun wrote:
> thanks，Josh
> Here the osd.10.log for the second condition.
> and osd.15-tail.log for the first, because osd.15.log is about 130MB,
> i'm not permitted to upload it, so i tail 70000 lines of it.
> btw if the recovery statechart in GetInfo state, what will happened if
> we recept a MOSDPGLog message, the statechart going to Crashed state?
It depends on when the message was sent. If it was sent during a
previous peering, it is ignored before it reaches the state machine by
checking pg->old_peering_msg in OSD::handle_pg_log.
Otherwise, if the log was sent after the current peering attempt
started, the primary does enter the Crashed state. It's a bug that a log
was received in this case, since GetInfo is the first stage of peering,
and no logs were requested yet.
--
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
next prev parent reply other threads:[~2011-08-09 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 13:19 osd down after adding OSDs huang jun
2011-08-09 0:13 ` Josh Durgin
[not found] ` <CABAwU-ZVhwSRyZgy9n1EG7gUWpxgcH97YnKjPjQn4C+TvomALQ@mail.gmail.com>
2011-08-09 17:15 ` Josh Durgin [this message]
2011-08-10 0:13 ` huang jun
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=4E416B1E.5040904@dreamhost.com \
--to=josh.durgin@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=hjwsm1989@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.