hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-2499) Race condition when disabling a table leaves regions in transition
Date Wed, 28 Apr 2010 22:11:54 GMT

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

Jean-Daniel Cryans updated HBASE-2499:
--------------------------------------

    Attachment: HBASE-2499.patch

This patch adds a new check to .META. (expensive!) before calling setClosing. Also, to lower
the .META. stress, it prevents unnecessary puts in postProcessMeta. I'm now able to disable
my big table without any issue.

> Race condition when disabling a table leaves regions in transition
> ------------------------------------------------------------------
>
>                 Key: HBASE-2499
>                 URL: https://issues.apache.org/jira/browse/HBASE-2499
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.3
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Blocker
>             Fix For: 0.20.4, 0.21.0
>
>         Attachments: HBASE-2499.patch
>
>
> A lot of people reported that weren't able to add/delete a column because only some of
the regions got the modification. I personally thought it was due to the CME bug in the Master,
but I'm able to easily reproduce on 0.20.4 on a 1800 regions table.
> Since 0.20.3, we now call disableTable after every retry to make sure we don't miss any
region. This creates a race where while we scan .META. in TableOperation, a region could be
reported as closed after we scanned the row. We end up processing it like if it was assigned
and we put it back into regionsInTransition. We need to either query .META. before processing
each region or make some more check to see if the region was closed.
> This kills the RC in my book.
> In the mean time, anyone getting this can restart their HBase and it will pick up the
change.

-- 
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