Hi,
I disabled SSL/TLS- now creating a collection works.
To re-enable ssl, I've tried upgrading Zookeeper's java from 7 to 8. Solr
was already java8. Now I'm thinking there's a solr.in.sh parameter that's
new, since solr 5, that I'm still missing,
or the certificate has some issue, maybe the SNI
Try directly the collection API url to create collection as Mangesh
suggested and see how it goes...
On Tue, May 30, 2017 at 11:02 PM, mganeshs wrote:
> Couple of times I faced this issue when firewall "Endpoint security" was
> on.
> Once I disabled it then it started working.
>
> Also for creat
Couple of times I faced this issue when firewall "Endpoint security" was on.
Once I disabled it then it started working.
Also for creating collection, I usually do in the following way,
upconfig the configuration to zookeeper using the command
bin/solr zk upconfig -n collection1_configs -z srv-n
Thank you Hrishikesh,
I did try recreating with async, but that just ran and ran. When I
called for the overseer status, that too hung up. I restarted the
cluster and now it is working.
-Joe
On 1/16/2017 3:01 PM, Hrishikesh Gadre wrote:
Based on the stack trace, it looks like the Solr co
Based on the stack trace, it looks like the Solr collection create request
was not processed (or in-progress) on the overseer node. Can you check if
the Solr server hosting the overseer role is healthy and is connected to
Zookeeper ?
If there are no issues with the cluster, you can try using the a
ly-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Re: Can't create collection without plugin,
: can't load plugin without collection
:
: I might be on the wrong track, but this statement made me think...
:
: I can force this to work by removing the c
I might be on the wrong track, but this statement made me think...
I can force this to work by removing the custom reference, create the
collection, load the jar and then add the custom reference back in place.
This is fine as a manual one-time setup, but not feasible in a scripted
production depl
Well, it was worth a try ;)
On Wed, Sep 7, 2016 at 9:42 AM, John Bickerstaff
wrote:
> Not sure if it's helpful, but I did solve a similar problem by scripting
> the placement of the plugin .jar file into the appropriate directories as
> part of the build process for my VMs
>
> I get that doin
Not sure if it's helpful, but I did solve a similar problem by scripting
the placement of the plugin .jar file into the appropriate directories as
part of the build process for my VMs
I get that doing it through the BlobStore would be preferred, probably...
But I couldn't get it to work and decide
Sadly, that didn't work.
Without a core to hit, the /[COLLECTION]/config returns a 404 error.
The best bet at this point may be for me may be one of the following:
1. Programmatically modify configoverlay.json file to add the runtime libs
when I upload the config.
or
2. Patch solr so that sc
Have you tried creating the collection with the special value of
"EMPTY" for createNodeSet? See:
https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api1
It's original purpose was to allow _all_ replicas to be placed
manually, but it might work for your use-case.
WARNI
11 matches
Mail list logo
