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/26 10:50:00 UTC

[jira] [Created] (SOLR-13718) SPLITSHARD using async can cause data loss

Ishan Chattopadhyaya created SOLR-13718:
-------------------------------------------

             Summary: SPLITSHARD using async can cause data loss
                 Key: SOLR-13718
                 URL: https://issues.apache.org/jira/browse/SOLR-13718
             Project: Solr
          Issue Type: Improvement
      Security Level: Public (Default Security Level. Issues are Public)
    Affects Versions: 7.7.2
            Reporter: Ishan Chattopadhyaya
            Assignee: Ishan Chattopadhyaya


When using SPLITSHARD with async, if there are underlying failures in the SPLIT core command or other sub-commands of SPLITSHARD, then SPLITSHARD succeeds and results in two empty sub-shards.

There are various potential failures with SPLIT core command, here's a way to reproduce using a Solr 6x index in Solr 7x.

Steps to reproduce (in Solr 7x):
{code}
1. Import the attached configset, and create a collection.
2. Move in the attached data directory (index created in Solr6x) in place of the created collection's data directory. Do a collection RELOAD.
3. Issue a *:* query, we see 5 documents.
4. Issue a SPLITSHARD, and then issue *:*, we see 0 documents.
{code}




--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org