Re: [ClusterLabs] [corosync] Virtual Synchrony Property guarantees in case of network partition

Hello Honza and others, It seems, Corosync is not reliable in network partition. Here is the test I ran: Process P1 on node N1 Process P2 on node N2 Process P3 on node N2 again When all the processes has joined the cluster, this is what happens: 1. P1 in one of its thread, continuously

Re: [ClusterLabs] [corosync] Virtual Synchrony Property guarantees in case of network partition

Thanks, really appreciate your help. On Mon, Jun 6, 2016 at 9:17 PM, Jan Friesse wrote: > But C1 is *guaranteed *to deliver *before *m(k)? No case where C1 is >> > > Yes > > delivered after m(k)? >> > > Nope. > > > >> >> Regards, >> Satish >> >> On Mon, Jun 6, 2016 at 8:10

Re: [ClusterLabs] [corosync] Virtual Synchrony Property guarantees in case of network partition

But C1 is *guaranteed *to deliver *before *m(k)? No case where C1 is Yes delivered after m(k)? Nope. Regards, Satish On Mon, Jun 6, 2016 at 8:10 PM, Jan Friesse wrote: satish kumar napsal(a): Hello honza, thanks for the response ! With state sync, I simply

Re: [ClusterLabs] [corosync] Virtual Synchrony Property guarantees in case of network partition

But C1 is *guaranteed *to deliver *before *m(k)? No case where C1 is delivered after m(k)? Regards, Satish On Mon, Jun 6, 2016 at 8:10 PM, Jan Friesse wrote: > satish kumar napsal(a): > > Hello honza, thanks for the response ! >> >> With state sync, I simply mean that

Re: [ClusterLabs] [corosync] Virtual Synchrony Property guarantees in case of network partition

Hello honza, thanks for the response ! With state sync, I simply mean that 'k-1' messages were delivered to N1, N2 and N3 and they have applied these messages to change their program state. N1.state = apply(m(k-1); N2.state = apply(m(k-1); N3.state = apply(m(k-1); The document you shared cleared

Re: [ClusterLabs] [corosync] Virtual Synchrony Property guarantees in case of network partition

Hi, Hello, Virtual Synchrony Property - messages are delivered in agreed order and configuration changes are delivered in agreed order relative to message. What happen to this property when network is partitioned the cluster into two. Consider following scenario (which I took from one of the

[ClusterLabs] [corosync] Virtual Synchrony Property guarantees in case of network partition

Hello, Virtual Synchrony Property - messages are delivered in agreed order and configuration changes are delivered in agreed order relative to message. What happen to this property when network is partitioned the cluster into two. Consider following scenario (which I took from one of the