Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 44844 invoked from network); 21 Jul 2009 21:42:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Jul 2009 21:42:32 -0000 Received: (qmail 30414 invoked by uid 500); 21 Jul 2009 21:43:37 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 30373 invoked by uid 500); 21 Jul 2009 21:43:37 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 30137 invoked by uid 99); 21 Jul 2009 21:43:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jul 2009 21:43:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jul 2009 21:43:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id EF81D29A0015 for ; Tue, 21 Jul 2009 14:43:14 -0700 (PDT) Message-ID: <1694080499.1248212594979.JavaMail.jira@brutus> Date: Tue, 21 Jul 2009 14:43:14 -0700 (PDT) From: "stack (JIRA)" To: hbase-dev@hadoop.apache.org Subject: [jira] Created: (HBASE-1679) Flapping DNS does us more harm than it need to MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org 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 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.