[
https://issues.apache.org/jira/browse/HDDS-12247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925131#comment-17925131
]
Ivan Andika commented on HDDS-12247:
------------------------------------
This make sense. Perhaps we need a new watch type called MAJORITY_APPLIED to
ensure that the block has been applied in at least 2 DNs.
> WaitForApply on data writes for ratis keys
> ------------------------------------------
>
> Key: HDDS-12247
> URL: https://issues.apache.org/jira/browse/HDDS-12247
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Datanode
> Reporter: Swaminathan Balachandran
> Priority: Major
>
> In order to ensure the data is completely written to at least majority of the
> nodes/all the nodes, a waitForApply where the ratis leader can optionally
> wait for the followers to apply the transaction and just not commit the
> transaction to raft log. This would mean that the applyIndex would have to be
> shared in the raft protocol
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
