[
https://issues.apache.org/jira/browse/ZOOKEEPER-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181504#comment-15181504
]
Biju Nair commented on ZOOKEEPER-2195:
--------------------------------------
[~dryabkov] the current code is in line with what is specified in the
documentation for
[fsync.warningthresholdms|https://zookeeper.apache.org/doc/r3.4.2/zookeeperAdmin.html#sc_advancedConfiguration].
But your change sets the property name to the standard followed for system
properties i.e. prefix with {{zookeeper}}. The change looks good to me, but
will need a change to the documentation so that they are in sync.
> fsync.warningthresholdms in zoo.cfg not working
> -----------------------------------------------
>
> Key: ZOOKEEPER-2195
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2195
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
> Affects Versions: 3.4.6, 3.5.0
> Reporter: David Fan
> Assignee: Biju Nair
> Priority: Trivial
> Attachments: ZOOKEEPER-2195.patch
>
>
> Config fsync.warningthresholdms in zoo.cfg does not work.
> I find QuorumPeerConfig.parseProperties give fsync.warningthresholdms a
> prefix like "zookeeper.fsync.warningthresholdms". But in class FileTxnLog
> where fsync.warningthresholdms is used, code is
> :Long.getLong("fsync.warningthresholdms", 1000),without prefix "zookeeper.",
> therefore can not get fsync.warningthresholdms's value.
> I wonder the speed of fsync, need this config to see whether the speed is
> good enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
