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.

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

Give more time to AutoFollowIT tests #51938

Merged
merged 1 commit into from Feb 5, 2020
Merged

Conversation

tlrx
Copy link
Member

@tlrx tlrx commented Feb 5, 2020

AutoFollowIT tests are regularly failing on CI because they rely on how cluster state updates are processed within the integration clusters. We tried to limit this in #49141 by moving to latches instead of waiting for assertions to pass but there are still some places were it still need to wait for the cluster state updates to be processed and auto-follow stats to be updated.

This PR gives more time to assertBusy() that verifies the AutoFollowStats (up to 60 seconds) and also always log the auto-follow stats in case the assertions failed.

Closes #48982

@tlrx tlrx added >test Issues or PRs that are addressing/adding tests :Distributed/CCR Issues around the Cross Cluster State Replication features v8.0.0 v7.7.0 v7.6.1 labels Feb 5, 2020
@tlrx tlrx requested a review from dnhatn February 5, 2020 12:54
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (:Distributed/CCR)

Copy link
Member

@dnhatn dnhatn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks Tanguy.

@tlrx tlrx merged commit e856734 into elastic:master Feb 5, 2020
@tlrx tlrx deleted the auto-follow-it branch February 5, 2020 14:52
@tlrx
Copy link
Member Author

tlrx commented Feb 5, 2020

Thanks Nhat!

tlrx added a commit that referenced this pull request Feb 5, 2020
AutoFollowIT tests are regularly failing on CI because they rely 
on how cluster state updates are processed within the integration 
clusters. We tried to limit this in #49141 by moving to latches 
instead of waiting for assertions to pass but there are still some 
places were it still need to wait for the cluster state updates to 
be processed and auto-follow stats to be updated.

This commit gives more time to assertBusy() that verifies the 
AutoFollowStats (up to 60 seconds) and also always log the 
auto-follow stats in case the assertions failed.

Closes #48982
tlrx added a commit that referenced this pull request Feb 5, 2020
AutoFollowIT tests are regularly failing on CI because they rely 
on how cluster state updates are processed within the integration 
clusters. We tried to limit this in #49141 by moving to latches 
instead of waiting for assertions to pass but there are still some 
places were it still need to wait for the cluster state updates to 
be processed and auto-follow stats to be updated.

This commit gives more time to assertBusy() that verifies the 
AutoFollowStats (up to 60 seconds) and also always log the 
auto-follow stats in case the assertions failed.

Closes #48982
@polyfractal polyfractal added v7.6.0 and removed v7.6.1 labels Feb 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/CCR Issues around the Cross Cluster State Replication features >test Issues or PRs that are addressing/adding tests v7.6.0 v7.7.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AutoFollowIT#testPauseAndResumeWithMultipleAutoFollowPatterns failing
5 participants