[ 
https://issues.apache.org/jira/browse/SOLR-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516197#comment-14516197
 ] 

Steve Davids commented on SOLR-7474:
------------------------------------

The base url should be generated by the node when it joins the cluster (or at 
least that's how it used to work), so  the sequence of events that you describe 
will work upon restart without having to touch the cluster state. The purpose 
of the SSLMigrationTest is to do just that - update ZK, restart all nodes, then 
verify the base_url was updated appropriately with the proper URL scheme.

> Remove protocol name from base_url in cluster state
> ---------------------------------------------------
>
>                 Key: SOLR-7474
>                 URL: https://issues.apache.org/jira/browse/SOLR-7474
>             Project: Solr
>          Issue Type: Wish
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>             Fix For: Trunk, 5.2
>
>
> In order to setup SSL, a user must add a cluster property which enables HTTPS 
> instead of HTTP. This property is used to create the base_url which is stored 
> for every node in the cluster.
> The above works fine if we assume that a user decides to enable SSL before 
> creating the cluster. However, if a user with an existing cluster wants to 
> start using SSL, he will need to manually edit his cluster state to switch 
> the protocol stored inside base_url for every node from http to https. If we 
> remove the protocol from the base_url, a user can shutdown the cluster, setup 
> the certificates, add the cluster property and start the cluster thereby 
> re-using the same cluster state which existed without manual modifications.
> Alternately, an extension to zkcli can be provided to change the cluster 
> state. Thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to