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] [Commented] (PHOENIX-4026) Option to not wait on global mutable index write to complete
Date Sat, 15 Jul 2017 01:06:00 GMT

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

James Taylor commented on PHOENIX-4026:
---------------------------------------

We had an offline discussion and concluded that doing index writes asynchronously is problematic
because we cannot guarantee on a RS crash that the not yet written index updates are not lost.
The data table write would have succeeded, so the WAL replay that also replays index updates
presumably wouldn't kick in for this case.

> Option to not wait on global mutable index write to complete
> ------------------------------------------------------------
>
>                 Key: PHOENIX-4026
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4026
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>         Attachments: PHOENIX-4026_wip.patch
>
>
> Today, a data table update synchronously waits for the index update to complete. While
some users may want that kind of strong consistency, some may be ok with the call to return
once the data table write is done.



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

Mime
View raw message