Thanks Again.
Another question:
My solr.xml has:
<cores adminPath="/admin/cores" defaultCoreName="master1">
<core name="master1" instanceDir="." shard="shard1" collection="myconf"/>
</cores>
And I omitted -Dcollection.configName=myconf from the startup command
because I felt that specifying collection="myconf" should take care of
that:
cd /trunk/solr/example
java -Dbootstrap_confdir=./solr/conf -Dslave=disabled -DzkRun -jar start.jar
But the zookeeper.jsp page doesn't seem to take any of that into
effect and shows:
/collections (v=6 children=1)
collection1 (v=0 children=1) "configName=configuration1"
shards (v=0 children=1)
shard1 (v=0 children=1)
tiklup-mac.local:8983_solr_ (v=0)
"node_name=tiklup-mac.local:8983_solr
url=http://tiklup-mac.local:8983/solr/";
Then what is the point of naming the core and the collection?
- Pulkit
2011/9/9 Yury Kats <yuryk...@yahoo.com>:
> On 9/9/2011 10:52 AM, Pulkit Singhal wrote:
>> Thank You Yury. After looking at your thread, there's something I must
>> clarify: Is solr.xml not uploaded and held in ZooKeeper?
>
> Not as far as I understand. Cores are loaded/created by the local
> Solr server based on solr.xml and then registered with ZK, so that
> ZK know what cores are out there and how they are organized in shards.
>
>
>> because you have a slightly different config between Node 1 & 2:
>> http://lucene.472066.n3.nabble.com/Replication-setup-with-SolrCloud-Zk-td2952602.html
>
>
> I have two shards, each shard having a master and a slave core.
> Cores are located so that master and slave are on different nodes.
> This protects search (but not indexing) from node failure.
>
