hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-627) Disable table doesn't work reliably
Date Fri, 27 Jun 2008 17:55:45 GMT

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

Jim Kellerman commented on HBASE-627:

> stack - 27/Jun/08 08:18 AM
> HBASE-713 is about offliining/onlining not being reliiable on branch. I got around the
> issue by writing a script that went through the regions that wouldn't offline individually
> offlining them. I was then able to add my new column. But I just noticed that the add
> column didn't apply to all regions, just to most. Would suggest that this issue also
> cover this case; i.e. not just enabling/disabling but also guarantee that
> add/edit/delete of columns works too. 

This is a bug in both column operations and table deletion.

If they think a region is being served that region is not added to the list of regions to
Unfortunately, determination of whether a region is being served is imprecise, because it
is based on info:server and info:startcode matching a server that the master knows about.

When a region is offlined, it should delete the server and startcode fields. Apparently sometimes,
these fields are not deleted and those regions never get processed, even though the region
info indicates the region is disabled.

> Disable table doesn't work reliably
> -----------------------------------
>                 Key: HBASE-627
>                 URL: https://issues.apache.org/jira/browse/HBASE-627
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.2.0
>         Environment: Hadoop/HBase on two nodes
>            Reporter: Michaela Buergle
>            Assignee: Jim Kellerman
>            Priority: Critical
>             Fix For: 0.2.0
>         Attachments: disableTable31.log, disableTable5.log, patch.txt
> When creating a couple of tables like this:
> 1) create an empty table
> 2) disable table, add new column family, enable table
> 3) put 100 small documents into newly created column
> around once in 10 tries the disable doesn't happen.
> I have no clue as to why the table isn't disabled in the first place, but if this occurs,
two things in HBaseAdmin.disableTable() strike me as odd:
> - after numRetries tries to wait for disabling we exit the loop; there is no exception
or error message:
> ...
> 2008-05-14 16:19:47,903 INFO org.apache.hadoop.hbase.client.HBaseAdmin: Disabled table
> 2008-05-14 16:19:47,910 INFO org.apache.hadoop.ipc.Server: IPC Server handler 3 on 60000,
call addColumn(table31, {name: document, max versions: 3, compression: NONE, in memory: false,
block cache enabled: false, max length: 2147483647, time to live: FOREVER, bloom filter: none})
from XXX.XX.40.36:47116: error: org.apache.hadoop.hbase.TableNotDisabledException: table31
> ...
> - the scanner iterates over HRegionInfos of several tables. If any one of those is disabled,
we also leave the loop as if the requested table had been disabled.
> I've had this disabling problem occur quite reliably over the last days - today I couldn't
reproduce it, though HBase version hasn't changed. ???

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

View raw message