From: Mykola Golub <to.my.trociny@gmail.com>
To: Sage Weil <sage@newdream.net>
Cc: Willem Jan Withagen <wjw@digiware.nl>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: OSD rebind connects to ports of other OSDs
Date: Tue, 20 Dec 2016 19:31:55 +0200 [thread overview]
Message-ID: <20161220173155.GC1510@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1612201521120.10615@piezo.novalocal>
On Tue, Dec 20, 2016 at 03:23:59PM +0000, Sage Weil wrote:
> On Tue, 20 Dec 2016, Willem Jan Withagen wrote:
> > So the question is:
> > - how much rebinding is required.....
>
> I think it's just for tests. My recollection is that we did this just
> because we can run out of ports since we can't reuse one until the tcp
> finwait2 (or whatever) timeout expires.
>
> > - And why do we set SO_REUSEADDR if we are going to add the ports to
> > avoid_ports. And thus a complete new port is required.
>
> I suspect it's safe to drop the option if the Linux vs FreeBSD semantics
> are in fact different.
SO_REUSEADDR is good to have, so when restarting after a crash bind
wouldn't fail with EADDRINUSE. Thus I wouldn leave it.
For the rebind issue, I would investigate first if this is expected,
that it binds to all interfaces, but rebinds to only one address. If
this is wrong fixing this might also solve the issue on FreeBSD.
--
Mykola Golub
next prev parent reply other threads:[~2016-12-20 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 10:21 OSD rebind connects to ports of other OSDs Willem Jan Withagen
2016-12-20 15:00 ` 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 [this message]
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=20161220173155.GC1510@gmail.com \
--to=to.my.trociny@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
--cc=wjw@digiware.nl \
/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.