Skip to content
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.

Sign up for GitHub

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

Jump to bottom

FAILED: DowningClusteredTests.test_stopLeader_by_leaveSelfNode_shouldPropagateToOtherNodes #1018

Open
ktoso opened this issue Jul 20, 2022 · 0 comments
Open

FAILED: DowningClusteredTests.test_stopLeader_by_leaveSelfNode_shouldPropagateToOtherNodes #1018

ktoso opened this issue Jul 20, 2022 · 0 comments
Labels
failed 💥 Failed tickets are CI or benchmarking failures, should be investigated as soon as possible

Comments

@ktoso
Copy link
Member

ktoso commented Jul 20, 2022 


21:43:00 <EXPR>:0: error: DowningClusteredTests.test_stopLeader_by_leaveSelfNode_shouldPropagateToOtherNodes : threw error "
21:43:00         try await self.joinNodes(node: first, with: second, ensureMembers: .up)
21:43:00                          ^~~~~~
21:43:00 error: MembershipError(awaitStatusTimedOut(20.0 seconds, Optional(DistributedActors.Cluster.MembershipError.statusRequirementNotMet(expected: DistributedActors.Cluster.MemberStatus.up, found: Member(sact://second:[email protected]:9002, status: joining, reachability: reachable)))), details: No result within 20s. Last error: statusRequirementNotMet(expected: DistributedActors.Cluster.MemberStatus.up, found: Member(sact://second:[email protected]:9002, status: joining, reachability: reachable)))"

Saw the same issue in #1016 and I suspect sometimes the node may have hiccups and take longer to join nodes... we should give it a bigger timeout I suppose -- and also measure average time it takes to join nodes, then we'll see if we have hiccups or not.
@ktoso ktoso mentioned this issue Jul 20, 2022
Merged
@ktoso ktoso added the failed 💥 Failed tickets are CI or benchmarking failures, should be investigated as soon as possible label Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failed 💥 Failed tickets are CI or benchmarking failures, should be investigated as soon as possible
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ktoso