[
https://issues.apache.org/jira/browse/HBASE-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220965#comment-16220965
]
Chia-Ping Tsai commented on HBASE-5617:
---------------------------------------
There is no rollback in master/branch-2 (see HBASE-15158), and i don't think it
is necessary to add the rollback hook for branch-1.x. Perhaps this issue can be
closed. [~ram_krish] WDYT?
> 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
> Fix For: 2.0.0-alpha-4
>
> 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)
