You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/10/06 16:07:20 UTC

[jira] [Updated] (KUDU-1677) Ordered scans may return out-of-order rows when concurrent with compaction

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

Todd Lipcon updated KUDU-1677:
------------------------------
    Priority: Critical  (was: Major)

> Ordered scans may return out-of-order rows when concurrent with compaction
> --------------------------------------------------------------------------
>
>                 Key: KUDU-1677
>                 URL: https://issues.apache.org/jira/browse/KUDU-1677
>             Project: Kudu
>          Issue Type: Bug
>          Components: tablet
>    Affects Versions: 1.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>
> If an ordered scan starts during the 'phase 2' of a compaction (when there is a DuplicatingRowSet in place), then the DuplicatingRowSet ends up creating a UnionIterator of the original rowsets. This union is non-ordered, so it ends up yielding out-of-order rows.
> This is causing alter_table-randomized-test to have verification failures about 0.25% of the time, but should be relatively easy to reproduce by adding concurrent ordered scans to some stress test that causes lots of compaction.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)