Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <7874814.1188448830561.JavaMail.jira@brutus>
Date: Wed, 29 Aug 2007 21:40:30 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-1816) [hbase] Scan of .META. does socket
 timeout over and over again (rather than
In-Reply-To: <14057506.1188448711071.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HADOOP-1816:
--------------------------

    Attachment: excerpt.txt

Log excerpt illustrating the problem.

> [hbase] Scan of .META. does socket timeout over and over again (rather than 
> ----------------------------------------------------------------------------
>
>                 Key: HADOOP-1816
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1816
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>            Reporter: stack
>            Priority: Trivial
>         Attachments: excerpt.txt
>
>
> A mismatch in the code on the cluster revealed an infinite loop.  The .META. scanner is doing a socket timeout trying to contact a borked region server (The borked server was having trouble contacting hdfs because of of code version mismatch -- it was sort-of-working).  We retry the timeout up to the retry limit but then rather than try and redeploy the unreachable .META. we just drop back into scanning at the old location.... I'll attach a log that illustrates the goings-on.
> I think this likely a trivial issue since it shouldn't really ever happen....

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.