Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+ipvs\:\s+Fix\s+reuse\s+connection\s+if\s+RS\s+weight\s+is\s+0\s*$/: 8 ]

Total 8 documents matching your query.

1. Re: [PATCH] ipvs: Fix reuse connection if RS weight is 0 (score: 1)
Author: yangxingwu <xingwu.yang@xxxxxxxxx>
Date: Thu, 28 Oct 2021 10:50:00 +0800
hello The problem is we can NOT decide what the customers do, many of them run kubernetes with old versions of kube-proxy. And most importantly, upgrade to new version is a very long and painful proc
/html/lvs-devel/2021-10/msg00031.html (12,407 bytes)

2. Re: [PATCH] ipvs: Fix reuse connection if RS weight is 0 (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Thu, 28 Oct 2021 00:09:09 +0300 (EEST)
Hello, My concern is with the behaviour people expect from each sysctl var: conn_reuse_mode decides if port reuse is considered for rescheduling and expire_nodest_conn should have priority only for u
/html/lvs-devel/2021-10/msg00030.html (11,324 bytes)

3. Re: [PATCH] ipvs: Fix reuse connection if RS weight is 0 (score: 1)
Author: yangxingwu <xingwu.yang@xxxxxxxxx>
Date: Wed, 27 Oct 2021 09:43:31 +0800
Julian what we want is if RS weight is 0, then no new connections should be served even if conn_reuse_mode is 0, just as commit dc7b3eb900aa ("ipvs: Fix reuse connection if real server is dead") tryi
/html/lvs-devel/2021-10/msg00029.html (15,484 bytes)

4. Re: [PATCH] ipvs: Fix reuse connection if RS weight is 0 (score: 1)
Author: yangxingwu <xingwu.yang@xxxxxxxxx>
Date: Tue, 26 Oct 2021 14:13:48 +0800
thanks Julian yes, I know that the one-second delay issue has been fixed by commit f0a5e4d7a594e0fe237d3dfafb069bb82f80f42f if we set conn_reuse_mode to 1 BUT it's still NOT what we expected with sys
/html/lvs-devel/2021-10/msg00028.html (14,293 bytes)

5. Re: [PATCH] ipvs: Fix reuse connection if RS weight is 0 (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Tue, 26 Oct 2021 08:44:28 +0300 (EEST)
Hello, Yes, this is expected when conn_reuse_mode=0. What happens if you try conn_reuse_mode=1? The one-second delay in previous kernels should be corrected with ipvs: allow connection reuse for unco
/html/lvs-devel/2021-10/msg00027.html (13,053 bytes)

6. Re: [PATCH] ipvs: Fix reuse connection if RS weight is 0 (score: 1)
Author: yangxingwu <xingwu.yang@xxxxxxxxx>
Date: Tue, 26 Oct 2021 10:54:40 +0800
thanks julian What happens in this situation is that if we set the wait of the realserver to 0 and do NOT remove the weight zero realserver with sysctl settings (conn_reuse_mode == 0 && expire_nodest
/html/lvs-devel/2021-10/msg00026.html (15,309 bytes)

7. Re: [PATCH] ipvs: Fix reuse connection if RS weight is 0 (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Mon, 25 Oct 2021 21:12:33 +0300 (EEST)
Hello, Your change does not look correct to me. At the time expire_nodest_conn was created, it was not checked when weight is 0. At different places different terms are used but in short, we have two
/html/lvs-devel/2021-10/msg00025.html (13,629 bytes)

8. [PATCH] ipvs: Fix reuse connection if RS weight is 0 (score: 1)
Author: yangxingwu <xingwu.yang@xxxxxxxxx>
Date: Mon, 25 Oct 2021 19:59:10 +0800
Since commit dc7b3eb900aa ("ipvs: Fix reuse connection if real server is dead"), new connections to dead servers are redistributed immediately to new servers. Then commit d752c3645717 ("ipvs: allow r
/html/lvs-devel/2021-10/msg00024.html (11,364 bytes)


This search system is powered by Namazu