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

Exit cold flush early when there is nothing to merge #1780

Merged
merged 2 commits into from
Jun 27, 2019

Conversation

justinjc
Copy link
Collaborator

What this PR does / why we need it:

Currently, cold flushes happen unnecessarily because dirtySeriesToWrite contains empty seriesLists (since it is a shared resource between shards). Checking for data in dirtySeries is a sufficient condition in figuring out whether a merge should actually happen or not.

Special notes for your reviewer: N/A

Does this PR introduce a user-facing and/or backwards incompatible change?:

NONE

Does this PR require updating code package or user-facing documentation?:

NONE

Copy link
Contributor

@richardartoul richardartoul left a comment

Choose a reason for hiding this comment

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

Can you add a unit/regression test before merging?

@justinjc
Copy link
Collaborator Author

Sure thing, added one

@justinjc justinjc merged commit 645aba5 into master Jun 27, 2019
@justinjc justinjc deleted the juchan/merge-when-required branch June 27, 2019 01:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants