[
https://issues.apache.org/jira/browse/SOLR-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16328709#comment-16328709
]
Jan Høydahl commented on SOLR-9272:
-----------------------------------
Nice work. Sorry for the long silence.
* You have a few {{System.out.println}} debug prints still in the patch
* HTTP->HTTPS workaround I guess is acceptable if not the most elegant :)
Perhaps the tool can assume port 8983 if neither -z or -p is given? Then
{{bin/solr zk ls /}} would work if solr is running locally on default port.
Most other operations such as start, stop etc will attempt to work with port
8983 if nothing else specified, so it would be nice if we did the same here?
> Auto resolve zkHost for bin/solr zk for running Solr
> ----------------------------------------------------
>
> Key: SOLR-9272
> URL: https://issues.apache.org/jira/browse/SOLR-9272
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Affects Versions: 6.2
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Labels: newdev
> Attachments: SOLR-9272.patch, SOLR-9272.patch, SOLR-9272.patch,
> SOLR-9272.patch, SOLR-9272.patch, SOLR-9272.patch
>
>
> Spinoff from SOLR-9194:
> We can skip requiring {{-z}} for {{bin/solr zk}} for a Solr that is already
> running. We can optionally accept the {{-p}} parameter instead, and with that
> use StatusTool to fetch the {{cloud/ZooKeeper}} property from there. It's
> easier to remember solr port than zk string.
> Example:
> {noformat}
> bin/solr start -c -p 9090
> bin/solr zk ls / -p 9090
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
