lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-5476) Overseer Role for nodes
Date Thu, 16 Jan 2014 16:26:20 GMT


ASF subversion and git services commented on SOLR-5476:

Commit 1558846 from [~noble.paul] in branch 'dev/trunk'
[ ]

SOLR-5476 removing forbidden API usage

> Overseer Role for nodes
> -----------------------
>                 Key: SOLR-5476
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>             Fix For: 5.0, 4.7
>         Attachments: SOLR-5476.patch, SOLR-5476.patch, SOLR-5476.patch, SOLR-5476.patch,
> 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=addrole&role=overseer&node=
> This results in the creation of a entry in the /roles.json in ZK which would look like
the following
> {code:javascript}
> {
> "overseer" : [""]
> }
> {code}
> If a node is designated for overseer it gets preference over others when overseer election
takes place. If no designated servers are available another random node would become the Overseer.
> Later on, if one of the designated nodes are brought up ,it would take over the Overseer
role from the current Overseer to become the Overseer of the system

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message