From: Gregory Farnum <gregory.farnum@dreamhost.com>
To: Longguang Yue <longguang_yue@tcloudcomputing.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: question about socket conection among osd,mds,mon
Date: Mon, 14 Feb 2011 09:12:49 -0800 [thread overview]
Message-ID: <F7AC6D547FA64F7EB1230167F17B99A9@gmail.com> (raw)
In-Reply-To: <D0C67741759ABD4BBD8D3A5CB815606E07E986@mail.cloud-valley.com.cn>
On Monday, February 14, 2011 at 5:37 AM, Longguang Yue wrote:
> !!!! osd e35: 3 osds: 3 up, 3 in -- 2 blacklisted MDSes
>
> ceph can recover blacklisted osds by itself, but I want to recover blacklist osds as soon as possible.
>
> How to use the command, 'ceph osd blacklist rm host:port' ????
>
> thanks
None of your OSDs have been blacklisted. 2 of your MDSes have been, but that means that they either went down or were so laggy as to be useless. If they were laggy, then they will eventually find out and restart themselves, at which point they will be identified as a different MDS and won't be blacklisted.
This doesn't mean there's anything wrong with your OSDs, though!
-Greg
> -----邮件原件-----
> 发件人: rarecactus@gmail.com [mailto:rarecactus@gmail.com] 代表 Colin McCabe
> 发送时间: 2011年2月14日 18:21
> 收件人: Longguang Yue
> 抄送: Sage Weil; ceph-devel@vger.kernel.org
> 主题: Re: question about socket conection among osd,mds,mon
>
> Hi Longguang,
>
> The blacklist stops MDSes from talking to OSDs. You cannot blacklist
> an OSD itself.
>
> What is it that you're trying to do?
>
> sincerely,
> Colin
>
>
> On Sun, Feb 13, 2011 at 7:13 PM, Longguang Yue
> <longguang_yue@tcloudcomputing.com> wrote:
> > 1.Netstat info:
> > 10.10.1.100:6800 <--- 10.10.1.106:34585, 10.10.1.98:46625
> > 10.10.1.100:6801 <--- 10.10.1.106:59284, 10.10.1.98:35101
> > When osd need 2(more) listen sockets? Why others osd connect as many
> > times as its listen socket?
> >
> >
> > 2.how to deal with blacklist osds
> > osd e35: 3 osds: 3 up, 3 in -- 2 blacklisted MDSes
> >
> > according to 1 case, how to deal with blacklist.
> > If I need run 'ceph osd blacklist rm 10.10.1.106:34585 &&
> > 10.10.1.98:46625 ' ??????
> >
> > I think just only one osd listen socket exists!!!!!!
> > --
> > 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
> ??{.n?+???????+%??lzwm??b?맲??r??yǩ?ׯzX????ܨ}???Ơz?&j:+v???????zZ+??+zf???h???~????i???z??w?????????&?)ߢf?
--
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
prev parent reply other threads:[~2011-02-14 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 13:43 The Ceph wiki? Daniel Friesen
2011-02-13 18:30 ` Sage Weil
2011-02-14 0:44 ` Daniel Friesen
2011-02-14 1:21 ` how long client will take when recover to ok,after ceph down Longguang Yue
2011-02-14 10:00 ` Colin McCabe
2011-02-14 3:13 ` question about socket conection among osd,mds,mon Longguang Yue
2011-02-14 10:21 ` Colin McCabe
2011-02-14 13:37 ` 答复: " Longguang Yue
2011-02-14 17:12 ` Gregory Farnum [this message]
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=F7AC6D547FA64F7EB1230167F17B99A9@gmail.com \
--to=gregory.farnum@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=longguang_yue@tcloudcomputing.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.