Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
etcd client missing a watch update. #9107
I have 3 etcd clients configured with all the 3 etcd server endpoints.
The key put operation was done at timestamp
In order to debug this issue I had added a debug statement in etcd clientv3's balancer code to print the last pinned etcd server address.
An interesting log line I found on 169 was this
The above timestamp lies within our 30 seconds timeout where we expect the update.
Any help will be much appreciated.
I am not able to reproduce this issue consistently, may be 2 out of 10 times.
No. It should not be related. Also I should suggest you try latest 3.2.13 release.…
On Fri, Jan 5, 2018 at 6:58 PM adityadani ***@***.***> wrote: @xiang90 <https://github.com/xiang90> Sure. Let me do that. On a side note, can high fsync latency on a node cause such missed watch updates? Or are they completely unrelated — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9107 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AERbyyBke_DsxDBqKMUTGkXiSNAsVS5hks5tHuE6gaJpZM4RVKZ8> .