Hi Ekta, Rule#1 - You shouldn't forcefully and manually change the state unless you know what you're doing and have performed all the checks.
Seems like the child shards were still getting created i.e. copying the entire index from the parent shard when you manually switched. One of the reasons for this could be that you ran out of disk on the leader node. You might be able to get more information about that by looking at the logs, and information from any cluster management tool that you might be using that tracks metrics like disk usage etc. The shard split, actually creates 2 subshards on the same node as the original parent, practically duplicating the data in a separate set of index directories. Did you send more updates while this was going on? You still might be able to restore things from the original parent by changing the clusterstate to how it was before you issues SPLITSHARD (with only the parent shard - in active ). Before you do anything, I'd suggest you copy the indexes. If you have any error logs, it would be good to share them here on the list (if you can). Make sure you upload them to a file sharing service instead of sending those as attachments to the mailing list. -Anshum On Mon, Jan 16, 2017 at 2:33 AM Ekta Bhalwara <ekta.bhalw...@e-arc.com> wrote: > Hi , > > I tried Shard Splitting with 6.3 version of Solr,with the following steps:- > > Step 1 : > > I have issued > "collections?action=SPLITSHARD&collection=<collectionName>&shard=shard1" > > Step 2 : > > I noticed 2 child shard got created shard1_0 and shard1_1 > > step 3 : > > After complete step 2, still I see > > shard1 state : active > > AND > > shard1_0 and shard1_1 : > > state:construction > > I checked the state in state.json for nearly 48 hours , but the data > copying got frozen up while reaching a certain range(for example:- 60GB > data in parent node, after splitting, both child nodes got 24GB data, > then data copying into child not got stopped). The state.json file was > not changing further. > > Moreover, when i manually changed state.json (parent node to inactive > from active and child node to active from construction) i suffered a > huge loss of data.Please look into the issue from your side and let me > know in case of any further information is required. > > > -- > > Thanks & Regards > Ekta > >
