You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/09/18 17:46:00 UTC

[jira] [Commented] (HBASE-17787) Drop rollback for all procedures; not useful afterall

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

stack commented on HBASE-17787:
-------------------------------

Unscheduling from 2.x. We depend on rollback. Needs beefing up as a notion. Currently anemic. Unscheduling as not important for 2.0.

> Drop rollback for all procedures; not useful afterall
> -----------------------------------------------------
>
>                 Key: HBASE-17787
>                 URL: https://issues.apache.org/jira/browse/HBASE-17787
>             Project: HBase
>          Issue Type: Bug
>          Components: proc-v2
>            Reporter: stack
>            Priority: Critical
>
> Quote from [~mbertozzi] from https://docs.google.com/document/d/1kEWzyA0iCyRjdogjju9JNMDT9ODHaKcyoAJTMXkDpxc/edit#
> "Looking back rollback support is not really useful in our operations. We are always able to complete the operation at some point. So stuff like create, modify table, and so on. Should try to finish the operation instead of giving up and rollback in case of failure (e.g. hdfs hiccup)"



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