Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <2731099.4661288853145184.JavaMail.jira@thor>
Date: Thu, 4 Nov 2010 02:45:45 -0400 (EDT)
From: "Konstantin Shvachko (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1457) Limit transmission rate when
 transfering image between primary and secondary NNs
In-Reply-To: <20990968.146771287081033153.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Shvachko commented on HDFS-1457:
-------------------------------------------

Looks like {{imageTransferThrottler}} is instantiated but not used in {{FSImage}}. Should it be moved into {{GetImageServlet}} instead?

> 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, trunkThrottleImage1.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.