Any other solutions for this ?
On Fri, Apr 21, 2017 at 9:42 AM, Pranaya Behera
wrote:
> Hi Erick,
> Even if they use different solr.home which I have also
> tested in AWS environment there also is the same problem.
>
> Can someone verify the first message
Hi Erick,
Even if they use different solr.home which I have also
tested in AWS environment there also is the same problem.
Can someone verify the first message in their local ?
On Fri, Apr 21, 2017 at 2:27 AM, Erick Erickson wrote:
> Have you looked at the
Have you looked at the Solr logs on the node you try to bring back up?
There are sometimes much more informative messages in the log files.
The proverbial "smoking gun" would be messages about write locks.
You say they are all using the same solr.home, which is probably the
source of a lot of
Hi,
Can someone from the mailing list also confirm the same findings
? I am at wit's end on what to do to fix this. Please guide me to
create a patch for the same.
On Thu, Apr 20, 2017 at 3:13 PM, Pranaya Behera
wrote:
> Hi,
> Through SolrJ I am trying to
Hi,
Through SolrJ I am trying to upload configsets and create
collections in my solrcloud.
Setup:
1 Standalone zookeeper listening on 2181 port. version 3.4.10
-- bin/zkServer.sh start
3 Starting solr nodes. (All running from the same solr.home) version
6.5.0 and as well in 6.2.1
-- bin/solr