Hi,
issue is also on Github at
https://github.com/openvswitch/ovs-issues/issues/175, added my comments.
Now will need help from somebody familiar with code - Openvswitch is
definitively not stable on Ubuntu Bionic and we can reproduce bug
easily, so any patching can be tested but need to figure out
Hi,
we have new lead at
https://github.com/openvswitch/ovs-issues/issues/175, which is pointing
to bug in glibc: https://sourceware.org/bugzilla/show_bug.cgi?id=23844
I will see on testing patch in our environment.
Best regards
Zdenek
On 27. 11. 19 17:32, Zdenek Janda wrote:
> Hi,
> issue is also
On Wed, Nov 27, 2019 at 7:22 PM taoyunupt wrote:
>
> Hi,
> My OVN cluster has 3 OVN-northd nodes, They are proxied by Haproxy
with a VIP. Recently, I restart OVN cluster frequently. One of the members
report the logs below.
> After read the code and paper of RAFT, it seems normal process
Hi,
My OVN cluster has 3 OVN-northd nodes, They are proxied by Haproxy with a
VIP. Recently, I restart OVN cluster frequently. One of the members report the
logs below.
After read the code and paper of RAFT, it seems normal process ,If the
follower does not find an entry in its log with
Hi,Han
Thanks for your reply. I think maybe we can disconnect the failed
follower from the Haproxy then synchronize the date, after all completed,
reconnect it to Haproxy again. But I do not know how to synchronize actually.
It is just my naive idea. Do you have some suggesti
