Yes, and my clusterstate.json is still:
==
"shards":{
"shard1":{
"range":"80000000-7fffffff",
"state":"active",
"replicas":{"core_node1":{
"state":"active",
"base_url":"http://...../solr";,
"core":".._shard1_replica1",
"node_name":"....:8080_solr",
"leader":"true"}}},
"shard1_1":{
"range":"0-7fffffff",
"state":"construction",
"parent":"shard1",
"replicas":{"core_node2":{
"state":"active",
"base_url":"http://....:8080/solr";,
"core":".._shard1_1_replica1",
"node_name":"....:8080_solr",
"leader":"true"}}},
"shard1_0":{
"range":"80000000-ffffffff",
"state":"construction",
"parent":"shard1",
"replicas":{"core_node3":{
"state":"active",
"base_url":"http://....:8080/solr";,
"core":".._shard1_0_replica1",
"node_name":"....:8080_solr",
"leader":"true"}}}},
"maxShardsPerNode":"1",
"router":{"name":"compositeId"},
"replicationFactor":"1"}}
==
But, it got failed finally with out of memory.
And is definitely not progressing because the thread is stopped. Probably
SPLITSHARD is not mature enough to use yet.
Now, I've no choice but to do it from Solrj, indexing manually.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Unable-to-check-Solr-4-6-SPLITSHARD-command-progress-tp4106520p4106699.html
Sent from the Solr - User mailing list archive at Nabble.com.
