Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+Sync\s+issue\s+after\s+master\s+reboot\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+Sync\s+issue\s+after\s+master\s+reboot\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [lvs-users] Sync issue after master reboot (score: 1): Author: "Markhasin, Dan" <dan.markhasin@xxxxxxxxx>; Date: Tue, 25 Feb 2014 13:03:04 +0000; Thanks for the reply. Let me clarify, it doesn't stop synchronizing information after the reboot. The synchronization continues, but after the old master is rebooted its connections table is obviousl; /html/lvs-users/2014-02/msg00009.html (12,559 bytes)
2. Re: [lvs-users] Sync issue after master reboot (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Tue, 25 Feb 2014 10:25:45 +0200 (EET); Hello, Yes, there is no trigger implemented to sync all connections at once. But looking at the code I don't see why sync should stop transferring information. I don't know what kernel you are using; /html/lvs-users/2014-02/msg00008.html (11,037 bytes)
3. [lvs-users] Sync issue after master reboot (score: 1): Author: "Markhasin, Dan" <dan.markhasin@xxxxxxxxx>; Date: Wed, 12 Feb 2014 16:59:09 +0000; Hello, We are currently building an LVS cluster with two ldirector servers to ensure HA. Each of these servers has two ipvsadm 1.26 sync daemons running, which we start by: On master: --start-daemon; /html/lvs-users/2014-02/msg00004.html (9,736 bytes)

Current List: 1 - 3
Page: [1]