[
https://issues.apache.org/jira/browse/ZOOKEEPER-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051334#comment-13051334
]
Nate Putnam commented on ZOOKEEPER-1087:
----------------------------------------
I'm not sure what is going on with the import of the assertion methods. The
other tests in that class use assertEquals without any issue but Jenkins was
complaining about assertTrue,assertFalse not being found. I don't see an
explicit import for assertEquals so I'm not sure what's going on. Runs fine for
me in IntelliJ and command line. Attaching the latest patch.
> ForceSync VM arguement not working when set to "no"
> ---------------------------------------------------
>
> Key: ZOOKEEPER-1087
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1087
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.2, 3.3.3
> Reporter: Ankit Patel
> Assignee: Nate Putnam
> Priority: Blocker
> Fix For: 3.3.4, 3.4.0
>
> Attachments: ZOOKEEPER-1087.patch, ZOOKEEPER-1087.patch
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> Cannot use forceSync=no to asynchronously write transaction logs. This is a
> critical bug, please address it ASAP. More details:
> The class org.apache.zookeeper.server.persistence.FileTxnLog initializes
> forceSync property in a static block. However, the static variable is defined
> after the static block with a default value of true. Therefore, the value of
> the variable can never be false. Please move the declaration of the variable
> before the static block.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
