Hi,
I figured out when this issue happens, by observing the patterns with a
small set of data.
SPLITSHARD issues a soft-commit (with some of the files still not fully
written to disk). If I restart SOLR without issuing an explicit ,
the index directory is not fully written and the process is kill
This is strange. You can use the "bin/solr zk cp..." commands to bring
the collection state.json down to your local machine and do anything
you want to do with it, including marking the old shard as "active"
and removing the entries for the sub-shards. It's just a text file
after all. I'd also dele
Binoy,
I don't see anything wrong with the logs. The newly split shards are up,
with the parent set to inactive. But before restart, the new shards had all
of the data as in parent. After a restart, it wiped off to 0. I checked the
data directory, the data is completely gone.
Below, I attach the
Vanniarajan,
Do you see errors in your solr logs when you reboot? If so paste them here.
Are both the shards up?
Have you checked the data directory for both and confirmed that the data is
gone?
On Thu 24 Aug, 2017, 18:04 Vannia Rajan wrote:
> Hi,
>
> I'm facing weird issues on using SPLITSHARD
