From: Tomasz Chmielewski <mangoo@wpkg.org>
To: lvs-devel@vger.kernel.org
Subject: how does LVS persistence work?
Date: Tue, 18 Oct 2011 23:26:43 +0200 [thread overview]
Message-ID: <4E9DEF13.3040106@wpkg.org> (raw)
According to http://www.linuxvirtualserver.org/docs/persistence.html:
In the persistent port, when a client first accesses the
service, LinuxDirector will create a connection template
between the given client and the selected server, then create
an entry for the connection in the hash table. The template
expires in a configurable time, and the template won't expire
until all its connections expire.
Suppose I have two real servers and persistence set to 30 minutes.
How will LVS persistence behave for a client which first connects at 01:00?
1) persistence is always "first connected + 30 minutes".
When the client connects at 01:00, LVS sets persistence to 30 minutes.
All connections from this client, between 01:00-01:30 will be directed
to one server.
At ~01:31, persistence will expire and will be set again; it's possible
that the client will hit the other server, even though the last
connection was made at 01:29.
Meaning - if the client makes one short connection every 25 minutes and
persistence is set to 30 minutes, the chances are it will hit a
different server (almost) every time.
lvs-devel@vger.kernel.org
2) persistence is always extended and is "last connection + 30 minutes".
In other words - if the client makes one short connection every 25
minutes and persistence is set to 30 minutes, it is practically
guaranteed the client will always hit the same server.
Which one is true, 1) or 2)?
PS. http://lists.graemef.net/mailman/listinfo/lvs-users seems dead?
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2011-10-18 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 21:26 Tomasz Chmielewski [this message]
2011-10-18 21:40 ` how does LVS persistence work? Simon Horman
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=4E9DEF13.3040106@wpkg.org \
--to=mangoo@wpkg.org \
--cc=lvs-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 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.