lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Updated] (SOLR-6491) Umbrella JIRA for managing the leader assignments
Date Tue, 16 Sep 2014 17:38:34 GMT


Erick Erickson updated SOLR-6491:
    Summary: Umbrella JIRA for managing the leader assignments  (was: Add preferredLeader
as a ROLE and a collections API command to respect this role)

> Umbrella JIRA for managing the leader assignments
> -------------------------------------------------
>                 Key: SOLR-6491
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.11, 5.0
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
> Leaders can currently get out of balance due to the sequence of how nodes are brought
up in a cluster. For very good reasons shard leadership cannot be permanently assigned.
> However, it seems reasonable that a sys admin could optionally specify that a particular
node be the _preferred_ leader for a particular collection/shard. During leader election,
preference would be given to any node so marked when electing any leader.
> So the proposal here is to add another role for preferredLeader to the collections API,
something like
> ADDROLE?role=preferredLeader&collection=collection_name&shard=shardId
> Second, it would be good to have a new collections API call like ELECTPREFERREDLEADERS?collection=collection_name
> (I really hate that name so far, but you see the idea). That command would (asynchronously?)
make an attempt to transfer leadership for each shard in a collection to the leader labeled
as the preferred leader by the new ADDROLE role.
> I'm going to start working on this, any suggestions welcome!
> This will subsume several other JIRAs, I'll link them momentarily.

This message was sent by Atlassian JIRA

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

View raw message