Looking at this, it doesn't look like the operation completed. Also, the
parent shard seems to be intact and ideally should have served the results.
Until splitting and replication completes, the sub-shards don't go active
(and the parent shard doesn't go inactive).
Can you give me more information on this? What version of Solr are you
using?
Also, exceptions/messages from the logs would be required to get more
context.
On Fri, Dec 20, 2013 at 7:58 AM, cwhi <chris.whi...@gmail.com> wrote:
> My apologies, I forgot to paste the output of clusterstate.json to my last
> post. Here it is:
>
> [zk: localhost:2181(CONNECTED) 1] get /clusterstate.json
> {"collection1":{
> "shards":{
> "shard1":{
> "range":"80000000-d554ffff",
> "state":"active",
> "replicas":{"10.0.0.229:8443_solr_collection1":{
> "state":"active",
> "base_url":"http://10.0.0.229:8443/solr";,
> "core":"collection1",
> "node_name":"10.0.0.229:8443_solr",
> "leader":"true"}}},
> "shard2":{
> "range":"d5550000-2aa9ffff",
> "state":"active",
> "replicas":{"10.0.0.5:8443_solr_collection1":{
> "state":"active",
> "base_url":"http://10.0.0.5:8443/solr";,
> "core":"collection1",
> "node_name":"10.0.0.5:8443_solr",
> "leader":"true"}}},
> "shard3":{
> "range":"2aaa0000-7fffffff",
> "state":"active",
> "replicas":{"10.0.0.246:8443_solr_collection1":{
> "state":"active",
> "base_url":"http://10.0.0.246:8443/solr";,
> "core":"collection1",
> "node_name":"10.0.0.246:8443_solr",
> "leader":"true"}}},
> "shard1_0":{
> "range":"80000000-aaa9ffff",
> "state":"construction",
> "parent":"shard1",
> "replicas":{"10.0.0.229:8443_solr_collection1_shard1_0_replica1":{
> "state":"down",
> "base_url":"http://10.0.0.229:8443/solr";,
> "core":"collection1_shard1_0_replica1",
> "node_name":"10.0.0.229:8443_solr"}}},
> "shard1_1":{
> "range":"aaaa0000-d554ffff",
> "state":"construction",
> "parent":"shard1",
> "replicas":{"10.0.0.229:8443_solr_collection1_shard1_1_replica1":{
> "state":"down",
> "base_url":"http://10.0.0.229:8443/solr";,
> "core":"collection1_shard1_1_replica1",
> "node_name":"10.0.0.229:8443_solr"}}},
> "shard2_0":{
> "range":"d5550000-fffeffff",
> "state":"construction",
> "parent":"shard2",
> "replicas":{"10.0.0.5:8443_solr_collection1_shard2_0_replica1":{
> "state":"down",
> "base_url":"http://10.0.0.5:8443/solr";,
> "core":"collection1_shard2_0_replica1",
> "node_name":"10.0.0.5:8443_solr",
> "leader":"true"}}},
> "shard2_1":{
> "range":"ffff0000-2aa9ffff",
> "state":"construction",
> "parent":"shard2",
> "replicas":{"10.0.0.5:8443_solr_collection1_shard2_1_replica1":{
> "state":"down",
> "base_url":"http://10.0.0.5:8443/solr";,
> "core":"collection1_shard2_1_replica1",
> "node_name":"10.0.0.5:8443_solr",
> "leader":"true"}}}},
> "maxShardsPerNode":"1",
> "router":{"name":"compositeId"},
> "replicationFactor":"1",
> "autoCreated":"true"}}
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Shards-stuck-in-down-state-after-splitting-shard-How-can-we-recover-from-a-failed-SPLITSHARD-tp4107297p4107622.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
Anshum Gupta
http://www.anshumgupta.net
