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
Comments
@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? |
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? |
Seems reasonable to me |
@mikemccand I see you pushed it, should this also go to 1.5? I think it should, no? |
@kimchy OK, I agree ... I'll push. |
This was fixed in 1.5.0 |
Per the recommendation here - http://www.elasticsearch.org/blog/performance-considerations-elasticsearch-indexing/ - can/should we set
index.translog.flush_threshold_size
to1g
by default in latest releases?The text was updated successfully, but these errors were encountered: