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?
Hi Shawn,
Thanks for the info.
Regards,
Edwin
On 28 April 2017 at 20:36, Shawn Heisey wrote:
> On 4/27/2017 10:06 PM, Zheng Lin Edwin Yeo wrote:
> > I'm using Solr 6.4.2, and I realized that for those fields which has no
> > values, the field name is not index into Solr.
> >
> > It was working
We use Solr 6.2 in EC2 instance with Cent OS 6.2 and we don't see any
difference in performance between EC2 and in local environment.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-performance-on-EC2-linux-tp4332467p4332553.html
Sent from the Solr - User mailing list
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
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
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
