bin/solr start -help

will give you a lot of info. But yes, the -s option is what you should
use. Here's one of my batch files I used to start various cloud
examples:

bin/solr start -c -z localhost:2181 -p 898 -s example/cloud/node1/solr

On Sun, Oct 15, 2017 at 11:48 PM, Gunalan V <visagan2...@gmail.com> wrote:
> Thanks Erick,
>
> I'm using the one VM where all SOLRCloud and Zookeeper nodes are running.
>
> I have two solr nodes in solrcloud. Just wanted to check do I need to
> create different solr home directory using -s param for each SOLR nodes ?
>
> If yes kindly share me some documentation to configure separate node
> directories.
>
>
> GVK
>
>
> On Thu, Oct 12, 2017 at 10:17 AM, Erick Erickson <erickerick...@gmail.com>
> wrote:
>
>> You might be hitting SOLR-11297, which is fixed in Solr 7.0.1. The
>> patch should back-port cleanly to 6x versions though.
>>
>> Best,
>> Erick
>>
>> On Thu, Oct 12, 2017 at 12:14 AM, Gunalan V <visagan2...@gmail.com> wrote:
>> > Hello,
>> >
>> > I'm using SOLR 6.5.1 and I have 2 SOLR nodes in SOLRCloud and created
>> > collection using the below [1] and it was created successfully during
>> > initial time but next day I tried to restart the nodes in SOLR cloud.
>> When
>> > I start the first node the collection health is active but when I start
>> the
>> > second node the collection is became down and could see the locks in the
>> > logs [2].
>> >
>> > Also I have the set the solr home in zookeeper using the command [3].
>> >
>> > Did anyone came across this issue? If so please let me know how to fix
>> it.
>> >
>> >
>> > [1]
>> > http://localhost:8983/solr/admin/collections?action=
>> CREATE&name=testcollection&numShards=2&replicationFactor=
>> 2&maxShardsPerNode=2&collection.configName=testconfigs
>> >
>> >
>> > [2]  Caused by: org.apache.lucene.store.LockObtainFailedException: Index
>> > dir
>> > '/data01/solr/solr-6.5.1/server/solr/testcollection_
>> shard1_replica2/data/index/'
>> > of core 'testcollection_shard1_replica2' is already locked. The most
>> likely
>> > cause is another Solr server (or another solr core in this server) also
>> > configured to use this directory; other possible causes may be specific
>> to
>> > lockType: native
>> >         at org.apache.solr.core.SolrCore.initIndex(SolrCore.java:713)
>> >
>> >
>> > [3]  ./solr zk cp file:/data01/solr/solr-6.5.1/server/solr/solr.xml
>> > zk:/solr.xml -z 10.120.166.12:2181,10.120.166.12:2182,10.120.166.12:2183
>> >
>> >
>> >
>> > Thanks,
>> > GVK
>>

Reply via email to