You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ishan Chattopadhyaya (JIRA)" <ji...@apache.org> on 2019/08/15 04:10:00 UTC
[jira] [Resolved] (SOLR-13695) SPLITSHARD (link), followed by
DELETESHARD of parent shard causes data loss
[ https://issues.apache.org/jira/browse/SOLR-13695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ishan Chattopadhyaya resolved SOLR-13695.
-----------------------------------------
Resolution: Invalid
> SPLITSHARD (link), followed by DELETESHARD of parent shard causes data loss
> ---------------------------------------------------------------------------
>
> Key: SOLR-13695
> URL: https://issues.apache.org/jira/browse/SOLR-13695
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Assignee: Ishan Chattopadhyaya
> Priority: Critical
>
> One of my clients experienced data loss with the following sequence of operations:
> 1) SPLITSHARD with method as "link".
> 2) DELETESHARD of the parent (inactive) shard.
> 3) Query for documents in the subshards, seems like both subshards have 0 documents.
> Proposing a fix (after offline discussion with [~noble.paul]) based on running FORCEMERGE after SPLITSHARD (such that segments are rewritten), and not letting DELETESHARD delete the data directory until the FORCEMERGE operations finish.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org