Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+clarification\s+of\s+sync_threshold\s+and\s+sync_refresh_period\s+for\s+active\/active\s+director\s+setups\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [lvs-users] clarification of sync_threshold and sync_refresh_period for active/active director setups (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Thu, 21 Jun 2018 23:57:19 +0300 (EEST)
Hello, There is a sloppy_tcp sysctl var that allows creating connections from non-SYN packets. We have here sync_threshold and sync_period. The first is packet ID (1 .. sync_period-1 or 0), the secon
/html/lvs-users/2018-06/msg00019.html (13,315 bytes)

2. [lvs-users] clarification of sync_threshold and sync_refresh_period for active/active director setups (score: 1)
Author: Phillip Moore <pdm@xxxxxxxxx>
Date: Wed, 20 Jun 2018 21:38:39 -0500
Hi, I'm trying to understand some behavior we are seeing. We run a group of IPVS director nodes all active with BGP for advertising their addresses and every IPVS node is running both the master and
/html/lvs-users/2018-06/msg00018.html (9,864 bytes)


This search system is powered by Namazu