I think the -c option should be unnecessary if -z is supplied. And it
works on the other machines.
Take a look at the solr.log files on the nodes that doesn't start,
that might give more information.
Or start with the -f option, that'll log to the foreground and you'll
probably see a better messag
AFAIK, to start as SolrCloud you should add "-c" switch option as below:
bin/solr start -c -z 192.168.1.6:2181,192.168.1.7:2181,
192.168.1.102:2181/solr
Otherwise, you'll be starting as standalone Solr instance.
Edward
On Mon, Jan 21, 2019 at 3:15 PM wrote:
> Hello,
>
> I am configuring the
Thanks a lot Shawn. That really helps, I believe the changes were made during
our load testing phase to introduce some changes in the startup script to
manage the max allocated memory.
That’s where someone introduced that line. We removed it and I’ll check how it
behaves now.
Regards
Prashan
On 1/5/2018 2:35 PM, Satyaprashant Bezwada wrote:
> Thanks a lot. It helped, I noticed the error in the solr console log.
> # java.lang.OutOfMemoryError: Metaspace
> # -XX:OnOutOfMemoryError="/usr/local/solr/bin/oom_solr.sh 8983 /var/solr/logs"
> # Executing /bin/sh -c "/usr/local/solr/bin/oom_s
Thanks a lot. It helped, I noticed the error in the solr console log.
cat solr-8983-console.log
I> No access restrictor found, access to any MBean is allowed
Jolokia: Agent started with URL http://xxx.xx.x.xxx:8778/jolokia/
2018-01-05 03:56:30.824 INFO (main) [ ] o.e.j.s.Server jetty-9.3.14.v20
If this has been working fine for a while and suddenly started this
behavior my first suspicion would be excessive GC, i.e. you've been adding
docs and your heap is no longer adequate. If Java needs to do a
stop-the-world garbage collection you can get these kinds of errors.
So I'd enable GC loggi
