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

Add a scheduled translog retention check #25622

Merged
merged 2 commits into from Jul 10, 2017

Conversation

Projects
None yet
3 participants
@bleskes
Copy link
Member

commented Jul 10, 2017

We currently check whether translog files can be trimmed whenever we create a new translog generation or close a view. However #25294 added a long translog retention period (12h, max 512MB by default), which means translog files should potentially be cleaned up long after there isn't any indexing activity to trigger flushes/the creation of new translog files. We therefore need a scheduled background check to clean up those files once they are no longer needed.

Relates to #10708

bleskes added some commits Jul 9, 2017

@s1monw

s1monw approved these changes Jul 10, 2017

Copy link
Contributor

left a comment

LGTM

@bleskes bleskes merged commit 09378f4 into elastic:master Jul 10, 2017

2 checks passed

CLA Commit author is a member of Elasticsearch
Details
elasticsearch-ci Build finished.
Details

@bleskes bleskes deleted the bleskes:translog_scheduled_trimming branch Jul 10, 2017

bleskes added a commit that referenced this pull request Jul 10, 2017

@clintongormley clintongormley added v6.0.0-beta1 and removed v6.0.0 labels Jul 25, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.