You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Nate Putnam (JIRA)" <ji...@apache.org> on 2011/06/17 18:24:47 UTC

[jira] [Updated] (ZOOKEEPER-1087) ForceSync VM arguement not working when set to "no"

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nate Putnam updated ZOOKEEPER-1087:
-----------------------------------

    Attachment: ZOOKEEPER-1087.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
>            Priority: Blocker
>             Fix For: 3.3.2, 3.3.3
>
>         Attachments: 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