[
https://issues.apache.org/jira/browse/SOLR-13942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051396#comment-17051396
]
Erick Erickson commented on SOLR-13942:
---------------------------------------
Oh, looked there I can comment on JIRAs.
I should have mentioned that I could go on and on about how difficult it is to
troubleshoot Solr with clients, or, for that matter, operations people.
Anything we can do to facilitate this is welcome.
We’ve been guilty all along of thinking like developers who have access to
_everything_. And it’s not just when trying to consult I’ve the phone. There
are lots of organizations out there that.have their developers get stuff
working then throw it over the wall to their operations people. I can’t count
the number of times I feel like saying “find all the Solr log directories on
all your machines, plus the GC logs plus the ZK logs (oh, where are they?) and
zip them all up and send them to me” A day or two later they’ve tracked them
all down, zipped them up and the resulting 100G zip file overwhelms me.
Assuming they’ve gotten to them in time to capture the problem.
I’ve worked with clients with at least several hundred physical nodes. Every
client at that scale I’ve worked with has invested considerable time and energy
creating custom tools to help them because Solr doesn’t have much support
there. Joel’s work with streaming to identify query response and I have an SIP
out about indexing log files with Solr-specific faceting are two very small
examples.
Oh, and we need thread dumps of all those hundreds of machines too sometimes.
And I’ve completely skipped security restrictions. Government, financial
institutions, health insurance applications, etc. may or may not even allow
screen sharing. To make it worse, operations folks in some of these places
_also_ may not be able to see the raw data.
All this to drive home the fact that we’ve frankly done a poor job of making
troubleshooting easier...
</rant>
> /api/cluster/zk/* to fetch raw ZK data
> --------------------------------------
>
> Key: SOLR-13942
> URL: https://issues.apache.org/jira/browse/SOLR-13942
> Project: Solr
> Issue Type: New Feature
> Components: v2 API
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Blocker
> Fix For: 8.5
>
> Time Spent: 20m
> 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
