Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*IPVS\s+Health\s+Checking\s+Best\s+Practices\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*IPVS\s+Health\s+Checking\s+Best\s+Practices\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: IPVS Health Checking Best Practices (score: 1): Author: Alexey Andriyanov <alan@xxxxxxxxxx>; Date: Fri, 19 Sep 2014 08:31:05 +0400; Hi, Alex. We use tunnel checks to the host itself. The encapsulated packet looks like this: CHK_SRC -> RS1 [ (IPIP) CHK_SRC -> VIP1 ]. This could be done without maintaining iptables rules or tunnel; /html/lvs-devel/2014-09/msg00087.html (10,832 bytes)
2. IPVS Health Checking Best Practices (score: 1): Author: Alex Gartrell <agartrell@xxxxxx>; Date: Thu, 18 Sep 2014 14:26:58 -0700; Hello All, Today, we run IPVS on a number of hosts. Each of these hosts has a python process responsible for ensuring the health of pool members and then updating their weights as necessary. We do th; /html/lvs-devel/2014-09/msg00086.html (9,977 bytes)

Current List: 1 - 2
Page: [1]