Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 11 Nov 2013 19:13:17 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12678638.1384197172233.52799.1384197197902@arcas>
In-Reply-To: <JIRA.12678638.1384197172233@arcas>
References: <JIRA.12678638.1384197172233@arcas>
Subject: [jira] [Created] (HDFS-5496) Make replication queue initialization
 asynchronous
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kihwal Lee created HDFS-5496:
--------------------------------

             Summary: Make replication queue initialization asynchronous
                 Key: HDFS-5496
                 URL: https://issues.apache.org/jira/browse/HDFS-5496
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: namenode
            Reporter: Kihwal Lee


Today, initialization of replication queues blocks safe mode exit and certain HA state transitions. For a big name space, this can take hundreds of seconds with the FSNamesystem write lock held.  During this time, important requests (e.g. initial block reports, heartbeat, etc) are blocked.

The effect of delaying the initialization would be not starting replication right away, but I think the benefit outweighs. If we make it asynchronous, the work per iteration should be limited, so that the lock duration is capped. 

If full/incremental block reports and any other requests that modifies block state properly performs replication checks while the blocks are scanned and the queues populated in background, every block will be processed. (Some may be done twice)  The replication monitor should run even before all blocks are processed.

This will allow namenode to exit safe mode and start serving immediately even with a big name space. It will also reduce the HA failover latency.


--
This message was sent by Atlassian JIRA
(v6.1#6144)