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 2009/07/19 09:20:14 UTC
[jira] Updated: (HBASE-1673) .META. regionserver died, cluster
recovered but not UI
[ https://issues.apache.org/jira/browse/HBASE-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1673:
-------------------------
Description:
Getting 500 in UI:
{code}
org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to contact region server null for region , row '', but failed after 3 attempts.
Exceptions:
java.net.ConnectException: Call to /208.76.44.141:60020 failed on connection exception: java.net.ConnectException: Connection refused
...
{code}
Doesn't recover.
I think issue is here in HCM:
{code}
} catch (IOException e) {
if (e instanceof RemoteException) {
e = RemoteExceptionHandler.decodeRemoteException(
(RemoteException) e);
}
if (tries < numRetries - 1) {
if (LOG.isDebugEnabled()) {
LOG.debug("locateRegionInMeta attempt " + tries + " of " +
this.numRetries + " failed; retrying after sleep of " +
getPauseTime(tries), e);
}
relocateRegion(parentTable, metaKey);
} else {
...
{code}
The call to relocateRegion is going to result in an attempt at finding the .META.,,1 region in .META. which will get a ConnectionException again.
On ConnectionException, should be backing up and going to -ROOT- to find new location of .META.
was:
Getting 500 in UI:
{code}
> .META. regionserver died, cluster recovered but not UI
> ------------------------------------------------------
>
> Key: HBASE-1673
> URL: https://issues.apache.org/jira/browse/HBASE-1673
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
>
> Getting 500 in UI:
> {code}
> org.apache.hadoop.hbase.client.RetriesExhaustedException: Trying to contact region server null for region , row '', but failed after 3 attempts.
> Exceptions:
> java.net.ConnectException: Call to /208.76.44.141:60020 failed on connection exception: java.net.ConnectException: Connection refused
> ...
> {code}
> Doesn't recover.
> I think issue is here in HCM:
> {code}
> } catch (IOException e) {
> if (e instanceof RemoteException) {
> e = RemoteExceptionHandler.decodeRemoteException(
> (RemoteException) e);
> }
> if (tries < numRetries - 1) {
> if (LOG.isDebugEnabled()) {
> LOG.debug("locateRegionInMeta attempt " + tries + " of " +
> this.numRetries + " failed; retrying after sleep of " +
> getPauseTime(tries), e);
> }
> relocateRegion(parentTable, metaKey);
> } else {
> ...
> {code}
> The call to relocateRegion is going to result in an attempt at finding the .META.,,1 region in .META. which will get a ConnectionException again.
> On ConnectionException, should be backing up and going to -ROOT- to find new location of .META.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.