hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4352) Apply version of hbase-4015 to branch
Date Thu, 08 Dec 2011 05:55:40 GMT

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

stack commented on HBASE-4352:
------------------------------

Playing around w/ a cluster under load upgrading it from 0.90.4 to 0.90.5, all basically works
except stuff like the following:

{code}
2011-12-08 05:47:42,226 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Assigning
region TestTable,0006971712,1323323148059.2e97f25eefbd77765d64b0900d94e5ba. to sv4r12s38,7003,1323321454788
2011-12-08 05:47:42,226 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Handling transition=M_ZK_REGION_OFFLINE,
server=sv4r11s38:7001, region=2e97f25eefbd77765d64b0900d94e5ba
2011-12-08 05:47:42,229 WARN org.apache.hadoop.hbase.master.AssignmentManager: Failed assignment
of TestTable,0006971712,1323323148059.2e97f25eefbd77765d64b0900d94e5ba. to serverName=sv4r12s38,7003,1323321454788,
load=(requests=29558, regions=35, usedHeap=295, maxHeap=493), trying to assign elsewhere instead;
retry=9
org.apache.hadoop.ipc.RemoteException: java.io.IOException: java.lang.NoSuchMethodException:
org.apache.hadoop.hbase.regionserver.HRegionServer.openRegion(org.apache.hadoop.hbase.HRegionInfo,
int)
        at java.lang.Class.getMethod(Class.java:1605)
        at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:565)
        at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1039)

        at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:771)
        at org.apache.hadoop.hbase.ipc.HBaseRPC$Invoker.invoke(HBaseRPC.java:257)
        at $Proxy7.openRegion(Unknown Source)
        at org.apache.hadoop.hbase.master.ServerManager.sendRegionOpen(ServerManager.java:574)
        at org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1132)
        at org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:894)
        at org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:876)
        at org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:872)
        at org.apache.hadoop.hbase.master.handler.ClosedRegionHandler.process(ClosedRegionHandler.java:92)
        at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:156)
        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)
{code}

I see this when balancer tries to run (Its a 0.90.5 master running against a 0.90.4 cluster).

I don't think this too bad.  Its transient situation: i.e. you can't do a balancer till all
servers go up to 0.90.5.


                
> Apply version of hbase-4015 to branch
> -------------------------------------
>
>                 Key: HBASE-4352
>                 URL: https://issues.apache.org/jira/browse/HBASE-4352
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Blocker
>             Fix For: 0.90.5
>
>         Attachments: HBASE-4352_0.90.patch, HBASE-4352_0.90_1.patch
>
>
> Consider adding a version of hbase-4015 to 0.90.  It changes HRegionInterface so would
need move change to end of the Interface and then test that it doesn't break rolling restart.

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

        

Mime
View raw message