hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Molkov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1457) Limit transmission rate when transfering image between primary and secondary NNs
Date Tue, 02 Nov 2010 20:36:31 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927583#action_12927583
] 

Dmytro Molkov commented on HDFS-1457:
-------------------------------------

I like this approach overall. The patch looks good (not much going on in there except for
the move of the class).
The only comment is on the default value for bandwidth. I know without limiting we can get
speeds up to 10 times greater than the default you are putting in conf. Do you think it might
make sense to have a default behaviour be unlimited? And only people who want to turn the
feature on will specify some limit?

> Limit transmission rate when transfering image between primary and secondary NNs
> --------------------------------------------------------------------------------
>
>                 Key: HDFS-1457
>                 URL: https://issues.apache.org/jira/browse/HDFS-1457
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.22.0
>
>         Attachments: checkpoint-limitandcompress.patch, trunkThrottleImage.patch
>
>
> If the fsimage is very big. The network is full in a short time when SeconaryNamenode
do checkpoint, leading to Jobtracker access Namenode to get relevant file data to fail in
job initialization phase. So we limit transmission speed and compress transmission to resolve
the problem. 

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


Mime
View raw message