hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1724) [hbase] 'Normal' operation should not depend on throwing of exceptions (e.g. NotServingRegionException)
Date Wed, 22 Aug 2007 04:18:30 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521675
] 

stack commented on HADOOP-1724:
-------------------------------

I didn't realize the exception only shows at DEBUG level.  That undoes the "exceptions in
the logs are unsettling" but though its not showing, we are still using the exception mechanism
to deal with normal operation.

Regards 'region moved' message, yes, region servers have no remembrance of regions past but
I was thinking the commit return message nothing more than the boolean -- succeeded/failed
-- that you suggested or a 'region ain't here'. 



> [hbase] 'Normal' operation should not depend on throwing of exceptions (e.g. NotServingRegionException)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1724
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1724
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: contrib/hbase
>            Reporter: stack
>            Assignee: Jim Kellerman
>            Priority: Minor
>
> Region server and client logs will have lots of the following when a cluster is being
loaded:
> {code}
> org.apache.hadoop.hbase.NotServingRegionException: hbaserepository,,7144829661993961256
>         at org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServer.java:1208)
>         at org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServer.java:1180)
>         at org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionServer.java:1122)
>         at org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionServer.java:985)
>         at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:340)
>         at org.apache.hadoop.ipc.Server$Handler.run(Server.java:566)
> {code}
> The NotServingRegionException exception is thrown when the remote server is no longer
serving the asked-for region (usually because its been split).  The server throws the exception
to provoke the client into making a new interrogation of region locations.
> It would be an improvement if such 'normal' operation was not built atop exceptions.
 For example, commits might return a 'region moved' message.

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