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

Use Lucene's defaults for CMS settings #5912

Closed
wants to merge 2 commits into from

Conversation

mikemccand
Copy link
Contributor

#5882

Lucene changed the settings a while back to be more conservative but ES has the old hardwired defaults.

@kimchy
Copy link
Member

kimchy commented Apr 22, 2014

LGTM, I suggest pushing to master and 1.x branches

@mikemccand
Copy link
Contributor Author

Thanks, Shay, will do...

Mike

http://blog.mikemccandless.com

On Tue, Apr 22, 2014 at 3:46 PM, Shay Banon notifications@github.comwrote:

LGTM, I suggest pushing to master and 1.x branches


Reply to this email directly or view it on GitHubhttps://github.com//pull/5912#issuecomment-41086618
.

@@ -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)));
Copy link
Contributor

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?

Copy link
Member

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woops, fixed!

@kimchy
Copy link
Member

kimchy commented Apr 22, 2014

LGTM

@mikemccand mikemccand self-assigned this Apr 23, 2014
@mikemccand mikemccand closed this Apr 23, 2014
@clintongormley clintongormley changed the title use Lucene's defaults for CMS settings Use Lucene's defaults for CMS settings Jun 8, 2015
@clintongormley clintongormley added >enhancement :Core/Infra/Core Core issues without another label labels Jun 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants