Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1120743134.1233770521133.JavaMail.jira@brutus>
Date: Wed, 4 Feb 2009 10:02:01 -0800 (PST)
From: "Jonathan Gray (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1175) HBA administrative tools do not work
 when specifying regionName
In-Reply-To: <876284100.1233618960070.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Gray commented on HBASE-1175:
--------------------------------------

Yes.  Have run this on every region in one of my clusters a few times in the past two days without a problem.

+1 to commit

> HBA administrative tools do not work when specifying regionName
> ---------------------------------------------------------------
>
>                 Key: HBASE-1175
>                 URL: https://issues.apache.org/jira/browse/HBASE-1175
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client, master
>    Affects Versions: 0.19.0, 0.20.0
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>             Fix For: 0.19.1, 0.20.0
>
>         Attachments: hbase-1175-v1.patch, hbase-1175-v2.patch
>
>
> HBaseAdmin administrative functions allow tableName or regionName through the API.  Things are okay if we pass tableName, but when using regionName the code in HMaster is incorrect.  It is expecting to be passed tableName and startRow, but we are passing null and regionName.  Patch will fix master to handle this case properly.
> Log for good measure:
> {code}
> [hbase@mb0 StyBase]$ java TableMaintenance chunks
> Running maintenance on table 'chunks'
> Table contains 2 regions
>   > Flushing region {chunks,,1229390225893}
> EXCEPTION FLUSHING REGION! [org.apache.hadoop.ipc.RemoteException: java.io.IOException: Invalid arguments to openScanner
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:1695)
>         at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:616)
>         at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:632)
>         at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:895)
> Caused by: java.lang.NullPointerException: firstRow for scanner is null
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:1692)
>         ... 5 more
>         at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:701)
>         at org.apache.hadoop.hbase.ipc.HBaseRPC$Invoker.invoke(HBaseRPC.java:321)
>         at $Proxy2.openScanner(Unknown Source)
>         at org.apache.hadoop.hbase.master.HMaster.getTableRegionClosest(HMaster.java:725)
>         at org.apache.hadoop.hbase.master.HMaster.modifyTable(HMaster.java:804)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:616)
>         at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:632)
>         at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:895)
> ]
> {code}

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