as a note you could change out the values in solr.xml to be as follows
and pull these values from System Properties.
<cores adminPath="/admin/cores" defaultCoreName="${collection.configName}">
<core name="${collection.configName}" instanceDir="." shard="${shard}"/>
</cores>
unless someone says otherwise, but the quick tests I've run seem to
work perfectly well with this setup.
2011/9/9 Yury Kats <yuryk...@yahoo.com>:
> On 9/9/2011 6:54 PM, Pulkit Singhal wrote:
>> 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
>
> With this you are telling ZK to bootstrap a collection with content of
> specific
> files, but you don't tell what collection that should be.
>
> Hence you want collection.configName parameter, and you want
> solr.xml to reference the same name in 'collection' attribute for the cores,
> so that SolrCloud knows where to pull configuration for that core from.
>
>
>
