hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5481) Namenode should return lease recovery request with other requests
Date Thu, 19 Mar 2009 19:56:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683591#action_12683591

Hairong Kuang commented on HADOOP-5481:

Does your kind of request have to be combined with other requests? Is it Ok that the new request
is sent separately with the highest priority? Initial heartbeat design prefers one single
request per heartbeat. HADOOP-5034 was a cautious change to solve a deadlock situation. Currently
a DataNode processes heartbeat requests inline with sending heartbeats in one thread. If too
many requests get sent to DataNode in one heartbeat reply, it may delay DataNode sending next
heartbeat to NameNode. 

> Namenode should return lease recovery request with other requests
> -----------------------------------------------------------------
>                 Key: HADOOP-5481
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5481
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Kan Zhang
>            Assignee: Kan Zhang
>         Attachments: HADOOP-5481.patch
> HADOOP-5034 modified NN to return both replication and deletion requests to DN in one
reply to a heartbeat. However, the lease recovery request is still sent separately by itself.
Is there a reason for this? If not, I suggest we combine them together. This will make it
less confusing when adding new types of requests, which are combinable as well.

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

View raw message