stack created HBASE-9796:
----------------------------
Summary: npe in RegionServerCallable
Key: HBASE-9796
URL: https://issues.apache.org/jira/browse/HBASE-9796
Project: HBase
Issue Type: Bug
Affects Versions: 0.96.0
Reporter: stack
Saw this running hbase-it suite on test cluster. Its tricky. Needs a little
study. Connection or location became null in this code when we go to clear the
caches:
{code}
if (t instanceof SocketTimeoutException ||
t instanceof ConnectException ||
t instanceof RetriesExhaustedException ||
(location != null &&
getConnection().isDeadServer(location.getServerName()))) {
// if thrown these exceptions, we clear all the cache entries that
// map to that slow/dead server; otherwise, let cache miss and ask
// hbase:meta again to find the new location
getConnection().clearCaches(location.getServerName());
{code}
Here is exception seen:
2013-10-17 09:05:44,569 INFO [Thread-9] actions.Action: Killed region
server:a1811.halxg.cloudera.com,60020,1382025707403. Reported num of rs:4
2013-10-17 09:05:44,569 INFO [Thread-9] actions.Action: Sleeping for:2961
Exception in thread "HBaseUpdaterThread_3" java.lang.NullPointerException
at
org.apache.hadoop.hbase.client.RegionServerCallable.throwable(RegionServerCallable.java:120)
at
org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:124)
at org.apache.hadoop.hbase.client.HTable.get(HTable.java:755)
at
org.apache.hadoop.hbase.util.MultiThreadedUpdater$HBaseUpdaterThread.run(MultiThreadedUpdater.java:159)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
