[HBASE-72] [hbase] 'Normal' operation should not depend on throwing of exceptions (e.g. NotServingRegionException)

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Won't Fix
• Assignee: Unassigned
• Reporter: Michael Stack
• Created: 16/Aug/07 17:43
• Updated: 11/Jun/22 19:48
• Resolved: 08/Jun/14 21:42

Description

Region server and client logs will have lots of the following when a cluster is being loaded:

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)

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.

Issue Links

• is blocked by: HBASE-359 [hbase] Remove deprecated APIs and change signature of another in HRegionInterface