[jira] [Commented] (SOLR-9272) Auto resolve zkHost for bin/solr zk for running Solr

["Amrit Sarkar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242335#comment-16242335 ] 

Amrit Sarkar commented on SOLR-9272:
------------------------------------

Looking for any suggestions. Not comforable saying this, but we can ignore tests for this utility, as I can see hardcoded "http://localhost:....." for default Solr url and not being tested anywhere. Pretty sure if tested under {{SolrTestCaseJ}}, it will randomise SSL config.

Let me know [~erickerickson] [~janhoy]

> 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
>              Labels: newdev
>         Attachments: 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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org