[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 ] Patrick Hunt updated ZOOKEEPER-1087: Fix Version/s: (was: 3.2.3) 3.4.0 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: scripts Affects Versions: 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, 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
[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 Fix import for Assert.assertTrue/False 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, 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
[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 ] Benjamin Reed updated ZOOKEEPER-1087: - Hadoop Flags: [Reviewed] +1 looks good 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, 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
[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 ] Benjamin Reed updated ZOOKEEPER-1087: - Component/s: (was: server) scripts Affects Version/s: (was: 3.3.2) Fix Version/s: (was: 3.4.0) 3.2.3 +1 looks good 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: scripts Affects Versions: 3.3.3 Reporter: Ankit Patel Assignee: Nate Putnam Priority: Blocker Fix For: 3.2.3, 3.3.4 Attachments: ZOOKEEPER-1087.patch, 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
[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
[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 ] Patrick Hunt updated ZOOKEEPER-1087: Fix Version/s: 3.3.4 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.4, 3.4.0 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
[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: (was: 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 Assignee: Nate Putnam Priority: Blocker Fix For: 3.3.4, 3.4.0 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
[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 Assignee: Nate Putnam Priority: Blocker Fix For: 3.3.4, 3.4.0 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
[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 Assignee: Nate Putnam Priority: Blocker Fix For: 3.3.4, 3.4.0 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
[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 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
