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

Optimization: Only save changed index ranges #1412

Merged
merged 1 commit into from Sep 10, 2015

Conversation

Projects
None yet
2 participants
@joschi
Contributor

joschi commented Sep 10, 2015

In order to prevent potentially long-running cluster-level operations (like setting a write block on an index), the EsIndexRangeService#save() method now checks, whether an identical index range has already been stored for the index and skips saving the new but identical index range in this case.

Only save changed index ranges
In order to prevent potentially long-running cluster-level operations (like
setting a write block on an index), the EsIndexRangeService#save() method
now checks, whether an identical index range has already been stored for the
index and skips saving the new but identical index range in this case.

@joschi joschi added this to the 1.2.0 milestone Sep 10, 2015

kroepke added a commit that referenced this pull request Sep 10, 2015

Merge pull request #1412 from Graylog2/index-range-save-optimization
Optimization: Only save changed index ranges

@kroepke kroepke merged commit b99311d into 1.2 Sep 10, 2015

3 checks passed

ci Jenkins build graylog2-server-integration-pr 224 has succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@kroepke kroepke deleted the index-range-save-optimization branch Sep 10, 2015

@kroepke

This comment has been minimized.

Member

kroepke commented Sep 10, 2015

🎅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment