Thanks Shalin, Shawn.
I ended up getting guidance from Anshum on this and we did indeed use the
delete-replica api to delete all but one of the replicas, and bouncing the last
replica to let it lead.
I will let anshum share a post on the details of how to recover leader shards.
> On Mar 14, 2
correction:
Thanks Shalin, Shawn.
I ended up getting guidance from Anshum on this and we did indeed use the
delete-replica api to delete all but one of the replicas, and bouncing the last
replica to let it lead.
I will let anshum share a post on the details of how to recover leaderless
shard
What Shawn said.
DeleteShard API is supposed to be used either when using implicit routing
or when you have compositeId router but the shard has already been split
and therefore in an inactive state.
Delete Replica API is what you need if you want to delete an individual
replica.
On Fri, Mar 15,
On 3/14/2019 12:47 PM, Aroop Ganguly wrote:
I am trying to delete a shard from a collection using the collections
api for the same.
On the solr ui, all the replicas are in “downed” state.
However, when I run the delete shard
command: /solr/admin/collections?action=DELETESHARD&collection=x&sha
Hi All
I am trying to delete a shard from a collection using the collections api for
the same.
On the solr ui, all the replicas are in “downed” state.
However, when I run the delete shard command:
/solr/admin/collections?action=DELETESHARD&collection=x&shard=shard84
I get this exception:
{
