zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Konstantinov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ZOOKEEPER-3408) Improve information about risks for forceSync config option
Date Fri, 31 May 2019 12:28:00 GMT
Dmitry Konstantinov created ZOOKEEPER-3408:

             Summary: Improve information about risks for forceSync config option
                 Key: ZOOKEEPER-3408
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3408
             Project: ZooKeeper
          Issue Type: Improvement
          Components: documentation
            Reporter: Dmitry Konstantinov


The following options can be useful, but be careful when you use them. The risk of each is
explained along with the explanation of what the variable does.

_forceSync_ : (Java system property: *zookeeper.forceSync*) Requires updates to be synced
to media of the transaction log before finishing processing the update. If this option is
set to no, ZooKeeper will not require updates to be synced to the media.
The risks for this option are not very clear. Does it only the risk of loss some recent committed
transactions if all Zookeeper instances from an ensemble are crashed and restarted at almost
the same time or some other problems are also possible? 


This message was sent by Atlassian JIRA

View raw message