Hi :
I was able to go little further from log perspective with debug level and
see proper error:
However there were couple of changes that I did for current setup.
For controllers setup, since I am using 3 vms, to keep the specs in line
with current ovn scale env:
1. Increased the virtual memo
Thanks Numan:
Will also try to go little deep and see if we get little more hints by
increasing the log levels to debug and will wait for inputs from you and
Ben further . Hope we can find the culprit soon :)
Regards,
On Tue, Apr 17, 2018 at 12:13 AM, Numan Siddique
wrote:
>
>
> On Tue, Apr
On Tue, Apr 17, 2018 at 5:52 AM, aginwala wrote:
> Hi Ben/Numan:
>
>
> Just following up again. Let me know for any further
> improvements/suggestions on this.
>
>
Hi Aliasgar,
I need to educate myself first by studing raft and Ben's patches :). I
hope I will do it soon.
Thanks
Numan
> Reg
Hi Ben/Numan:
Just following up again. Let me know for any further
improvements/suggestions on this.
Regards,
On Mon, Apr 9, 2018 at 10:53 AM, aginwala wrote:
> Further Analysis indicates that cluster is not able to select a new leader
> and hence every node keeps retrying:
>
> ovn-northd l
Further Analysis indicates that cluster is not able to select a new leader
and hence every node keeps retrying:
ovn-northd logs around the same time on all three nodes complains about
disconnection from cluster and failing to choose leader
#Node1
2018-04-06T01:19:06.481Z|00466|ovn_northd|INFO|ov
Hi Ben/Numan:
So I went ahead to try out clustered db in scale env and results are not as
expected.
OVS branch used is master;
commit-id(2062840612904ff0873d46b2f4f226bc23f2296d)
Setup is uing 3 nodes.
Also disabled inactivity_probe,
ovn-nbctl --db="tcp:192.168.220.101:6641,tcp:192.168.220.102:6