You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2013/11/20 15:37:36 UTC
[jira] [Created] (SOLR-5476) Roles per node
Noble Paul created SOLR-5476:
--------------------------------
Summary: Roles per node
Key: SOLR-5476
URL: https://issues.apache.org/jira/browse/SOLR-5476
Project: Solr
Issue Type: Sub-task
Reporter: Noble Paul
In a very large cluster the OverSeer is likely to be overloaded.If the same node is a serving a few other shards it can lead to OverSeer getting slowed down due to GC pauses , or simply too much of work . If the cluster is really large , it is possible to dedicate high end h/w for OverSeers
It works as a new collection admin command
command=assignRole&whitelist=overseer&blacklist=leader&blacklist=replica&node=node_name
If a node is whitelisted for overseer it gets preference over others when overseer election takes place. If no whitelisted servers are available another random node will be picked up
if the node is blacklisted for leade/replica , it won't be assigned any new shards
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: (SOLR-5476) Overseer Role for nodes
Posted by Michael McCandless <lu...@mikemccandless.com>.
On Fri, Jan 17, 2014 at 3:09 AM, ASF subversion and git services
(JIRA) <ji...@apache.org> wrote:
> PLEASE RUN "ant precommit" (root) or alternatively the faster "ant check-forbidden-apis" (in your module folder) before committing!
And also try to watch out for build failures for a few hours after you
commit ...
Mike McCandless
http://blog.mikemccandless.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org