[
https://issues.apache.org/jira/browse/ZOOKEEPER-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071034#comment-13071034
]
Hudson commented on ZOOKEEPER-1119:
-----------------------------------
Integrated in ZooKeeper-trunk #1255 (See
[https://builds.apache.org/job/ZooKeeper-trunk/1255/])
ZOOKEEPER-1119. zkServer stop command incorrectly reading comment lines in
zoo.cfg (phunt via mahadev)
mahadev :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1150937
Files :
* /zookeeper/trunk/bin/zkCleanup.sh
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/bin/zkServer.sh
> zkServer stop command incorrectly reading comment lines in zoo.cfg
> ------------------------------------------------------------------
>
> Key: ZOOKEEPER-1119
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1119
> Project: ZooKeeper
> Issue Type: Bug
> Components: scripts
> Affects Versions: 3.3.3
> Environment: Ubuntu Linux 10.04, JDK 6
> Reporter: Glen Mazza
> Assignee: Patrick Hunt
> Fix For: 3.4.0
>
> Attachments: ZOOKEEPER-1119.patch
>
>
> Hello, adding the following commented-out dataDir to the zoo.cfg file
> (keeping the default one provided active):
> {noformat}
> # the directory where the snapshot is stored.
> # dataDir=test123/data
> dataDir=/export/crawlspace/mahadev/zookeeper/server1/data
> {noformat}
> and then running sh zkServer.sh stop is showing that the program is
> incorrectly reading the commented-out dataDir:
> {noformat}
> gmazza@gmazza-work:~/dataExt3/apps/zookeeper-3.3.3/bin$ sh zkServer.sh stop
> JMX enabled by default
> Using config: /media/NewDriveExt3_/apps/zookeeper-3.3.3/bin/../conf/zoo.cfg
> Stopping zookeeper ...
> error: could not find file test123/data
> /export/crawlspace/mahadev/zookeeper/server1/data/zookeeper_server.pid
> gmazza@gmazza-work:~/dataExt3/apps/zookeeper-3.3.3/bin$
> {noformat}
> If I change the commented-out line in zoo.cfg to "test123456/data" and run
> the stop command again I get:
> error: could not find file test123456/data
> showing that it's incorrectly doing a run-time read of the commented-out
> lines. (Difficult to completely confirm, but this problem doesn't appear to
> occur with the start command, only the stop one.)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
