Re: [ovs-dev] [PATCH] ovsdb: fix data loss when OVSDB replication from itself

2017-02-07 Thread Andy Zhou
On Mon, Feb 6, 2017 at 5:31 PM, 克赛号0181 wrote: > In K8S, Pacemaker is not used usally, we use keepalived to implement the VIP > (OVN service endpoint),when master nodes fails, the VIP switched earlier > than we notice such event, > so, the new master node will connect itself in a short time(about

Re: [ovs-dev] [PATCH] ovsdb: fix data loss when OVSDB replication from itself

2017-02-02 Thread Guru Shetty
On 31 January 2017 at 19:27, Guoshuai Li wrote: > > > This patch removes IP migration and OVSDB services to promote timing > dependency, which occurs at the master / slave exchange time and may not be > user-configurable. > If this dependency requires upper-level processing, not every cluster > p

Re: [ovs-dev] [PATCH] ovsdb: fix data loss when OVSDB replication from itself

2017-01-31 Thread Guoshuai Li
This patch removes IP migration and OVSDB services to promote timing dependency, which occurs at the master / slave exchange time and may not be user-configurable. If this dependency requires upper-level processing, not every cluster program can easily handle it. For example, building an OVSD

Re: [ovs-dev] [PATCH] ovsdb: fix data loss when OVSDB replication from itself

2017-01-31 Thread Andy Zhou
On Mon, Jan 2, 2017 at 7:09 PM, Guoshuai Li wrote: > Delete the local database after receiving the master data, > this is safer for data. > This patch is used by HA cluster that have no way to > control the order of resources, such as kubernetes. > > Signed-off-by: Guoshuai Li Sorry for the dela

[ovs-dev] [PATCH] ovsdb: fix data loss when OVSDB replication from itself

2017-01-02 Thread Guoshuai Li
Delete the local database after receiving the master data, this is safer for data. This patch is used by HA cluster that have no way to control the order of resources, such as kubernetes. Signed-off-by: Guoshuai Li --- ovsdb/replication.c | 73 +---