You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2014/11/03 23:23:33 UTC
[jira] [Updated] (HBASE-12416) RegionServerCallable should report
what host it was communicating with
[ https://issues.apache.org/jira/browse/HBASE-12416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk updated HBASE-12416:
---------------------------------
Fix Version/s: 0.99.2
0.98.8
2.0.0
Assignee: Nick Dimiduk
Status: Patch Available (was: Open)
> RegionServerCallable should report what host it was communicating with
> ----------------------------------------------------------------------
>
> Key: HBASE-12416
> URL: https://issues.apache.org/jira/browse/HBASE-12416
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Trivial
> Fix For: 2.0.0, 0.98.8, 0.99.2
>
> Attachments: HBASE-12416.00.patch
>
>
> While debugging failure in IntegrationTestMTTR, I get an almost-useful message like the following
> {noformat}
> java.util.concurrent.ExecutionException: org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=36, exceptions:
> Mon Nov 03 16:53:25 UTC 2014, null, java.net.SocketTimeoutException: callTimeout=60000, callDuration=70598: row '' on table 'IntegrationTestMTTR
> {noformat}
> We should include in the error message the host and full region info for the target of the operation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)