Turn off translog retention only when shard started #57063
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
dnhatn
added
>non-issue
:Distributed Indexing/Distributed
|
Pinging @elastic/es-distributed (:Distributed/Distributed) |
elasticmachine
added
the
Team:Distributed (Obsolete)
|
run elasticsearch-ci/default-distro |
ganeshlakshmi9
approved these changes
May 22, 2020
ywelsch
approved these changes
May 22, 2020
|
Thanks Yannick. |
dnhatn
added a commit
that referenced
this pull request
May 22, 2020
We should only turn off the translog retention when a shard is started; otherwise, we can issue unnecessary warn logs.
dnhatn
added a commit
that referenced
this pull request
May 22, 2020
We should only turn off the translog retention when a shard is started; otherwise, we can issue unnecessary warn logs.
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.
We should only turn off the translog retention when a shard is started; otherwise, we can issue unnecessary warn logs.