[
https://issues.apache.org/jira/browse/SOLR-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500028#comment-14500028
]
Per Steffensen commented on SOLR-7176:
--------------------------------------
I agree, but from time to time I want to add a (async) command to the overseer
while the cluster is not running, expecting the overseer to pick it up and
execute it when I start my cluster. If you would enable this tool to do this
kind of stuff, then suddenly most of the cluster-commands become relevant for
this tool - if it is able to both execute the command directly (if supported -
e.g. by {{CLUSTERPROP}} command) or to leave the command for execution by the
overseer.
And, if you have numerous machines that might or might not currently run a
Solr-node, maybe you actually want to be able to run the {{OVERSEERSTATUS}}
command as a command-line just to get an "not running" response.
> 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
