zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shraer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3408) Improve information about risks for forceSync config option
Date Mon, 03 Jun 2019 23:33:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855145#comment-16855145

Alexander Shraer commented on ZOOKEEPER-3408:

Yes, that was my concern.

> 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
>            Priority: Minor
> [https://zookeeper.apache.org/doc/r3.5.5/zookeeperAdmin.html#Unsafe+Options]
> {quote}
> 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.
> {quote}
> {quote}
> _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.
> {quote}
> 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