You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/04/16 18:47:22 UTC
[jira] Commented: (HBASE-72) [hbase] 'Normal' operation should not
depend on throwing of exceptions (e.g. NotServingRegionException)
[ https://issues.apache.org/jira/browse/HBASE-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589640#action_12589640 ]
stack commented on HBASE-72:
----------------------------
>From the list, a new user is confused by this 'Exception'; thinks it an error:
{code}
Message-ID: <25...@mail.gmail.com>
Date: Tue, 15 Apr 2008 15:54:29 -0700
From: "Daniel Leffel" <da...@gmail.com>
To: hbase-user@hadoop.apache.org
Subject: Re: Region Server Processes Exit Unexpectedly during Moderate Load MapReduce
In-Reply-To: <25...@mail.gmail.com>
References: <25...@mail.gmail.com>
<48...@duboce.net>
<25...@mail.gmail.com>
Now I just got this exception:
2008-04-15 18:50:02,107 DEBUG org.apache.hadoop.hbase.HStore: maximum
sequence id for hstore 856584617/rule_id is 68555204
2008-04-15 18:50:02,284 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 8 on 60020, call
batchUpdate(category_rule_pricebin_statistics,2332627_1_-11,1208293443363,
9223372036854775807, org.apache.hadoop.hbase.io.BatchUpdate@19d277e)
from 10.252.50.36:53955: error:
org.apache.hadoop.hbase.NotServingRegionException:
category_rule_pricebin_statistics,2332627_1_-11,1208293443363
org.apache.hadoop.hbase.NotServingRegionException:
category_rule_pricebin_statistics,2332627_1_-11,1208293443363
...
{code}
> [hbase] 'Normal' operation should not depend on throwing of exceptions (e.g. NotServingRegionException)
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-72
> URL: https://issues.apache.org/jira/browse/HBASE-72
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: stack
> Priority: Trivial
>
> 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.