[
https://issues.apache.org/jira/browse/SOLR-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Davids updated SOLR-3854:
-------------------------------
Attachment: SOLR-3854v4.patch
Came across an issue with the release candidate... Unfortunately when switching
from http -> https it causes the same node to become a replica for that shard
group. That is because the base url is being compared in the clusterstate to
grab the previously assigned core node name / shard id. I attached a patch that
uses the nodeName instead (essentially the same as baseUrl just without the
scheme). It is important to note that the port is actually embedded in the node
name, so if the port changes the machine will be added as a new replica. Thus,
if clients would like to update their port from 8080 -> 8443 they would need to
update the node_name value in the clusterstate.json file in zookeeper.
Here is how to get the clusterprops.json initially populated in the example:
{code}
steves-mbp:cloud-scripts sdavids$ pwd
/Users/sdavids/Downloads/solr-4.7.0/example/scripts/cloud-scripts
steves-mbp:cloud-scripts sdavids$ ./zkcli.sh -zkhost localhost:9983 -cmd put
/clusterprops.json '{"urlScheme":"https"}'
{code}
> SolrCloud does not work with https
> ----------------------------------
>
> Key: SOLR-3854
> URL: https://issues.apache.org/jira/browse/SOLR-3854
> Project: Solr
> Issue Type: Bug
> Reporter: Sami Siren
> Assignee: Mark Miller
> Fix For: 4.7, 5.0
>
> Attachments: SOLR-3854.patch, SOLR-3854.patch, SOLR-3854.patch,
> SOLR-3854.patch, SOLR-3854.patch, SOLR-3854.patch, SOLR-3854.patch,
> SOLR-3854.patch, SOLR-3854.patch, SOLR-3854.patch, SOLR-3854.patch,
> SOLR-3854v2.patch, SOLR-3854v3.patch, SOLR-3854v4.patch
>
>
> There are a few places in current codebase that assume http is used. This
> prevents using https when running solr in cloud mode.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
