Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 11 Nov 2015 11:09:10 +0000 (UTC)
From: "He Tianyi (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12912130.1447239614000.38299.1447240150941@Atlassian.JIRA>
In-Reply-To: <JIRA.12912130.1447239614000@Atlassian.JIRA>
References: <JIRA.12912130.1447239614000@Atlassian.JIRA>
 <JIRA.12912130.1447239614640@arcas>
Subject: [jira] [Updated] (HDFS-9412) getBlocks occupies FSLock and takes
 too long to complete
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

He Tianyi updated HDFS-9412:
----------------------------
    Description: 
{{getBlocks}} in {{NameNodeRpcServer}} acquires a read lock then may take a long time to complete (probably several seconds, if number of blocks are too much). 
During this period, other threads attempting to acquire write lock will wait. 
In an extreme case, RPC handlers are occupied by one reader thread calling {{getBlocks}} and all other threads waiting for write lock, rpc server acts like hung. Unfortunately, this tends to happen in heavy loaded cluster, since read operations come and go fast (they do not need to wait), leaving write operations waiting.

Looks like we can optimize this thing like DN block report did in past, by splitting the operation into smaller sub operations, and let other threads do their work between each sub operation. The whole result is returned at once, though (one thing different from DN block report). 
I am not sure whether this will work. Any better idea?

  was:
{{getBlocks}} in {{NameNodeRpcServer}} acquires a read lock then may take a long time to complete (probably several seconds, if number of blocks are too much). 
During this period, other threads attempting to acquire write lock will wait. 
In an extreme case, RPC handlers are occupied by one reader thread calling {{getBlocks}} and all other threads waiting for write lock, rpc server acts like hung. Unfortunately, this tends to happen in heavy loaded cluster, since read operations come and go fast (they do not need to wait), leaving write operations waiting.

Looks like we can optimize this thing like DN block report did in past, by splitting the operation into smaller sub operations, and let other threads do their work between each sub operation. The whole result is returned at once, though (one thing different from DN block report). But there will be no more starvation.
I am not sure whether this will work. Any better idea?


> getBlocks occupies FSLock and takes too long to complete
> --------------------------------------------------------
>
>                 Key: HDFS-9412
>                 URL: https://issues.apache.org/jira/browse/HDFS-9412
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: He Tianyi
>            Assignee: He Tianyi
>
> {{getBlocks}} in {{NameNodeRpcServer}} acquires a read lock then may take a long time to complete (probably several seconds, if number of blocks are too much). 
> During this period, other threads attempting to acquire write lock will wait. 
> In an extreme case, RPC handlers are occupied by one reader thread calling {{getBlocks}} and all other threads waiting for write lock, rpc server acts like hung. Unfortunately, this tends to happen in heavy loaded cluster, since read operations come and go fast (they do not need to wait), leaving write operations waiting.
> Looks like we can optimize this thing like DN block report did in past, by splitting the operation into smaller sub operations, and let other threads do their work between each sub operation. The whole result is returned at once, though (one thing different from DN block report). 
> I am not sure whether this will work. Any better idea?


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