phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4053) Lock row exclusively when necessary for mutable secondary indexing
Date Sat, 29 Jul 2017 23:23:00 GMT

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

James Taylor updated PHOENIX-4053:
----------------------------------
    Attachment: PHOENIX-4053_v2.patch

Here's a patch with a test ConcurrentMutationsIT.testLockUntilMVCCAdvanced that repros the
issue (by waiting in postBatchMutate) and includes a fix - locking rows until after mvcc is
advanced.

Please take a look, [~samarthjain] & [~vincentpoon].

> Lock row exclusively when necessary for mutable secondary indexing
> ------------------------------------------------------------------
>
>                 Key: PHOENIX-4053
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4053
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>         Attachments: PHOENIX-4053_v2.patch, PHOENIX-4053_wip.patch
>
>
> From HBase 1.2 on, rows are not exclusively locked when the preBatchMutate call is made
(see HBASE-18474). The mutable secondary index (global and local) depend on this to get a
consistent snapshot of a row between the point when the current row value is looked up, and
when the new row is written.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message