-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Campaign API throws different exceptions in same scenario #1131
Comments
@KuZon do you have time to work on a PR ? |
Yes, please guide. I can spend some time. |
@lburgazzoli any update on this ? |
No sorry, I don't have much time at this stage. A PR would be more than welcome |
@KuZon can you provide instructions to reproduce this problem consistently ? |
@KuZon there have been some subtle changes in recent etcd version which should have been fixed. |
Have some code for reproduce it would be great. |
@KuZon any feedback ? this is issue will be closed soon without any feedback |
@KuZon ping |
Versions
Describe the bug
campaignResponse = electionClient.campaign(electionName, leaseId, proposal) .get(writeTimeOut, TimeUnit.SECONDS);
There is a leader already available for given electionName. We are doing this call as part of our code from another identical instance, sometimes it throws
TimeoutException
and some thing an exception which containsetcdserver: invalid auth token
. Before upgrading to server 3.5.9 , it was consistently throwingTimeoutException
. ITo Reproduce
In two separate programs, run above line. One after another, some times it will throw timeout and sometimes invalid auth token error
Expected behavior
This should be supported from client in a better way to understand if there is a server error or we are just timing out as there is a leader already available.
The text was updated successfully, but these errors were encountered: