zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "maoling (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ZOOKEEPER-3322) ./zkServer.sh status failed when reconfig don't write the clientPort into the zoo.cfg
Date Mon, 18 Mar 2019 01:53:00 GMT
maoling created ZOOKEEPER-3322:
----------------------------------

             Summary: ./zkServer.sh status failed when reconfig don't write the clientPort
into the zoo.cfg
                 Key: ZOOKEEPER-3322
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3322
             Project: ZooKeeper
          Issue Type: Bug
            Reporter: maoling


look at my zoo.cfg which don't have the clientPort value when using the reconfig.
*cat ../conf/zoo.cfg*
reconfigEnabled=true
dataDir=../../zkdata2
syncLimit=5
dataLogDir=../../zkdataLog2
initLimit=10
tickTime=2000
dynamicConfigFile=/data/software/zookeeper/zookeeper-test2/conf/zoo.cfg.dynamic.1f00000000

but look at the cmd:"./zkServer.sh status"´╝îit needs this clientPort value 
STAT=`"$JAVA" "-Dzookeeper.log.dir=${ZOO_LOG_DIR}" "-Dzookeeper.root.logger=${ZOO_LOG4J_PROP}"
"-Dzookeeper.log.file=${ZOO_LOG_FILE}" \
 -cp "$CLASSPATH" $JVMFLAGS org.apache.zookeeper.client.FourLetterWordMain \
 $clientPortAddress $clientPort srvr 2> /dev/null \

otw, ./zkServer.sh status will fail.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message