Hi Anshum,
Thanks for the reply.
But I've stuck in some other way. I'm able to split shard successfully with
less amount of index data, i.e. less than 45GB. But my actual data volume is
more than 70 GB, and when I'm trying to split the shard in the same process,
it's not completed successfully. I
I see a successful completion of the request in the logs here:
2017-01-18 14:43:55.439 INFO
(OverseerStateUpdate-97304349976428549-10.1.1.78:4983_solr-n_00)
[ ] o.a.s.c.o.SliceMutator Update shard state invoked for
collection: collection1 with message: {
"shard1":"inactive",
"collect
Hi Anshum,
Thanks for the reply.
I had the copy of data that i was experimenting on, and anyways i was doing
it later too, after i posted the mail. Some points i want to let you know:-
1. This time i did not change the state of state.json.
2. Rest,I did the same steps as above and still the dat
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 f
