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
Use Lucene's defaults for CMS settings #5912
Conversation
LGTM, I suggest pushing to master and 1.x branches |
Thanks, Shay, will do... Mike http://blog.mikemccandless.com On Tue, Apr 22, 2014 at 3:46 PM, Shay Banon notifications@github.comwrote:
|
@@ -52,9 +53,8 @@ | |||
public ConcurrentMergeSchedulerProvider(ShardId shardId, @IndexSettings Settings indexSettings, ThreadPool threadPool) { | |||
super(shardId, indexSettings, threadPool); | |||
|
|||
// TODO LUCENE MONITOR this will change in Lucene 4.0 | |||
this.maxThreadCount = componentSettings.getAsInt("max_thread_count", Math.max(1, Math.min(3, Runtime.getRuntime().availableProcessors() / 2))); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait - we don't allow to change it anymore? why don't we just pass the defaults to the componentSettings?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
argh, I left that comment, but seems to have been lost by github, yea, we need to keep those configurable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Woops, fixed!
…ults to Lucene's
LGTM |
#5882
Lucene changed the settings a while back to be more conservative but ES has the old hardwired defaults.