Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1973450567.142061264805614646.JavaMail.jira@brutus.apache.org>
Date: Fri, 29 Jan 2010 22:53:34 +0000 (UTC)
From: "Kannan Muthukkaruppan (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1679) Flapping DNS does us more harm than
 it need to
In-Reply-To: <1694080499.1248212594979.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806544#action_12806544 ] 

Kannan Muthukkaruppan commented on HBASE-1679:
----------------------------------------------

s/asked to restarted/asked to restart

> Flapping DNS does us more harm than it need to
> ----------------------------------------------
>
>                 Key: HBASE-1679
>                 URL: https://issues.apache.org/jira/browse/HBASE-1679
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>             Fix For: 0.21.0
>
>
> Over in HBASE-1675, JSharp has posted logs where a temporary DNS outage does his cluster a death blow.
> When cluster members report in, the master composes the regionserver name by doing a hostname lookup and appending it to port and startcode passed over by the regionserver.  The host lookup during a DNS outage when from name to IP.  Master then thought this regionserver an unknown host and told it restart.... and so on.
> If the regionserver composed its name once, it could pass this the master and avoid a DNS lookup per regionserver report.

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