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

TEST: Ensure a manual flush always occur #36188

Merged
merged 6 commits into from
Dec 6, 2018
Merged

Conversation

dnhatn
Copy link
Member

@dnhatn dnhatn commented Dec 3, 2018

The test testLookupSeqNoByIdInLucene fails because it expects if any
change should be visible after a flush. However, that flush might be
ignored if the waitIfOngoing parameter is false (the default value), and
there is an ongoing flush triggered after merge is running.

Closes #35823

The test testLookupSeqNoByIdInLucene fails because it expects if any
change should be visible after a flush. However, that flush might be
ignored if the waitIfOngoing parameter is false (the default value), and
there is an ongoing flush triggered after merge is running.

Closes elastic#35823
@dnhatn dnhatn added >test Issues or PRs that are addressing/adding tests v7.0.0 :Distributed/Engine Anything around managing Lucene and the Translog in an open shard. v6.6.0 v6.5.3 labels Dec 3, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

Copy link
Contributor

@jpountz jpountz left a comment

Choose a reason for hiding this comment

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

Thanks @dnhatn!

This makes me wonder whether calling flush(true, false) makes any sense and whether we should disallow this combination or maybe replace these two booleans with an enum (eg. TRY_FLUSH (false, false), FLUSH_IF_CHANGES (false, true), FORCE_FLUSH (true, true))?

@dnhatn
Copy link
Member Author

dnhatn commented Dec 6, 2018

Thanks @jpountz. Your suggestion makes sense to me. I opened #36342.

@dnhatn dnhatn merged commit a7edf1e into elastic:master Dec 6, 2018
@dnhatn dnhatn deleted the test/lookup-id branch December 6, 2018 23:37
@dnhatn dnhatn added v6.5.3 and removed v6.5.3 labels Dec 6, 2018
dnhatn added a commit that referenced this pull request Dec 7, 2018
The test testLookupSeqNoByIdInLucene fails because it expects if any
change should be visible after a flush. However, that flush might be
ignored if the waitIfOngoing parameter is false (the default value), and
there is an ongoing flush triggered after merge is running.

Closes #35823
dnhatn added a commit that referenced this pull request Dec 7, 2018
The test testLookupSeqNoByIdInLucene fails because it expects if any
change should be visible after a flush. However, that flush might be
ignored if the waitIfOngoing parameter is false (the default value), and
there is an ongoing flush triggered after merge is running.

Closes #35823
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed/Engine Anything around managing Lucene and the Translog in an open shard. >test Issues or PRs that are addressing/adding tests v6.5.3 v6.6.0 v7.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants