All of lore.kernel.org
 help / color / mirror / Atom feed
From: Haomai Wang <haomaiwang@gmail.com>
To: Xinze Chi <xmdxcxz@gmail.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: crc error when decode_message?
Date: Mon, 16 Mar 2015 22:06:22 +0800	[thread overview]
Message-ID: <CACJqLyZ50EkaLwSv2yEDuNq0Yj+=Og+x5gK01ao-woN1UqZPjw@mail.gmail.com> (raw)
In-Reply-To: <CANE=7sWuRcWhNx9VFBDp5csKed06a2ZDXbd1am2G+6Ua=wFC4w@mail.gmail.com>

On Mon, Mar 16, 2015 at 10:04 PM, Xinze Chi <xmdxcxz@gmail.com> wrote:
> How to process the write request in primary?
>
> Thanks.
>
> 2015-03-16 22:01 GMT+08:00 Haomai Wang <haomaiwang@gmail.com>:
>> AFAR Pipe and AsyncConnection both will mark self fault and shutdown
>> socket and peer will detect this reset. So each side has chance to
>> rebuild the session.
>>
>> On Mon, Mar 16, 2015 at 9:19 PM, Xinze Chi <xmdxcxz@gmail.com> wrote:
>>> Such as, Client send write request to osd.0 (primary), osd.0 send
>>> MOSDSubOp to osd.1 and osd.2
>>>
>>> osd.1 send reply to osd.0 (primary), but accident happened:
>>>
>>> 1. decode_message crc error when decode reply msg
>>> or
>>> 2. the reply msg is lost when send to osd.0, so osd.0 do not receive replay msg
>>>
>>> Could anyone tell me what is the behavior if osd.0 (primary)?
>>>

osd.0 and osd.1 both will try to reconnect peer side, and the lost
message will be resend to osd.0 from osd.1

>>> Thanks
>>>
>>> 2015-03-16 20:02 GMT+08:00 Xinze Chi <xmdxcxz@gmail.com>:
>>>> hi, all:
>>>>
>>>>       I want to know what is the behavior of primary when
>>>> decode_message crc error , such as read
>>>>
>>>> ack response message from remote peer?
>>>>
>>>>       Thanks.
>>> --
>>> 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
>>
>>
>>
>> --
>> Best Regards,
>>
>> Wheat



-- 
Best Regards,

Wheat

  reply	other threads:[~2015-03-16 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 12:02 crc error when decode_message? Xinze Chi
2015-03-16 13:19 ` Xinze Chi
2015-03-16 14:01   ` Haomai Wang
2015-03-16 14:04     ` Xinze Chi
2015-03-16 14:06       ` Haomai Wang [this message]
2015-03-17  7:23         ` Ning Yao
2015-03-17 13:46           ` Sage Weil
2015-03-17 13:58             ` Gregory Farnum
2015-03-18  2:52               ` Ning Yao

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='CACJqLyZ50EkaLwSv2yEDuNq0Yj+=Og+x5gK01ao-woN1UqZPjw@mail.gmail.com' \
    --to=haomaiwang@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=xmdxcxz@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.