hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Stepachev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13076) Table can be forcibly enabled in AssignmentManager during table disabling.
Date Sun, 08 Mar 2015 20:27:38 GMT

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

Andrey Stepachev commented on HBASE-13076:
------------------------------------------

Hey [~Apache9], I did digging a bit. Didn't find any evidence that it can be related.
It seems that only source of trouble here can be the fact that after master marked
as initialized it still initializes some subsystems (meta replicas assignment process, quota
manager) that can use Zk so they can just not set their watcher yet.
So, I was unable to reproduce in my environment, so can't find out what listener 
was missing. If you can reproduce that, it would be helpful to add some logging
to find out what listener was missed.
thanks.

> Table can be forcibly enabled in AssignmentManager during table disabling.
> --------------------------------------------------------------------------
>
>                 Key: HBASE-13076
>                 URL: https://issues.apache.org/jira/browse/HBASE-13076
>             Project: HBase
>          Issue Type: Bug
>          Components: master, Region Assignment
>    Affects Versions: 2.0.0
>            Reporter: Andrey Stepachev
>            Assignee: Andrey Stepachev
>             Fix For: 2.0.0
>
>         Attachments: 23757f039d83f4f17ca18815eae70b28.log, HBASE-13076.patch
>
>
> Got situation where region can be opened while table is disabling by DisableTableHandler.
Here is relevant log for such situation. There is no clues who issued OPEN to region.
> Log file attached.
> UPD: A bit more details. It seems that even in case of new state put into meta, it still
possible to get previous state.
> That leads to one more round of assignment invoked in AssignmentManager#onRegionClosed.
> UPD: Table become ENABLED, thats leads to regions instructed to assign immediately on
onRegionClosed. BulkDisabler will not know about that and will wait indefinitely, because
it will not issue unassign for newly opened regions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message