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.

Sign up for GitHub

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

Jump to bottom

Core: use Lucene's defaults for compound-file-format (CFS) #8919

Closed
mikemccand opened this issue Dec 12, 2014 · 1 comment
Closed

Core: use Lucene's defaults for compound-file-format (CFS) #8919

mikemccand opened this issue Dec 12, 2014 · 1 comment
Assignees
@mikemccand
Labels
v1.5.0 v2.0.0-beta1

Comments

@mikemccand
Copy link
Contributor

Lucene's defaults do a good job with CFS: tiny segments use CFS, and large segments don't.

But in ES we never use CFS for merged segments, risking file descriptor exhaustion.

I think we should just use Lucene's defaults here?
@mikemccand mikemccand self-assigned this Dec 12, 2014
@s1monw
Copy link
Contributor

s1monw commented Dec 12, 2014

+1

@mikemccand mikemccand mentioned this issue Dec 12, 2014
Closed
mikemccand added a commit that referenced this issue Dec 12, 2014
@mikemccand
Core: use compound file by default for merged segments < 10% of index…
287a1ba 
… size

Change Elasticsearch to use Lucene's defaults, to reduce file descriptor count.

Closes #8934

Closes #8919
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikemccand mikemccand

Labels
v1.5.0 v2.0.0-beta1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use Lucene's defaults for compound file format mikemccand/elasticsearch
2 participants
@mikemccand @s1monw