Re: Collection API calls on SSL sometimes hang

r.flushBuffer(HttpGenerator.java:838) ... 37 more,code=500} On Mon Feb 09 2015 at 7:49:24 PM Avanish Raju wrote: > Hi all, > > I'm using self-signed certificates between my SolrCloud (4.10.3 > <http://mirror.sdunix.com/apache/lucene/solr/ref-guide/apache-solr-ref-guide-4.10.pdf>)

Collection API calls on SSL sometimes hang

Hi all, I'm using self-signed certificates between my SolrCloud (4.10.3 ) instance and Curl/Solr http client with needClientAuth=true on jetty.xml. I'm able to load the Solr home page, and also make select/query

Re: Changing contextRoot from /solr to /

> >> The simplest (but definitely no "elegant") way is to rename the > solr.war under your deployment directory; this works with many servlet > engines / application server - Jetty, Tomcat, JBoss, Weblogic, Websphere > (most probably also with the others) > >>

Changing contextRoot from /solr to /

I want to serve solr as a standalone server on a specific port, and need to change the contextRoot from /solr to / (I need to include some health checks on / which I will add to the solr.war) I've tried changing my node1/solr/solr.xml's hostContext variable to $(hostContext:) instead of $(hostCont

Re: Core property name ignored when creating collection using API

o see such an activity community though. :) Regards, Avanish On Tue Feb 03 2015 at 9:15:20 PM Shawn Heisey wrote: > On 2/2/2015 1:08 AM, Avanish Raju wrote: > > I'm learning to create collections by http for a new solr instance. To > > create a new collection called "*

Re: Core property name ignored when creating collection using API

Hi Chris, Thanks so much for your reply and clarification. I was able to get the collection search working as expected. :) Also sharing the following JIRA issue for fixes/improvements to Solr Admin for SolrCloud-based things, shared by @elyagrog on IRC: https://issues.apache.org/jira/browse/SOLR

Re: Core property name ignored when creating collection using API

I had a discussion with @search_mb about this on IRC, and he explained how my collection query would still work with "user6", though we couldn't resolve why the solr Core Admin page doesn't show the collection name as " user6". Detailed chat log follows: --

Re: Core property name ignored when creating collection using API

Hi Erick, Thanks for your reply! I totally understand that each shard should have a different name and each replica should too. But I want "user6" to be the name of the collection. Similar to how we have "collection 1" in the quick start. I'm hoping to set up one collection per user, which may spa

Core property name ignored when creating collection using API

Hi all, I'm learning to create collections by http for a new solr instance. To create a new collection called "*user6*", I tried the following: http://104.154.50.127:8983/solr/admin/collections?action=CREATE&name=*user6* &numShards=1&replicationFactor=2&property.instanceDir=*user6*&property.name=

Core property name ignored when creating collection using API

Hi all, I'm learning to create collections by http for a new solr instance. To create a new collection called "*user6*", I tried the following: http://104.154.50.127:8983/solr/admin/collections?action=CREATE&name=*user6* &numShards=1&replicationFactor=2&property.instanceDir=*user6*&property.name=