[
https://issues.apache.org/jira/browse/KUDU-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813647#comment-16813647
]
Todd Lipcon commented on KUDU-2768:
-----------------------------------
This is looking for a stronger durability guarantee, not a stronger consistency
guarantee, right? We already have strict consistency assuming readers are using
consistent reads.
For this application, is bumping to 4 or 5 replicas not an option?
> Support client write strong consistency
> ----------------------------------------
>
> Key: KUDU-2768
> URL: https://issues.apache.org/jira/browse/KUDU-2768
> Project: Kudu
> Issue Type: New Feature
> Components: consensus
> Reporter: Xu Yao
> Priority: Major
>
> Sometimes we need to ensure that the data is not lost in the scenario where 2
> replicates cannot be recovered at the same time(we have 3 replicates). This
> requires 3 replicates to be committed before response to client.
> But currently, as long as there are 2 replicates to be committed, the write
> rpc success is returned to the client. Maybe we can add a gflag to indicate
> whether all replicates need to be committed before applying(response to
> client write success).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
