[
https://issues.apache.org/jira/browse/ZOOKEEPER-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229050#comment-15229050
]
Rahul Yadav commented on ZOOKEEPER-885:
---------------------------------------
One more input:
Following are the JVM params for zookeeper:
/usr/local/jre7/bin/java
-cp
/tools/stow/zookeeper-3_3_6-20120803T1430/zookeeper/bin/../build/classes:
/tools/stow/zookeeper-3_3_6-20120803T1430/zookeeper/bin/../build/lib/*.jar:
/tools/stow/zookeeper-3_3_6-20120803T1430/zookeeper/bin/../zookeeper-3.3.6.jar:
/tools/stow/zookeeper-3_3_6-20120803T1430/zookeeper/bin/../lib/jline-0.9.94.jar:
/tools/stow/zookeeper-3_3_6-20120803T1430/zookeeper/bin/../src/java/lib/*.jar:
/tools/config/current:/usr/local/lib/java/apache-log4j-1.2.17/log4j-1.2.17.jar:
/usr/local/lib/java/apache-log4j-extras-1.1/apache-log4j-extras-1.1.jar
-DprocessName=zookeeper
-DlogLevel=INFO
-server
-verbose:gc
-Xms28672m
-Xmx28672m
-XX:MaxNewSize=256m
-XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=70
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-XX:+PrintTenuringDistribution
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.local.only=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.port=5690
org.apache.zookeeper.server.quorum.QuorumPeerMain /path/to/conf/zoo.cfg
*zookeeper-3_3_6-20120803T1430* is a platinized package for the standard
Zookeeper (3.3.6) package
> Zookeeper drops connections under moderate IO load
> --------------------------------------------------
>
> Key: ZOOKEEPER-885
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-885
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.2.2, 3.3.1
> Environment: Debian (Lenny)
> 1Gb RAM
> swap disabled
> 100Mb heap for zookeeper
> Reporter: Alexandre Hardy
> Priority: Critical
> Fix For: 3.5.2, 3.6.0
>
> Attachments: WatcherTest.java, benchmark.csv, tracezklogs.tar.gz,
> tracezklogs.tar.gz, zklogs.tar.gz
>
>
> A zookeeper server under minimum load, with a number of clients watching
> exactly one node will fail to maintain the connection when the machine is
> subjected to moderate IO load.
> In a specific test example we had three zookeeper servers running on
> dedicated machines with 45 clients connected, watching exactly one node. The
> clients would disconnect after moderate load was added to each of the
> zookeeper servers with the command:
> {noformat}
> dd if=/dev/urandom of=/dev/mapper/nimbula-test
> {noformat}
> The {{dd}} command transferred data at a rate of about 4Mb/s.
> The same thing happens with
> {noformat}
> dd if=/dev/zero of=/dev/mapper/nimbula-test
> {noformat}
> It seems strange that such a moderate load should cause instability in the
> connection.
> Very few other processes were running, the machines were setup to test the
> connection instability we have experienced. Clients performed no other read
> or mutation operations.
> Although the documents state that minimal competing IO load should present on
> the zookeeper server, it seems reasonable that moderate IO should not cause
> problems in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
