From: Rick Jones <rick.jones2@hp.com>
To: Olaf van der Spek <ml@vdspek.org>
Cc: netdev@vger.kernel.org
Subject: Re: Seamless Service Restart / Port Takeover
Date: Wed, 12 Oct 2011 10:14:00 -0700 [thread overview]
Message-ID: <4E95CAD8.3050405@hp.com> (raw)
In-Reply-To: <CAGVGHmuVnsw4mdsxO=93yaYRgGaj20gR0+nNB_iaS=nTM_BThw@mail.gmail.com>
On 10/12/2011 09:53 AM, Olaf van der Spek wrote:
> Hi,
>
> When restarting a service, a webserver for example, you'd like this to
> be seamless for clients. Often, first a signal is send to the old
> process to close listening sockets, then the new process is started.
> This has both a race condition (sometimes 'avoided' with a sleep in
> between) and service interruption.
> Wouldn't it be possible to introduce mv / move like behaviour, where
> the socket can be rebound without races and without interruption?
I believe you can do that today if you write the application such that
the old instance, before it closes the listen endpoint and terminates,
instead passes access to it to the new instance via a Unix domain socket
between the two.
rick jones
next prev parent reply other threads:[~2011-10-12 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 16:53 Seamless Service Restart / Port Takeover Olaf van der Spek
2011-10-12 17:14 ` Rick Jones [this message]
2011-10-13 9:56 ` Olaf van der Spek
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=4E95CAD8.3050405@hp.com \
--to=rick.jones2@hp.com \
--cc=ml@vdspek.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).