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

Orchestrator analysis-locked-hypothesis test is unstable #1464

Open
kamil-holubicki opened this issue Dec 29, 2022 · 0 comments
Open

Orchestrator analysis-locked-hypothesis test is unstable #1464

kamil-holubicki opened this issue Dec 29, 2022 · 0 comments

Comments

@kamil-holubicki
Copy link

analysis-locked-hypothesis test works fine locally, but it often fails when run by automation which uses AWS instances.
kamil-holubicki added a commit to kamil-holubicki/orchestrator-openark-fork that referenced this issue Dec 29, 2022
@kamil-holubicki
Orchestrator analysis-locked-hypothesis test is unstable
5122a0a 
openark#1464

Problem:
analysis-locked-hypothesis test is unstable

Cause:
By default instance is polled every 5 seconds, but we wait only for
2 seconds, so it may happen that instance is not polled before we
get the analysis result.

Solution:
Wait for 7 seconds after disabling instance. It is 7 because it has
to be > 5 but LockedSemiSyncMasterHypothesis is reported only within
6 secs window (InstancePollSeconds + ReasonableInstanceCheckSeconds),
then it switches to LockedSemiSyncMaster status.
@kamil-holubicki kamil-holubicki mentioned this issue Dec 29, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kamil-holubicki