Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+Understanding\s+granularity\,\s+timeouts\s+and\s+unexpected\s+balance\s+of\s+traffic\s+on\s+reals\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+Understanding\s+granularity\,\s+timeouts\s+and\s+unexpected\s+balance\s+of\s+traffic\s+on\s+reals\s*$/: 7 ]

Total 7 documents matching your query.

1. Re: [lvs-users] Understanding granularity, timeouts and unexpected balance of traffic on reals (score: 1): Author: Abhijeet Rastogi <abhijeet.1989@xxxxxxxxx>; Date: Thu, 29 Aug 2019 11:01:56 -0700; HI Julian, Thanks for the information. I was using keepalived-1.3.5-8.el7_6.x86_64 to manage ipvsadm settings and that seems to be not doing the right thing and respecting configs. persistence_granul; /html/lvs-users/2019-08/msg00013.html (14,426 bytes)
2. Re: [lvs-users] Understanding granularity, timeouts and unexpected balance of traffic on reals (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Tue, 27 Aug 2019 10:11:33 +0300 (EEST); Hello, Yes, it is hardcoded in ip_vs_conn_expire() and can not be disabled because we know only the count of connections that have pointer to the template (n_control), the template has no list of the; /html/lvs-users/2019-08/msg00012.html (12,916 bytes)
3. Re: [lvs-users] Understanding granularity, timeouts and unexpected balance of traffic on reals (score: 1): Author: Abhijeet Rastogi <abhijeet.1989@xxxxxxxxx>; Date: Mon, 26 Aug 2019 15:11:41 -0700; Hi Julian, I still wanted to understand this behavior more. You mentioned:- ``` When the timer expires it can be extended each time with new 60 seconds if there are existing connections (even if not; /html/lvs-users/2019-08/msg00011.html (17,349 bytes)
4. Re: [lvs-users] Understanding granularity, timeouts and unexpected balance of traffic on reals (score: 1): Author: Abhijeet Rastogi <abhijeet.1989@xxxxxxxxx>; Date: Mon, 26 Aug 2019 14:05:57 -0700; Hi Julian, Thanks for taking a look. it would be a bug if connections from same subnet go to different real servers. I can confirm that traffic is coming to only one virtual service. Column 5 on "sud; /html/lvs-users/2019-08/msg00010.html (15,119 bytes)
5. Re: [lvs-users] Understanding granularity, timeouts and unexpected balance of traffic on reals (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Sun, 25 Aug 2019 13:28:37 +0300 (EEST); Hello, Yes, if they are for same virtual service. Otherwise, it would be a bug if connections from same subnet go to different real servers. I'm not sure how many virtual servers you are using. Pleas; /html/lvs-users/2019-08/msg00009.html (12,503 bytes)
6. Re: [lvs-users] Understanding granularity, timeouts and unexpected balance of traffic on reals (score: 1): Author: Abhijeet Rastogi <abhijeet.1989@xxxxxxxxx>; Date: Sat, 24 Aug 2019 18:58:38 -0700; Hi everyone, Bump. Can anyone help with why IPVS is not respecting the subnet persistence granularity? Thanks, Abhijeet On Thu, Aug 15, 2019 at 1:11 PM Abhijeet Rastogi <abhijeet.1989@xxxxxxxxx> wrot; /html/lvs-users/2019-08/msg00008.html (11,770 bytes)
7. [lvs-users] Understanding granularity, timeouts and unexpected balance of traffic on reals (score: 1): Author: Abhijeet Rastogi <abhijeet.1989@xxxxxxxxx>; Date: Thu, 15 Aug 2019 13:11:00 -0700; Hi everyone, I'm investigating a typical configuration for an L4 TCP load balancer using ipvs+keepalived. Settings:- persistence_timeout: 120 seconds. (# LVS persistence timeout, sec) /sbin/ipvsadm -; /html/lvs-users/2019-08/msg00004.html (10,761 bytes)

Current List: 1 - 7
Page: [1]