From: Willem Jan Withagen <wjw@digiware.nl>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: OSD rebind connects to ports of other OSDs
Date: Tue, 20 Dec 2016 11:21:19 +0100 [thread overview]
Message-ID: <2b061067-e839-054e-5166-619deecfae5e@digiware.nl> (raw)
Hi,
I've been banging my head against the wall for some time now.
But rebinding OSD.0 (in cephtool-test-mon.sh) does not quite work.
When rebinding it connects to the ports of OSD.1 because those ports are
the first not in the avoid_list. That should be refused since these
sockets belong to a different process.
UNLESS SO_REUSEPORT is set:
SO_REUSEPORT allows completely duplicate bindings by multiple processes
if they all set SO_REUSEPORT before binding the port. This option
permits multiple instances of a program to each receive UDP/IP
multicast or broadcast datagrams destined for the bound port.
Which seems that that happens.
Output from sockstat in this state:
wjw ceph-osd-0 43305 14 tcp4 *:6800 *:*
wjw ceph-osd-0 43305 15 tcp4 127.0.0.1:6804 *:*
wjw ceph-osd-0 43305 16 tcp4 127.0.0.1:6805 *:*
wjw ceph-osd-0 43305 45 tcp4 127.0.0.1:6806 *:*
wjw ceph-osd-1 43318 14 tcp4 *:6804 *:*
wjw ceph-osd-1 43318 15 tcp4 *:6805 *:*
wjw ceph-osd-1 43318 16 tcp4 *:6806 *:*
wjw ceph-osd-1 43318 17 tcp4 *:6807 *:*
Which clearly demonstrates the mess.
How ever that option is nowhere set in the ceph-code, neither is it a
setting that "just" gets set.
Any suggestions where to look for this option to get set in an
incidental/bug way would be much appreciated.
Or a suggestion on how to easily debug this.
Thanx,
--WjW
next reply other threads:[~2016-12-20 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 10:21 Willem Jan Withagen [this message]
2016-12-20 15:00 ` OSD rebind connects to ports of other OSDs Willem Jan Withagen
2016-12-20 15:23 ` Sage Weil
2016-12-20 15:50 ` Willem Jan Withagen
2016-12-20 17:31 ` Mykola Golub
2016-12-20 18:39 ` Willem Jan Withagen
2016-12-20 18:43 ` Sage Weil
2016-12-20 18:48 ` Willem Jan Withagen
2016-12-20 15:06 ` Mykola Golub
2016-12-20 16:48 ` Willem Jan Withagen
2016-12-20 17:23 ` Mykola Golub
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=2b061067-e839-054e-5166-619deecfae5e@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox