From: Aleksey Chudov <aleksey.chudov@gmail.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: lvs-devel@vger.kernel.org
Subject: Re: [PATCH] ipvs: add sync_persist_mode flag
Date: Mon, 24 Jun 2013 17:37:09 +0300 [thread overview]
Message-ID: <51C85995.1060500@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1306231108450.1584@ja.ssi.bg>
Hello,
Pair of LVS servers with a modified kernel worked under load for several
days without any problems.
I completed several additional tests. I analyzed the traffic to the LVS
servers using tcpdump. There is not SYN or RST packets spike at the time
of migration of IP address. Thus, most of the connections have continued
to operate normally. I also once again made sure that most of clients
remain on the same real servers.
Seems like sync_persist_mode combined with sloppy_tcp works fine.
Regards,
Aleksey
next prev parent reply other threads:[~2013-06-24 14:37 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 12:09 [PATCH] Sloppy TCP, SH rebalancing, SHP scheduling Alexander Frolkin
2013-05-24 15:05 ` Julian Anastasov
2013-05-24 15:14 ` Alexander Frolkin
2013-05-24 16:18 ` Aleksey Chudov
2013-05-27 21:31 ` Julian Anastasov
2013-05-28 13:41 ` Aleksey Chudov
2013-05-30 6:37 ` Julian Anastasov
2013-06-07 7:53 ` Alexander Frolkin
2013-06-19 9:03 ` Julian Anastasov
2013-06-19 19:25 ` Julian Anastasov
2013-06-20 17:02 ` Aleksey Chudov
2013-06-20 20:09 ` Julian Anastasov
2013-06-19 20:44 ` Aleksey Chudov
2013-06-22 11:20 ` [PATCH] ipvs: add sync_persist_mode flag Aleksey Chudov
2013-06-22 12:43 ` Julian Anastasov
2013-06-22 21:11 ` Aleksey Chudov
2013-06-23 8:34 ` Julian Anastasov
2013-06-24 14:37 ` Aleksey Chudov [this message]
2013-06-24 19:57 ` Julian Anastasov
2013-05-27 21:11 ` [PATCH] Sloppy TCP, SH rebalancing, SHP scheduling Julian Anastasov
2013-06-07 8:12 ` Alexander Frolkin
2013-06-10 19:31 ` Julian Anastasov
2013-06-11 8:38 ` Alexander Frolkin
2013-06-11 19:57 ` Julian Anastasov
2013-06-12 14:10 ` Alexander Frolkin
2013-06-12 20:47 ` Julian Anastasov
2013-06-13 8:38 ` Alexander Frolkin
2013-06-13 12:56 ` Alexander Frolkin
2013-06-13 19:50 ` Julian Anastasov
2013-06-13 14:18 ` Alexander Frolkin
2013-06-13 20:31 ` Julian Anastasov
2013-06-14 10:22 ` Alexander Frolkin
2013-06-16 6:52 ` Julian Anastasov
2013-06-17 8:32 ` Alexander Frolkin
2013-06-17 9:00 ` Julian Anastasov
2013-06-17 9:04 ` Julian Anastasov
2013-06-17 11:11 ` Alexander Frolkin
2013-06-17 20:05 ` Julian Anastasov
2013-06-18 9:30 ` Alexander Frolkin
2013-06-18 20:52 ` Julian Anastasov
2013-06-14 11:47 ` Alexander Frolkin
2013-06-16 8:30 ` Julian Anastasov
2013-06-17 10:35 ` Alexander Frolkin
2013-06-17 19:48 ` Julian Anastasov
2013-06-18 9:08 ` Alexander Frolkin
2013-06-18 20:41 ` Julian Anastasov
2013-06-10 15:12 ` Alexander Frolkin
2013-06-10 16:03 ` Alexander Frolkin
2013-06-10 20:52 ` Julian Anastasov
2013-06-11 12:38 ` Alexander Frolkin
2013-06-11 20:13 ` Julian Anastasov
2013-06-12 10:49 ` Alexander Frolkin
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=51C85995.1060500@gmail.com \
--to=aleksey.chudov@gmail.com \
--cc=ja@ssi.bg \
--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.