-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
grpcproxy: TestLaunchDuplicateMemberShouldFail: unexpect successful launch #7267
Comments
Fix etcd-io#7267. In slow CPU machine, it often takes more than 10ms, so times out. Signed-off-by: Gyu-Ho Lee <[email protected]>
Fix etcd-io#7267. In slow CPU machine, it often takes more than 10ms, so times out. Signed-off-by: Gyu-Ho Lee <[email protected]>
Root cause: duplicate member launched and got Problem: it is possible that duplicate member's Assume this should fail with TCP port conflicts in regular set-up. Not sure how this is handled in unix ports. |
I feel like just bumping up the bootstrap time-out for tests is enough. Problem was all |
A member could have more than one ip/port so there won't be a bind conflict. Maybe split-brain issues if the member is killed, has its wal dir removed, then tries to boot as a new cluster while partitioned. This path needs some more testing... I'm thinking:
|
via https://jenkins-etcd-public.prod.coreos.systems/job/etcd-proxy/620/console
Possibly related to #7239
The text was updated successfully, but these errors were encountered: