[
https://issues.apache.org/jira/browse/SOLR-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497484#comment-13497484
]
Gilles Comeau commented on SOLR-4075:
-------------------------------------
Agree.. I've done a similar test using:
SOLR.XML ->
<?xml version="1.0" encoding="UTF-8" ?>
<solr persistent="true">
<cores adminPath="/admin/cores" defaultCoreName="collection1" host="${host:}"
hostPort="${jetty.port:}" hostContext="${hostContext:}"
zkClientTimeout="${zkClientTimeout:15000}">
<core shard="shard1" instanceDir="collection1/" name="collection1"
collection="polecat"/>
<core shard="shard1" instanceDir="collection2/" name="collection2"
collection="polecat"/>
<core schema="schema.xml" shard="core3" instanceDir="core3/" name="core3"
config="solrconfig.xml" collection="polecat" dataDir="data"/>
<core schema="schema.xml" shard="core4" instanceDir="core4/" name="core4"
config="solrconfig.xml" collection="polecat2" dataDir="data"/>
<core schema="schema.xml" shard="core5" instanceDir="core5/" name="core5"
config="solrconfig.xml" collection="polecat2" dataDir="data"/>
</cores>
</solr>
and
http://localhost:8983/solr/admin/cores?action=UNLOAD&core=core4&deleteIndex=true
http://localhost:8983/solr/admin/cores?action=UNLOAD&core=core5&deleteIndex=true
and the polecat2 collection is removed with core5.
I do get the "no servers hosting shard:" error after removing core4 and before
removing core5.
So it's a "removing last core does not remove shard" while "removing last core
removes collection" is working fine?
> Upon removing the last core of a shard - Zookeeper keeps the shard and SOLR
> sends queries to it giving "no servers hosting shard:" when distributed query
> is run.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4075
> URL: https://issues.apache.org/jira/browse/SOLR-4075
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Gilles Comeau
> Priority: Minor
> Labels: patch
>
> Simple Repro of this issue: which now I thought was related to the decision
> made in: https://issues.apache.org/jira/browse/SOLR-3080 but Mark tells me
> might have been a problem during the zk layout refactoring right before 4.0.
> 1. Download SOLR 4 production and extract.
> 2. Replace solr.xml in apache-solr-4.0.0/example/solr/solr.xml with:
> <?xml version="1.0" encoding="UTF-8" ?>
> <solr persistent="true">
> <cores adminPath="/admin/cores" defaultCoreName="collection1"
> host="${host:}" hostPort="${jetty.port:}" hostContext="${hostContext:}"
> zkClientTimeout="${zkClientTimeout:15000}">
> <core shard="shard1" instanceDir="collection1/" name="collection1"
> collection="polecat"/>
> <core shard="shard1" instanceDir="collection2/" name="collection2"
> collection="polecat"/>
> <core schema="schema.xml" shard="core3" instanceDir="core3/" name="core3"
> config="solrconfig.xml" collection="polecat" dataDir="data"/>
> </cores>
> </solr>
> 3. Start solr with: java -Dbootstrap_confdir=./solr/collection1/conf
> -Dcollection.configName=myconf -DzkRun -Dsolrcloud.skip.autorecovery=true
> -jar start.jar
> (skip.autorecovery is used because the shards don't exist previously)
> Then run this:
> Sanity query:
> http://localhost:8983/solr/polecat/select?q=*%3A*&wt=xml&distrib=true
> Remove the core:
> http://localhost:8983/solr/admin/cores?action=UNLOAD&core=core3&deleteIndex=true
> Error query:
> http://localhost:8983/solr/polecat/select?q=*%3A*&wt=xml&distrib=true
> And the sanity query, we will receive 0 records, the error query "no servers
> hosting shard:". And in the clusterstate.json: "core3":{"replicas":{}}}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
