You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Dan Burkert (JIRA)" <ji...@apache.org> on 2017/10/09 22:42:00 UTC

[jira] [Reopened] (KUDU-1767) Reordering of client operations from the same KuduSession is possible

     [ https://issues.apache.org/jira/browse/KUDU-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Burkert reopened KUDU-1767:
-------------------------------

I'm reopening this, because I think it is a useful feature to have, and I think we can fix it without impacting performance.  I'm not keen on introducing more write modes, because I think even the set we have is unnecessarily confusing, and really only exists because we gradually changed the semantics of the clients instead of designing the semantics up-front.  We can strengthen the guarantees without breaking backwards compat, so we don't have to introduce a new mode for this case.

Fixing this would require the result tracker to reject out-of-order write batches from clients.  Then, clients are free to have an arbitrary number of in-flight batches, however they should be encouraged to rate limit when memory pressure errors are received.

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