Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 27 Oct 2015 00:05:28 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12908071.1445904154000.66050.1445904328019@Atlassian.JIRA>
In-Reply-To: <JIRA.12908071.1445904154000@Atlassian.JIRA>
References: <JIRA.12908071.1445904154000@Atlassian.JIRA>
 <JIRA.12908071.1445904154997@arcas>
Subject: [jira] [Updated] (HDFS-9311) Support optional offload of NameNode
 HA service health checks to a separate RPC server.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Nauroth updated HDFS-9311:
--------------------------------
    Attachment: HDFS-9311.001.patch

This is similar in spirit to what I proposed for DataNode liveness reporting in HDFS-9239.  I decided to tackle this one first, because the implementation is simpler and can lay the groundwork for HDFS-9239.  I have attached patch v001.

> Support optional offload of NameNode HA service health checks to a separate RPC server.
> ---------------------------------------------------------------------------------------
>
>                 Key: HDFS-9311
>                 URL: https://issues.apache.org/jira/browse/HDFS-9311
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, namenode
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HDFS-9311.001.patch
>
>
> When a NameNode is overwhelmed with load, it can lead to resource exhaustion of the RPC handler pools (both client-facing and service-facing).  Eventually, this blocks the health check RPC issued from ZKFC, which triggers a failover.  Depending on fencing configuration, the former active NameNode may be killed.  In an overloaded situation, the new active NameNode is likely to suffer the same fate, because client load patterns don't change after the failover.  This can degenerate into flapping between the 2 NameNodes without real recovery.  If a NameNode had been killed by fencing, then it would have to transition through safe mode, further delaying time to recovery.
> This issue proposes a separate, optional RPC server at the NameNode for isolating the HA health checks.  These health checks are lightweight operations that do not suffer from contention issues on the namesystem lock or other shared resources.  Isolating the RPC handlers is sufficient to avoid this situation.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)