lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vannia Rajan (JIRA)" <>
Subject [jira] [Created] (SOLR-11287) Sub-shards by SPLITSHARD loses data on restarting SOLR
Date Thu, 24 Aug 2017 14:01:17 GMT
Vannia Rajan created SOLR-11287:

             Summary: Sub-shards by SPLITSHARD loses data on restarting SOLR
                 Key: SOLR-11287
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
          Components: SolrCloud
    Affects Versions: 5.5.1
         Environment: Ubuntu 64-bit 32-core server, 240GB RAM
            Reporter: Vannia Rajan

We are running SOLR 5.5.1 with 4 nodes (1 shard per node). We are in the process of splitting
the 4 shards into 8 shards.

The SPLITSHARD collections API works great - it does create the sub-shards and activates sub-shards,
inactivates the parent shard upon completion. The row count compard with parent shard vs sub-shards
are matching. However, the data in sub-shards doesn't seem to be persistent in our case.

A restart of SOLR leaves the sub-shards with 0 documents with their data directory sizes getting
reduced from 40+ GB to 71KB.

If I'm missing any other steps to be followed after SPLITSHARD to make the data in sub-shards
persistent, please let me know. Otherwise, I feel this may be a bug in v5.5.1.

Note: I was able to manually set the states of parent to "active" and children with 0 documents
as "inactive" by setting /collections/{collection}/state.json in zookeeper, to get back the
lost data.

This message was sent by Atlassian JIRA

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

View raw message