[
https://issues.apache.org/jira/browse/ZOOKEEPER-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Ohanian updated ZOOKEEPER-1744:
------------------------------------
Description:
When "clientPortAddress" is used in the config file (zoo.cfg), zkServer.sh's
status command runs a grep command that matches both "clientPort" and
"clientPortAddress". This creates an extra argument for FourLetterWordMain,
which fails, so the status command incorrectly indicates that it couldn't
connect to the server.
Also, "localhost" is hardcoded as the target host for FourLetterWordMain. The
"clientPortAddress" should be used if it is provided in the config file.
was:When "clientPortAddress" is used in the config file (zoo.cfg),
zkServer.sh's status command runs a grep command that matches both "clientPort"
and "clientPortAddress". This creates an extra argument for
FourLetterWordMain, which fails, so the status command incorrectly indicates
that it couldn't connect to the server.
> clientPortAddress breaks "zkServer.sh status"
> ----------------------------------------------
>
> Key: ZOOKEEPER-1744
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1744
> Project: ZooKeeper
> Issue Type: Bug
> Components: scripts
> Affects Versions: 3.4.5
> Reporter: Nick Ohanian
> Attachments: ZOOKEEPER-1744.patch
>
>
> When "clientPortAddress" is used in the config file (zoo.cfg), zkServer.sh's
> status command runs a grep command that matches both "clientPort" and
> "clientPortAddress". This creates an extra argument for FourLetterWordMain,
> which fails, so the status command incorrectly indicates that it couldn't
> connect to the server.
> Also, "localhost" is hardcoded as the target host for FourLetterWordMain.
> The "clientPortAddress" should be used if it is provided in the config file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
