Ishan Chattopadhyaya created SOLR-13695:

             Summary: SPLITSHARD (link), followed by DELETESHARD of parent 
shard causes data loss
                 Key: SOLR-13695
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
            Reporter: Ishan Chattopadhyaya
            Assignee: Ishan Chattopadhyaya

One of my clients experienced data loss with the following sequence of 
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 

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

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to