[ 
https://issues.apache.org/jira/browse/SOLR-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shalin Shekhar Mangar updated SOLR-4693:
----------------------------------------

    Fix Version/s: 4.4
      Description: 
A collections API that unloads all replicas of a given shard and then removes 
it from the cluster state.

It will remove only those shards which are INACTIVE or have no range (created 
for custom sharding)

Among other places, this would be useful post the shard split call to manage 
the parent/original shard.

  was:
Have a collections API that cleans up a given shard.
Among other places, this would be useful post the shard split call to manage 
the parent/original slice.

          Summary: Create a collections API to delete/cleanup a shard  (was: 
Create a collections API to delete/cleanup a Slice)
    
> Create a collections API to delete/cleanup a shard
> --------------------------------------------------
>
>                 Key: SOLR-4693
>                 URL: https://issues.apache.org/jira/browse/SOLR-4693
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Anshum Gupta
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 4.4
>
>         Attachments: SOLR-4693.patch, SOLR-4693.patch, SOLR-4693.patch, 
> SOLR-4693.patch, SOLR-4693.patch
>
>
> A collections API that unloads all replicas of a given shard and then removes 
> it from the cluster state.
> It will remove only those shards which are INACTIVE or have no range (created 
> for custom sharding)
> Among other places, this would be useful post the shard split call to manage 
> the parent/original shard.

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to