[
https://issues.apache.org/jira/browse/SOLR-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504498#comment-14504498
]
Per Steffensen commented on SOLR-7176:
--------------------------------------
bq. Hence the fix for this use-case can not really depend upon the overseer lock
Sure you can. You can say that you have to own the Overseer-lock, in order to
be able to perform this kind of admin-tasks. The CLI job can try to take the
lock and then perform the operation. If it cannot get the lock (maybe retry for
a period of time), ask the Overseer to do it (either by doing the corresponding
HTTP request or by leaving it directly on the Overseer-queue) and wait
synchronously for the Overseer to handle it (it must be running since it the
lock is taken).
But optimistic locking (compare-and-swap) is probably the best in this case.
Only thing I fear is that if that approach is established as "the way it is
done" it will be repeated in upcoming cases where it might not be sufficient.
Sometime it is worth the effort to establish the best platform to build upon
from the beginning.
> 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
> Assignee: Noble Paul
> Priority: Minor
> Attachments: SOLR-7176.patch, SOLR-7176.patch, SOLR-7176.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
