[
https://issues.apache.org/jira/browse/SOLR-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049993#comment-17049993
]
Noble Paul commented on SOLR-13942:
-----------------------------------
bq.ZK internals should not be part of our public API.
OK let's deprecate the {{/admin/zookeeper}} API then.
bq.Since then you edited it to answer the security.
I edited it to just correct a grammar error
bq.Please give some good concrete examples of what you'd use it for.
I already told that we want to write scripts that read various items in ZK.We
also want to lock down direct acess of ZK to a smaller set of people and
debugging cluster issues need others to look at the state across firewall
bq.ZK contains lots of internals.
We have already exposed these internals for the last 10 yrs & it seems to be
fine. People who use Solr need those internal details
The position we take is "No data in ZK is private, However, write access should
be limited"
> /api/cluster/zk/* to fetch raw ZK data
> --------------------------------------
>
> Key: SOLR-13942
> URL: https://issues.apache.org/jira/browse/SOLR-13942
> Project: Solr
> Issue Type: Bug
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> example
> download the {{state.json}} of
> {code}
> GET http://localhost:8983/api/cluster/zk/collections/gettingstarted/state.json
> {code}
> get a list of all children under {{/live_nodes}}
> {code}
> GET http://localhost:8983/api/cluster/zk/live_nodes
> {code}
> If the requested path is a node with children show the list of child nodes
> and their meta data
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
