You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Sathiya N (JIRA)" <ji...@apache.org> on 2018/03/13 23:45:00 UTC
[jira] [Commented] (SOLR-12087) Deleting shards sometimes fails and
causes the shard to exist in the down state
[ https://issues.apache.org/jira/browse/SOLR-12087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397864#comment-16397864 ]
Sathiya N commented on SOLR-12087:
----------------------------------
Deletes are done via DELETE Command.
*Steps*:
1. Create a replica in new node.
2. Delete the existing replica in previous node.
and Deletes fail (sometimes) leaving the zombie replicas in a down state.
> Deleting shards sometimes fails and causes the shard to exist in the down state
> -------------------------------------------------------------------------------
>
> Key: SOLR-12087
> URL: https://issues.apache.org/jira/browse/SOLR-12087
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 7.2
> Reporter: Jerry Bao
> Priority: Major
>
> Sometimes when deleting replicas, the replica fails to be removed from the cluster state. This occurs especially when deleting replicas en mass; the resulting cause is that the data is deleted but the replicas aren't removed from the cluster state. Attempting to delete the downed replicas causes failures because the core does not exist anymore.
> It seems like when deleting replicas, ZK writes are timing out, preventing the cluster state from being properly updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org