hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3269) HBase table truncate semantics seems broken as "disable" table is now async by default.
Date Wed, 24 Nov 2010 04:11:13 GMT

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

stack commented on HBASE-3269:
------------------------------

Oh, I checked for other mentions of async I found enable is also async in shell so I changed
that too.  I committed the change under this issue.

> HBase table truncate semantics seems broken as "disable" table is now async by default.
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-3269
>                 URL: https://issues.apache.org/jira/browse/HBASE-3269
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.0
>         Environment: RHEL5 x86_64
>            Reporter: Suraj Varma
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.90.0, 0.92.0
>
>
> The new async design for disable table seems to have caused a side effect on the truncate
command. (IRC chat with jdcryans)
> Apparent Cause: 
> "Disable" is now async by default. When truncate is called, the disable operation returns
immediately and when the drop is called, the disable operation is still not completed. This
results in HMaster.checkTableModifiable() throwing a TableNotDisabledException.
> With earlier versions, disable returned only after Table was disabled.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message