lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-6517) CollectionsAPI call REBALANCELEADERS
Date Mon, 03 Nov 2014 16:33:33 GMT

    [ https://issues.apache.org/jira/browse/SOLR-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194701#comment-14194701
] 

Noble Paul commented on SOLR-6517:
----------------------------------

Unfortunately, solrcloud failures are hard to reproduce and fix. We need to put extra care
while making changes to  cloud . I've spent weeks debugging three overseer roles feature because
it only failed in our 120 node cluster (never in the junit tests) 

> CollectionsAPI call REBALANCELEADERS
> ------------------------------------
>
>                 Key: SOLR-6517
>                 URL: https://issues.apache.org/jira/browse/SOLR-6517
>             Project: Solr
>          Issue Type: New Feature
>    Affects Versions: 5.0, Trunk
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>             Fix For: 5.0, Trunk
>
>         Attachments: SOLR-6517.patch, SOLR-6517.patch, SOLR-6517.patch
>
>
> Perhaps the final piece of SOLR-6491. Once the preferred leadership roles are assigned,
there has to be a command "make it so Mr. Solr". This is something of a placeholder to collect
ideas. One wouldn't want to flood the system with hundreds of re-assignments at once. Should
this be synchronous or asnych? Should it make the best attempt but not worry about perfection?
Should it???
> a collection=name parameter would be required and it would re-elect all the leaders that
were on the 'wrong' node
> I'm thinking an optionally allowing one to specify a shard in the case where you wanted
to make a very specific change. Note that there's no need to specify a particular replica,
since there should be only a single preferredLeader per slice.
> This command would do nothing to any slice that did not have a replica with a preferredLeader
role. Likewise it would do nothing if the slice in question already had the leader role assigned
to the node with the preferredLeader role.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message