You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Anshum Gupta (JIRA)" <ji...@apache.org> on 2013/02/11 17:09:13 UTC

[jira] [Comment Edited] (SOLR-4425) Provide a way to change state of multiple shards atomically

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

Anshum Gupta edited comment on SOLR-4425 at 2/11/13 4:07 PM:
-------------------------------------------------------------

Possible API formats:

http://host:port/solr/admin/collections?action=UPDATESHARDSTATE&collection=<COLLECTION_NAME>&STATE1=<shard_1,shard_2>&STATE2=<shard_3,shard_4>
This would only handle acceptable shard states [STATE1/STATE2 = "active"] viz. "active" for now and we'd have to maintain this to cater to new states as and when introduced.

 OR
http://host:port/solr/admin/collections?action=UPDATESHARDSTATE&collection=<COLLECTION_NAME>&shard_1=<state1>&shard_2=<state2>
Anything other than collection name and action would be treated as possible <Shard, State> entry. We could either throw and exception and exit or just log an exception and continue in case of an invalid mapping.

I personally would prefer the later as it doesn't come with a maintenance overhead. Suggestions are welcome.
                
      was (Author: anshumg):
    Possible API formets:

http://host:port/solr/admin/collections?action=UPDATESHARDSTATE&<STATE1>=<shard_1,shard_2>&<STATE2>=<shard_3,shard_4>
This would only handle acceptable shard states viz. "active" for now and we'd have to maintain this to cater to new states as and when introduced.

 OR
http://host:port/solr/admin/collections?action=UPDATESHARDSTATE&shard_1=state1&shard_2=state2
Anything other than collection name and action would be treated as possible <Shard, State> entry. We could either throw and exception and exit or just log an exception and continue in case of an invalid mapping.

I personally would prefer the later as it doesn't come with a maintenance overhead. Suggestions are welcome.
                  
> Provide a way to change state of multiple shards atomically
> -----------------------------------------------------------
>
>                 Key: SOLR-4425
>                 URL: https://issues.apache.org/jira/browse/SOLR-4425
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Anshum Gupta
>            Assignee: Shalin Shekhar Mangar
>
> Provide a way to change state of multiple shards atomically perhaps through the Collection API.
> This command should take a map (in some format) of <Shard, State> and update the state of the Shards (Slice) to the corresponding state atomically.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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