Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+source\s+hashing\s+some\s+times\s+land\s+on\s+wrong\s+server\s+\(with\s+FTP\)\s*$/: 7 ]

Total 7 documents matching your query.

1. Re: [lvs-users] source hashing some times land on wrong server (with FTP) (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 6 Nov 2019 01:08:17 +0200 (EET)
Hello, No, this flag helps the backup server to run as real server by ignoring the steps that IPVS does to lookup and create connections. The packets are simply passed to the local stack without any
/html/lvs-users/2019-11/msg00006.html (11,474 bytes)

2. Re: [lvs-users] source hashing some times land on wrong server (with FTP) (score: 1)
Author: Phillip Moore <pdm@xxxxxxxxx>
Date: Mon, 4 Nov 2019 14:48:11 -0600
Julian, Thank you for the response. I'm not quite sure I understand though or maybe I did not express our setup clearly. We have a set of director hosts that are all active (running master and backup
/html/lvs-users/2019-11/msg00005.html (14,007 bytes)

3. Re: [lvs-users] source hashing some times land on wrong server (with FTP) (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Mon, 4 Nov 2019 22:21:39 +0200 (EET)
Hello, Try to set the backup_only sysctl var to 1 on all directors that are backup servers and that can be used also as real servers. The flag can stay to 1 even while director runs as master. For th
/html/lvs-users/2019-11/msg00004.html (12,794 bytes)

4. Re: [lvs-users] source hashing some times land on wrong server (with FTP) (score: 1)
Author: Malcolm Turnbull <malcolm@xxxxxxxxxxxxxxxx>
Date: Fri, 1 Nov 2019 19:30:37 +0000
Phillip, I'm not sure why the SH scheduler is not working for you, but I'm pretty certain that if you just remove it and use WLC with persistence then you should get the desired result. i.e. -A -t x.
/html/lvs-users/2019-11/msg00003.html (15,762 bytes)

5. Re: [lvs-users] source hashing some times land on wrong server (with FTP) (score: 1)
Author: Phillip Moore <pdm@xxxxxxxxx>
Date: Fri, 1 Nov 2019 13:40:20 -0500
On Fri, Nov 1, 2019 at 12:39 PM Malcolm Turnbull <malcolm@xxxxxxxxxxxxxxxx> wrote: There do not seem to be any health check failures that correspond with the incident. That was my thought to especial
/html/lvs-users/2019-11/msg00002.html (13,365 bytes)

6. Re: [lvs-users] source hashing some times land on wrong server (with FTP) (score: 1)
Author: Malcolm Turnbull <malcolm@xxxxxxxxxxxxxxxx>
Date: Fri, 1 Nov 2019 17:38:02 +0000
Phillip, Are you getting any health check failures? It's not a consistent hash - so any config changes would throw it. Why not just use the standard persistence table? The stick table for that is com
/html/lvs-users/2019-11/msg00001.html (11,632 bytes)

7. [lvs-users] source hashing some times land on wrong server (with FTP) (score: 1)
Author: Phillip Moore <pdm@xxxxxxxxx>
Date: Fri, 1 Nov 2019 10:48:50 -0500
Hello! We have FTP setup with on its own VIP and just map all ports (:0) and use source hashing. Sometimes when the FTP client opens the data channel it will land on the wrong real server causing a r
/html/lvs-users/2019-11/msg00000.html (9,211 bytes)


This search system is powered by Namazu