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

Ignore translog retention policy if soft-deletes enabled #45868

Merged
merged 4 commits into from
Aug 22, 2019

Conversation

dnhatn
Copy link
Member

@dnhatn dnhatn commented Aug 22, 2019

Since #45136, we use soft-deletes instead of translog in peer recovery.
There's no need to retain extra translog to increase a chance of
operation-based recoveries. This commit ignores the translog retention
policy if soft-deletes is enabled so we can discard translog more
quickly.

Backport of #45473

Since elastic#45136, we use soft-deletes instead of translog in peer recovery.
There's no need to retain extra translog to increase a chance of
operation-based recoveries. This commit ignores the translog retention
policy if soft-deletes is enabled so we can discard translog more
quickly.

Co-authored-by: David Turner <[email protected]>

Relates elastic#45136
If soft-deletes is enabled, we will trim translog above the local
checkpoint of the safe commit immediately. However, if the translog
durability is async, the last commit might not be the safe commit as the
local checkpoint won't advance until translog is synced. Therefore, we
need to verify translog stats busily.

Closes elastic#45801
Relates elastic#45473
@dnhatn dnhatn merged commit 3393f95 into elastic:7.x Aug 22, 2019
@dnhatn dnhatn deleted the 7x-translog-policy branch August 22, 2019 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant