phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4026) Option to not wait on global mutable index write to complete
Date Mon, 17 Jul 2017 20:03:00 GMT

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

Samarth Jain commented on PHOENIX-4026:
---------------------------------------

>From what I understand, after talking with [~churromorales], when region server recovers
after a crash, it replays the edits in WAL files to recover changes that were not flushed
from the memstore to HFile. I guess the real question is whether WAL is replayed when region
server crashes after postBatchMutateInDispensably has completed successfully. I would say
yes.

> 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