[
https://issues.apache.org/jira/browse/SOLR-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326645#comment-16326645
]
Jason Gerlowski commented on SOLR-9272:
---------------------------------------
Sorry to jump on so late here guys; only caught this Jira recently.
Based on my understanding (which may be wrong), the{{-p}} option can only be
used when Solr is running on that box. (But the alternative {{-z}} option can
be used regardless of where the script is being run).
This limitation of {{-p}} is probably worth mentioning in the help-text for
that option, just so it's documented and avoids confusing users.
(I suspect a bunch of the {{bin/solr}} commands have this same pitfall and
don't document it, now that I think about it. But fixing those up would be
work for a different JIRA...)
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
