[
https://issues.apache.org/jira/browse/KUDU-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197872#comment-16197872
]
Dan Burkert commented on KUDU-1767:
-----------------------------------
Good point. Could we add a 'depends-on' field to the write batch with the ID
of the previous batch?
> Reordering of client operations from the same KuduSession is possible
> ---------------------------------------------------------------------
>
> Key: KUDU-1767
> URL: https://issues.apache.org/jira/browse/KUDU-1767
> Project: Kudu
> Issue Type: Bug
> Components: client, tablet
> Affects Versions: 1.1.0
> Reporter: Mike Percy
> Priority: Critical
> Fix For: n/a
>
>
> It is possible for client operations written via the same KuduSession to be
> reordered on the server side in MANUAL_FLUSH and AUTO_BACKGROUND_FLUSH modes.
> This violates our desired consistency guarantees.
> This may occur because we allow concurrent flushes from the client for
> throughput reasons and there is nothing enforcing the well-ordering of lock
> acquisition from a single client session on the server side.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
