lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Bende <bbe...@gmail.com>
Subject Re: creating collection using collection API with SSL enabled SolrCloud
Date Thu, 09 Feb 2017 17:30:17 GMT
You should be able to start your Solr instances with "-h <hostname>".

On Thu, Feb 9, 2017 at 12:09 PM, Xie, Sean <Sean.Xie@finra.org> wrote:
> Thank you Hrishikesh,
>
> The cluster property solved the issue.
>
> Now we need to figure out a way to give the instance a host name to solve the SSL error
that IP not matching the SSL name.
>
> Sean
>
>
>
> On 2/9/17, 11:35 AM, "Hrishikesh Gadre" <gadre.solr@gmail.com> wrote:
>
>     Hi Sean,
>
>     Have you configured the "urlScheme" cluster property (i.e. urlScheme=https)
>     ?
>     https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-CLUSTERPROP:ClusterProperties
>
>     Thanks
>     Hrishikesh
>
>
>
>     On Thu, Feb 9, 2017 at 8:23 AM, Xie, Sean <Sean.Xie@finra.org> wrote:
>
>     > Hi All,
>     >
>     > When trying to create the collection using the API when there are a few
>     > replicas, I’m getting error because the call seems to trying to use HTTP
>     > for the replicas.
>     >
>     > https://IP_1:8983/solr/admin/collections?action=CREATE&
>     > name=My_COLLECTION&numShards=1&replicationFactor=1&
>     > collection.configName=my_collection_conf
>     >
>     > Here is the error:
>     >
>     > org.apache.solr.client.solrj.SolrServerException:IOException occured when
>     > talking to server at: http://IP_2:8983/solr
>     >
>     >
>     > Is there something need to be configured for that?
>     >
>     > Thanks
>     > Sean
>     >
>     > Confidentiality Notice::  This email, including attachments, may include
>     > non-public, proprietary, confidential or legally privileged information.
>     > If you are not an intended recipient or an authorized agent of an intended
>     > recipient, you are hereby notified that any dissemination, distribution or
>     > copying of the information contained in or transmitted with this e-mail is
>     > unauthorized and strictly prohibited.  If you have received this email in
>     > error, please notify the sender by replying to this message and permanently
>     > delete this e-mail, its attachments, and any copies of it immediately.  You
>     > should not retain, copy or use this e-mail or any attachment for any
>     > purpose, nor disclose all or any part of the contents to any other person.
>     > Thank you.
>     >
>
>

Mime
View raw message