Is this the correct way to start both of the replicas?
bin\solr.cmd start -cloud -p 8983 -s solr\node1\solr -m 8g -z
"localhost:9981,localhost:9982,localhost:9983"
bin\solr.cmd start -cloud -p 8984 -s solr\node2\solr -m 8g -z
"localhost:9981,localhost:9982,localhost:9983"
Regards,
Edwin
On 30
I'm starting Solr with this command:
bin\solr.cmd start -cloud -p 8983 -s solr\node1\solr -m 8g -z
"localhost:9981,localhost:9982,localhost:9983"
bin\solr.cmd start -cloud -p 8984 -s solr\node2\solr -m 8g -z
"localhost:9981,localhost:9982,localhost:9983"
Regards,
Edwin
On 30 April 2017 at 13:52
It might depend some on how you are starting Solr (I am less familiar with
Windows) but you will need to give each instead a separate log4j.properties
file and configure the log location in there.
Also check out the Solr Ref Guide section on Configuring Logging,
subsection Permanent Logging Settin
Yes, both Solr instances are running in the same hardware.
I believe they are pointing to the same log directories/config too.
How do we point them to different log directories/config?
Regards,
Edwin
On 30 April 2017 at 00:36, Mike Drob wrote:
> Are you running both Solr instances in the sam
Are you running both Solr instances in the same hardware and pointing them
at the same log directories/config?
On Sat, Apr 29, 2017, 2:56 AM Zheng Lin Edwin Yeo
wrote:
> Hi,
>
> I'm using Solr 6.4.2 on SolrCloud, and I'm running 2 replica of Solr.
>
> When I start the replica, I will encounter t
Hi,
I'm using Solr 6.4.2 on SolrCloud, and I'm running 2 replica of Solr.
When I start the replica, I will encounter this error message. It is
probably due to the Solr log, as both the main and the replica are trying
to access the same solr_gc.log.0.current file.
Is there anyway to prevent this?
