|
|
| 'Normal' operation should not depend on
throwing of exceptio |
 
United States |
2007-08-16 12:45:32 |
[hbase] 'Normal' operation should not depend on throwing of
exceptions (e.g. NotServingRegionException)
------------------------------------------------------------
-------------------------------------------
Key: HADOOP-1724
URL: htt
ps://issues.apache.org/jira/browse/HADOOP-1724
Project: Hadoop
Issue Type: Improvement
Components: contrib/hbase
Reporter: stack
Priority: Minor
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(HRegionServe
r.java:1208)
at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1180)
at
org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionSer
ver.java:1122)
at
org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionSer
ver.java:985)
at
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
|
| 'Normal' operation should not depend on
throwing of excepti |
United States |
2007-08-20 14:21:31 |
[ https://issues.apache.org/jira/browse/HADOOP-1724?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman reassigned HADOOP-1724:
-------------------------------------
Assignee: Jim Kellerman
> [hbase] 'Normal' operation should not depend on
throwing of exceptions (e.g. NotServingRegionException)
>
------------------------------------------------------------
-------------------------------------------
>
> Key: HADOOP-1724
> URL: htt
ps://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:
>
> org.apache.hadoop.hbase.NotServingRegionException:
hbaserepository,,7144829661993961256
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1208)
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1180)
> at
org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionSer
ver.java:1122)
> at
org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionSer
ver.java:985)
> at
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
|
| 'Normal' operation should not depend on
throwing of except |
United States |
2007-08-21 11:14:31 |
[ https://issues.apache.org/jira/browse
/HADOOP-1724?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12521511 ]
Jim Kellerman commented on HADOOP-1724:
---------------------------------------
Looking at the (non-deprecated) methods in HRegionInterface,
there are two that could return a status: batchUpdate and
close (a scanner).
However, the remainder return a value.
The Java paradigm seems (to me at least) to be that methods
return values or void and not a status code. Errors are
handled by throwing exceptions. This is the paradigm that is
followed by the other Hadoop RPC protocols.
A client sending a request to the wrong server, either due
to a bug or because the region has moved to another server
feels like an error to me, and throwing an exception to get
the client to 'recalibrate' seems ok.
The server really has no other choice because input
parameters are final (any modification to them are not
returned to the client).
The only other thing we could do is wrap each returned value
in another Writable which always contains a "status
message". This does not feel like the right paradigm to
me.
The only other solution I can think of is to make two RPCs
for every one we make today. The first asks the server,
"Are you serving this region?", and based on that
answer either sends the "real" message or
"recalibrates". Seems highly inefficient to me.
If there are other ideas I have overlooked, please comment
here.
> [hbase] 'Normal' operation should not depend on
throwing of exceptions (e.g. NotServingRegionException)
>
------------------------------------------------------------
-------------------------------------------
>
> Key: HADOOP-1724
> URL: htt
ps://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:
>
> org.apache.hadoop.hbase.NotServingRegionException:
hbaserepository,,7144829661993961256
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1208)
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1180)
> at
org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionSer
ver.java:1122)
> at
org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionSer
ver.java:985)
> at
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
|
| 'Normal' operation should not depend on
throwing of except |
United States |
2007-08-21 13:57:31 |
[ https://issues.apache.org/jira/browse
/HADOOP-1724?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12521550 ]
stack commented on HADOOP-1724:
-------------------------------
Here's a couple of comments.
Those that return a value are all reads I believe. Its
unlikely a read will encounter a NotServingRegionException.
If they do, the circumstances are probably 'exceptional'
such as a crashed region server-- so an exception seems
appropriate here.
On the other hand, a stream of writes ineluctably provokes
splits and region relocations. IMO, such splits are
not-unexpected and do not constitute an 'error', nor an
'exceptional' or 'abnormal' condition. Use of NSRE
realigning the client strikes me as an instance of using
exceptions to ordain program control.
Seeing exceptions in the logs though all is working properly
is unsettling.
batchUpdate commit would seem to be the main provocateur of
NotServingRegionExceptions during 'normal' operation.
Currently it returns void. Would it be odd if just this
one method returned a status code that had to be checked?
(Its rough counterpart in JDBC has a primitive status
facility: http://java.sun.com/j2se/1.5.0/docs/
api/java/sql/Statement.html#executeBatch()).
> [hbase] 'Normal' operation should not depend on
throwing of exceptions (e.g. NotServingRegionException)
>
------------------------------------------------------------
-------------------------------------------
>
> Key: HADOOP-1724
> URL: htt
ps://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:
>
> org.apache.hadoop.hbase.NotServingRegionException:
hbaserepository,,7144829661993961256
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1208)
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1180)
> at
org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionSer
ver.java:1122)
> at
org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionSer
ver.java:985)
> at
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
|
| 'Normal' operation should not depend on
throwing of except |
United States |
2007-08-21 14:23:30 |
[ https://issues.apache.org/jira/browse
/HADOOP-1724?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12521557 ]
Jim Kellerman commented on HADOOP-1724:
---------------------------------------
Ok, I'll buy that argument. We'll change the API for commit
only.
> [hbase] 'Normal' operation should not depend on
throwing of exceptions (e.g. NotServingRegionException)
>
------------------------------------------------------------
-------------------------------------------
>
> Key: HADOOP-1724
> URL: htt
ps://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:
>
> org.apache.hadoop.hbase.NotServingRegionException:
hbaserepository,,7144829661993961256
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1208)
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1180)
> at
org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionSer
ver.java:1122)
> at
org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionSer
ver.java:985)
> at
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
|
| 'Normal' operation should not depend on
throwing of except |
United States |
2007-08-21 16:24:30 |
[ https://issues.apache.org/jira/browse
/HADOOP-1724?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12521597 ]
Jim Kellerman commented on HADOOP-1724:
---------------------------------------
There are two cases for batchUpdate that I would consider to
be "normal operation" as you have described it.
Both could result from a region split:
NotServingRegionException, and WrongRegionException (in
which the row being updated falls outside the row range of
the region that is being served).
The other exceptions that might get thrown during a batch
update really are problems: region is offline, region is
closed, etc. These will remain exceptions.
batchUpdate will be modified to return a boolean: true if
successful; false if the server caught a
NotServingRegionException or WrongRegionException. When the
client receives a false answer, it needs to
"recalibrate"
> [hbase] 'Normal' operation should not depend on
throwing of exceptions (e.g. NotServingRegionException)
>
------------------------------------------------------------
-------------------------------------------
>
> Key: HADOOP-1724
> URL: htt
ps://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:
>
> org.apache.hadoop.hbase.NotServingRegionException:
hbaserepository,,7144829661993961256
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1208)
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1180)
> at
org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionSer
ver.java:1122)
> at
org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionSer
ver.java:985)
> at
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
|
| 'Normal' operation should not depend on
throwing of except |
United States |
2007-08-21 19:28:30 |
[ https://issues.apache.org/jira/browse
/HADOOP-1724?page=com.atlassian.jira.plugin.system.issuetabp
anels:comment-tabpanel#action_12521643 ]
Jim Kellerman commented on HADOOP-1724:
---------------------------------------
The only time a message is written to the logs is if DEBUG
level logging is enabled. Under normal operation, the log
level should be set to INFO in which case no stack trace
will be visible unless the client runs out of retries (in
which case both NotServingRegionException and
WrongRegionException should be treated as errors).
commit can not return a "region moved" message
because the region server has no idea what happened some
time earlier. It just knows that the region that was
requested of it is not one of the ones it is serving.
Debug logs are not pretty and if someone does enable them,
then they are not operating "normally".
For these reasons I'm inclined to not make this change.
> [hbase] 'Normal' operation should not depend on
throwing of exceptions (e.g. NotServingRegionException)
>
------------------------------------------------------------
-------------------------------------------
>
> Key: HADOOP-1724
> URL: htt
ps://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:
>
> org.apache.hadoop.hbase.NotServingRegionException:
hbaserepository,,7144829661993961256
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1208)
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1180)
> at
org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionSer
ver.java:1122)
> at
org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionSer
ver.java:985)
> at
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
|
| 'Normal' operation should not depend on
throwing of except |
United States |
2007-08-21 23:18:30 |
[ https://issues.apache.org/jira/browse
/HADOOP-1724?page=com.atlassian.jira.plugin.system.issuetabp
anels: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: htt
ps://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:
>
> org.apache.hadoop.hbase.NotServingRegionException:
hbaserepository,,7144829661993961256
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1208)
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1180)
> at
org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionSer
ver.java:1122)
> at
org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionSer
ver.java:985)
> at
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
|
| 'Normal' operation should not depend on
throwing of excepti |
United States |
2007-08-21 23:54:30 |
[ https://issues.apache.org/jira/browse/HADOOP-1724?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman resolved HADOOP-1724.
-----------------------------------
Resolution: Won't Fix
Since there are other implementations that subclass
HRegionServer and HTable, We should not change the API
without a better reason for doing so.
> [hbase] 'Normal' operation should not depend on
throwing of exceptions (e.g. NotServingRegionException)
>
------------------------------------------------------------
-------------------------------------------
>
> Key: HADOOP-1724
> URL: htt
ps://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:
>
> org.apache.hadoop.hbase.NotServingRegionException:
hbaserepository,,7144829661993961256
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1208)
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1180)
> at
org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionSer
ver.java:1122)
> at
org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionSer
ver.java:985)
> at
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
|
| 'Normal' operation should not depend on
throwing of excepti |
United States |
2007-08-22 12:20:30 |
[ https://issues.apache.org/jira/browse/HADOOP-1724?page=co
m.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman reopened HADOOP-1724:
-----------------------------------
Re-opening issue.
While it would be an improvement, there are a couple of
reasons not to do it:
- It changes the wire protocol and because we cannot
overload the method (since the only change is in the
return), we can't deprecate the current interface and
replace it with a method of the same name. Instead we would
have to create a new API with a different name.
- What we currently have works and perhaps the problem
described above is a good reason not to do it.
> [hbase] 'Normal' operation should not depend on
throwing of exceptions (e.g. NotServingRegionException)
>
------------------------------------------------------------
-------------------------------------------
>
> Key: HADOOP-1724
> URL: htt
ps://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:
>
> org.apache.hadoop.hbase.NotServingRegionException:
hbaserepository,,7144829661993961256
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1208)
> at
org.apache.hadoop.hbase.HRegionServer.getRegion(HRegionServe
r.java:1180)
> at
org.apache.hadoop.hbase.HRegionServer.startUpdate(HRegionSer
ver.java:1122)
> at
org.apache.hadoop.hbase.HRegionServer.batchUpdate(HRegionSer
ver.java:985)
> at
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
thodAccessorImpl.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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
online.
|
|