hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-5617) Provide coprocessor hooks in put flow while rollbackMemstore.
Date Thu, 26 Oct 2017 23:00:00 GMT

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

stack resolved HBASE-5617.
--------------------------
       Resolution: Invalid
    Fix Version/s:     (was: 2.0.0-alpha-4)

Closing as invalid. There is no rollback of memstore anymore (as per [~chia7712]), not since
we reordered the write path (1.2). Thanks [~mdrob] for putting this into consideration. Correct
me if I have this wrong [~ram_krish]

> Provide coprocessor hooks in put flow while rollbackMemstore.
> -------------------------------------------------------------
>
>                 Key: HBASE-5617
>                 URL: https://issues.apache.org/jira/browse/HBASE-5617
>             Project: HBase
>          Issue Type: Improvement
>          Components: Coprocessors
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: HBASE-5617_1.patch, HBASE-5617_2.patch
>
>
> With coprocessors hooks while put happens we have the provision to create new puts to
other tables or regions.  These puts can be done with writeToWal as false.
> In 0.94 and above the puts are first written to memstore and then to WAL.  If any failure
in the WAL append or sync the memstore is rollbacked.  
> Now the problem is that if the put that happens in the main flow fails there is no way
to rollback the 
> puts that happened in the prePut.
> We can add coprocessor hooks to like pre/postRoolBackMemStore.  Is any one hook enough
here?



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

Mime
View raw message