[
https://issues.apache.org/jira/browse/HBASE-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134227#comment-13134227
]
stack commented on HBASE-4578:
------------------------------
bq. // It said that the cluster has 10 regions. but the cluster has 8 regions
and 2 offlined regions.
I think the fact that it says 10 regions updated seems fine. When you say
offlined, what do you mean? They are offline parents of splits? If so, they
should probably not be counted but no harm done I'd say. You thinking that we
should not be altering split, offlined regions? That sounds good but in
another issue?
> NPE when altering a table that has moving regions
> -------------------------------------------------
>
> Key: HBASE-4578
> URL: https://issues.apache.org/jira/browse/HBASE-4578
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: Jean-Daniel Cryans
> Assignee: gaojinchao
> Priority: Blocker
> Fix For: 0.92.0
>
> Attachments: HBASE-4578_Trunk_V1.patch, HBASE-4578_trial_Trunk.patch
>
>
> I'm still not a 100% sure on the source of this error, but here's what I was
> able to get twice while altering a table that was doing a bunch of splits:
> {quote}
> 2011-10-11 23:48:59,344 INFO
> org.apache.hadoop.hbase.master.handler.SplitRegionHandler: Handled SPLIT
> report);
> parent=TestTable,0002608338,1318376880454.a75d6815fdfc513fb1c8aabe086c6763.
> daughter
> a=TestTable,0002608338,1318376938764.ef170ff6cd8695dc8aec92e542dc9ac1.daughter
> b=TestTable,0003301408,1318376938764.36eb2530341bd46888ede312c5559b5d.
> 2011-10-11 23:49:09,579 DEBUG
> org.apache.hadoop.hbase.master.handler.TableEventHandler: Ignoring table not
> disabled exception for supporting online schema changes.
> 2011-10-11 23:49:09,580 INFO
> org.apache.hadoop.hbase.master.handler.TableEventHandler: Handling table
> operation C_M_MODIFY_TABLE on table TestTable
> 2011-10-11 23:49:09,612 INFO org.apache.hadoop.hbase.util.FSUtils:
> TableInfoPath = hdfs://sv4r11s38:9100/hbase/TestTable/.tableinfo tmpPath =
> hdfs://sv4r11s38:9100/hbase/TestTable/.tmp/.tableinfo.1318376949612
> 2011-10-11 23:49:09,692 INFO org.apache.hadoop.hbase.util.FSUtils:
> TableDescriptor stored. TableInfoPath =
> hdfs://sv4r11s38:9100/hbase/TestTable/.tableinfo
> 2011-10-11 23:49:09,693 INFO org.apache.hadoop.hbase.util.FSUtils: Updated
> tableinfo=hdfs://sv4r11s38:9100/hbase/TestTable/.tableinfo to blah
> 2011-10-11 23:49:09,695 INFO
> org.apache.hadoop.hbase.master.handler.TableEventHandler: Bucketing regions
> by region server...
> 2011-10-11 23:49:09,695 DEBUG org.apache.hadoop.hbase.client.MetaScanner:
> Scanning .META. starting at row=TestTable,,00000000000000 for max=2147483647
> rows
> 2011-10-11 23:49:09,709 DEBUG
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
> The connection to hconnection-0x132f043bbde02e9 has been closed.
> 2011-10-11 23:49:09,709 ERROR org.apache.hadoop.hbase.executor.EventHandler:
> Caught throwable while processing event C_M_MODIFY_TABLE
> java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:324)
> at java.util.TreeMap.containsKey(TreeMap.java:209)
> at
> org.apache.hadoop.hbase.master.handler.TableEventHandler.reOpenAllRegions(TableEventHandler.java:114)
> at
> org.apache.hadoop.hbase.master.handler.TableEventHandler.process(TableEventHandler.java:90)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:168)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> {quote}
> The first time the shell reported that all the regions were updated
> correctly, the second time it got stuck for a while:
> {quote}
> 6/14 regions updated.
> 0/14 regions updated.
> ...
> 0/14 regions updated.
> 2/16 regions updated.
> ...
> 2/16 regions updated.
> 8/9 regions updated.
> ...
> 8/9 regions updated.
> {quote}
> After which I killed it, redid the alter and it worked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
