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

Update default value for index.translog.flush_threshold_size #9265

Closed
markwalkom opened this issue Jan 13, 2015 · 6 comments
Closed

Update default value for index.translog.flush_threshold_size #9265

markwalkom opened this issue Jan 13, 2015 · 6 comments

Comments

@markwalkom
Copy link
Contributor

Per the recommendation here - http://www.elasticsearch.org/blog/performance-considerations-elasticsearch-indexing/ - can/should we set index.translog.flush_threshold_size to 1g by default in latest releases?

@clintongormley
Copy link

@markwalkom not sure it is always appropriate. It increases indexing throughput, but also increases recovery time in case of shard failure.

@mikemccand what do you think?

@mikemccand
Copy link
Contributor

That's a good point (higher recovery time); the blog post should have mentioned that tradeoff. It does also mean added disk usage.

But then, fsync is often quite costly on the IO system, and if you are indexing with enough client side concurrency, you can burn through 200 MB quickly enough (I've seen that equate to ~ 5 seconds wall clock time). Maybe we should increase to 500 MB?

@clintongormley
Copy link

Seems reasonable to me

@kimchy
Copy link
Member

kimchy commented Jan 20, 2015

@mikemccand I see you pushed it, should this also go to 1.5? I think it should, no?

@mikemccand
Copy link
Contributor

@kimchy OK, I agree ... I'll push.

@mikemccand
Copy link
Contributor

This was fixed in 1.5.0

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

Successfully merging a pull request may close this issue.

6 participants