[
https://issues.apache.org/jira/browse/SOLR-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168366#comment-14168366
]
Jan Høydahl commented on SOLR-6595:
-----------------------------------
The reason for the IOException was that the Overseer node did not have the
correct SSL certificate required for authenticating with all the other Solr
nodes. Uploading the correct certificate to all nodes solved the issue.
However, will re-purpose this issue to improving error response on failed
distributed collection actions.
> Client SSL
> ----------
>
> Key: SOLR-6595
> URL: https://issues.apache.org/jira/browse/SOLR-6595
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.10
> Environment: SolrCloud with Client SSL
> Reporter: Sindre Fiskaa
> Priority: Minor
>
> Followed the description
> https://cwiki.apache.org/confluence/display/solr/Enabling+SSL and generated a
> self signed key pair. Configured a few solr-nodes and used the collection api
> to crate a new collection. I get error message when specify the nodes with
> the createNodeSet param. When I don't use createNodeSet param the collection
> gets created without error on random nodes. Could this be a bug related to
> the createNodeSet param?
> <response>
> <lst name="responseHeader"><int name="status">0</int><int
> name="QTime">185</int></lst><lst
> name="failure"><str>org.apache.solr.client.solrj.SolrServerException:IOException
> occured when talking to server at: https://vt-searchln04:443/solr</str></lst>
> </response>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
