[jira] [Commented] (KUDU-2768) Support client write strong consistency

["Xu Yao (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838234#comment-16838234 ] 

Xu Yao commented on KUDU-2768:
------------------------------

You’re right. It’s a stronger durablility guarantee.  When our cluster is large, using 4 or 5 replicas is a good option.  But if our cluster is very small (3 master + 3 tserver), we can't create more replicas. I think this feature will be useful in this small cluster.

>  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)