在 2011年8月10日 上午1:15，Josh Durgin <[email protected]> 写道：
> 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.
>
thanks，Josh
That explains the error i encountered,in GetInfo state,the peer OSD should send
MOSDPGNotify msg but not MOSDPGLog msg,so it's strange in upper condition.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
