-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Update retention policy before saving database #1564
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Without this change, new shard group information is not persisted in the metastore and only when the next database-save took place would this update be persisted. If the server shutdown before the update, the new shard group would be lost.
Green build. |
I have updated the unit tests so it explicitly tests that shard groups are persisted to disk after a restart. With this change in place, I am now seeing this failure:
so this change may have brought out something else. |
otoolep
force-pushed
the
persist_policies
branch
from
February 11, 2015 04:32
5661851
to
f87d974
Compare
The shards aren't being closed in |
Shipt it from @benbjohnson |
otoolep
added a commit
that referenced
this pull request
Feb 11, 2015
Update retention policy before saving database
mark-rushakoff
pushed a commit
that referenced
this pull request
Jan 11, 2019
add run return to rerun
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without this change, new shard group information is not persisted in the
metastore and only when the next database-save took place would this
update be persisted. If the server shutdown before the update, the new
shard group would be lost.