[SOLR-11287] Sub-shards by SPLITSHARD loses data on restarting SOLR

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 5.5.1
• Component/s: SolrCloud
• Labels: documentation-update

Environment

Ubuntu 64-bit 32-core server, 240GB RAM

• Assignee: Unassigned
• Reporter: Vannia Rajan
• Created: 24/Aug/17 14:00
• Updated: 08/Jun/19 15:22
• Resolved: 05/Sep/17 16:46

Description

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.