Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-1087

ForceSync VM arguement not working when set to "no"

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.3.3
    • Fix Version/s: 3.3.4, 3.4.0
    • Component/s: scripts
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Respect the "zookeeper.forceSync" system property.

      Description

      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.

        Attachments

        1. ZOOKEEPER-1087.patch
          3 kB
          Nate Putnam
        2. ZOOKEEPER-1087.patch
          2 kB
          Nate Putnam
        3. ZOOKEEPER-1087.patch
          2 kB
          Nate Putnam

          Activity

            People

            • Assignee:
              nputnam Nate Putnam
              Reporter:
              ankitp129 Ankit Patel
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 5m
                5m
                Remaining:
                Remaining Estimate - 5m
                5m
                Logged:
                Time Spent - Not Specified
                Not Specified