[jira] Updated: (ZOOKEEPER-326) standalone server ignores tickTime configuration
[ https://issues.apache.org/jira/browse/ZOOKEEPER-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Darroch updated ZOOKEEPER-326: Attachment: ZOOKEEPER-326.patch standalone server ignores tickTime configuration Key: ZOOKEEPER-326 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-326 Project: Zookeeper Issue Type: Bug Components: server Affects Versions: 3.0.0, 3.0.1, 3.1.0 Reporter: Chris Darroch Priority: Minor Fix For: 3.1.1, 3.2.0 Attachments: ZOOKEEPER-326.patch When using the ZooKeeper server in standalone mode, it ignores the tickTime setting in the configuration file and uses the DEFAULT_TICK_TIME of 3000 coded into ZooKeeperServer.java. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-326) standalone server ignores tickTime configuration
[ https://issues.apache.org/jira/browse/ZOOKEEPER-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Darroch updated ZOOKEEPER-326: Status: Patch Available (was: Open) standalone server ignores tickTime configuration Key: ZOOKEEPER-326 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-326 Project: Zookeeper Issue Type: Bug Components: server Affects Versions: 3.1.0, 3.0.1, 3.0.0 Reporter: Chris Darroch Priority: Minor Fix For: 3.1.1, 3.2.0 Attachments: ZOOKEEPER-326.patch When using the ZooKeeper server in standalone mode, it ignores the tickTime setting in the configuration file and uses the DEFAULT_TICK_TIME of 3000 coded into ZooKeeperServer.java. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
