Re: 答复: 答复: 答复: another peering stuck caused by net problem.

* Re: 答复: 答复: 答复: another peering stuck caused by net problem.
       [not found]           ` <0C3F6DA3760D0C4691E69E5BE224FF495E175A2E@H3CMLB12-EX.srv.huawei-3com.com>
@ 2015-11-03  1:12             ` Samuel Just
  2015-11-03  1:24               ` 答复: " yangruifeng.09209
  0 siblings, 1 reply; 7+ messages in thread
From: Samuel Just @ 2015-11-03  1:12 UTC (permalink / raw)
  To: yangruifeng.09209; +Cc: Chenxiaowei, Sage Weil (sweil@redhat.com), ceph-devel

The problem is that peering shouldn't hang for no reason.  If you are
seeing peering hang for a long time either
1) you are hitting a peering bug which we need to track down and fix
2) peering actually cannot make progress.

In case 1, it can be nice to have a work around to force peering to
restart and avoid the bug.  However, case 2 would not be helped by
restarting peering, you'd just end up in the same place.  If you did
it based on a timeout, you'd just increase load by a ton when in that
situation.  What problem are you trying to solve?
-Sam

On Mon, Nov 2, 2015 at 5:05 PM, yangruifeng.09209@h3c.com
<yangruifeng.09209@h3c.com> wrote:
> ok.
>
> thanks
> Ruifeng Yang
>
> -----邮件原件-----
> 发件人: Samuel Just [mailto:sjust@redhat.com]
> 发送时间: 2015年11月3日 9:03
> 收件人: yangruifeng 09209 (RD)
> 抄送: chenxiaowei 11245 (RD); Sage Weil (sweil@redhat.com)
> 主题: Re: 答复: 答复: another peering stuck caused by net problem.
>
> Would it be ok if I reply to the list as well?
> -Sam
>
> On Mon, Nov 2, 2015 at 4:37 PM, yangruifeng.09209@h3c.com <yangruifeng.09209@h3c.com> wrote:
>> the cluster is maybe always peering in same exceptional cases, but it
>> can return to normal by *manual* 'ceph osd down <osdid>', this is not
>> convenient in a production environment, and against the concept of rados.
>> add a timeout mechanism to kick it, or kick it when io hang, maybe reasonable?
>>
>> thanks,
>> Ruifeng Yang
>>
>> -----邮件原件-----
>> 发件人: Samuel Just [mailto:sjust@redhat.com]
>> 发送时间: 2015年11月3日 2:21
>> 收件人: yangruifeng 09209 (RD)
>> 抄送: chenxiaowei 11245 (RD); Sage Weil (sweil@redhat.com)
>> 主题: Re: 答复: another peering stuck caused by net problem.
>>
>> I mean issue 'ceph osd down <osdid>' for the primary on the pg.  But that only causes peering to restart.  If peering stalled previously, it'll probably stall again.  What are you trying to accomplish?
>> -Sam
>>
>> On Fri, Oct 30, 2015 at 5:51 PM, yangruifeng.09209@h3c.com <yangruifeng.09209@h3c.com> wrote:
>>> do you mean restart primary osd? or any other command？
>>>
>>> thanks
>>> Ruifeng Yang
>>>
>>> -----邮件原件-----
>>> 发件人: Samuel Just [mailto:sjust@redhat.com]
>>> 发送时间: 2015年10月30日 23:07
>>> 收件人: chenxiaowei 11245 (RD)
>>> 抄送: Sage Weil (sweil@redhat.com); yangruifeng 09209 (RD)
>>> 主题: Re: another peering stuck caused by net problem.
>>>
>>> How would that help?  As a way to work around a possible bug?  You can accomplish pretty much the same thing by setting the primary down.
>>> -Sam
>>>
>>> On Wed, Oct 28, 2015 at 8:22 PM, Chenxiaowei <chen.xiaowei@h3c.com> wrote:
>>>> Hi, Samuel&Sage:
>>>>         I am cxwshawn from H3C(belong to HP), the pg peering stuck
>>>> problem is a serious problem especially under the production environment, So here we came up two solutions:
>>>>         if state Peering stuck too long, we can check timeout
>>>> exceeds to force transition from Peering to Reset state, Or we can add a command line to force one pg from Peering stuck to Reset state.
>>>>
>>>> What's your advice? Wish your reply
>>>>
>>>> Yours
>>>> shawn from Beijing, China.
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> -
>>>> ---------------------------------------------------------------
>>>> 本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
>>>> 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
>>>> 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
>>>> 邮件！
>>>> This e-mail and its attachments contain confidential information
>>>> from H3C, which is intended only for the person or entity whose
>>>> address is listed above. Any use of the information contained herein
>>>> in any way (including, but not limited to, total or partial
>>>> disclosure, reproduction, or dissemination) by persons other than
>>>> the intended
>>>> recipient(s) is prohibited. If you receive this e-mail in error,
>>>> please notify the sender by phone or email immediately and delete it!
--
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

^ permalink raw reply	[flat|nested] 7+ messages in thread