[
https://issues.apache.org/jira/browse/SOLR-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341906#comment-14341906
]
Hrishikesh Gadre commented on SOLR-7176:
----------------------------------------
[~markrmiller] [~andyetitmoves] There is a cluster management API to support
this functionality.
solr/admin/collections?action=CLUSTERPROP&name=urlScheme&val=https
The problem with using this API is that it requires that Solr server need to be
up and running. This could be problematic if Solr cluster is being managed by
an external tool (e.g. Cloudera Manager). e.g. assume following workflow,
1. User shuts down Solr cluster.
2. Users configures Solr service to use SSL (via. Cloudera Manager)
3. User restart the Solr cluster
Here you can see that the Solr servers would be down during step (3). Instead
if we expose this functionality through zkcli, then we would be able to bypass
the requirement for Solr servers to be up and running. Obviously we don't have
to add this option to zkcli. Any other option (which would not depend upon Solr
server to be up) should be fine.
> allow zkcli to modify JSON
> --------------------------
>
> Key: SOLR-7176
> URL: https://issues.apache.org/jira/browse/SOLR-7176
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
> Priority: Minor
>
> To enable SSL, we have instructions like the following:
> {code}
> server/scripts/cloud-scripts/zkcli.sh -zkhost localhost:2181 -cmd put
> /clusterprops.json '{"urlScheme":"https"}'
> {code}
> Overwriting the value won't work well when we have more properties to put in
> clusterprops. We should be able to change individual values or perhaps merge
> values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
