Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates
 209.85.223.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKtYt7DFYBKVGHKJ0iaGKtHSOu9C0yN-+XbLWgLjrP4Sj_Wn5A@mail.gmail.com>
References: 
 <CAKtYt7DFYBKVGHKJ0iaGKtHSOu9C0yN-+XbLWgLjrP4Sj_Wn5A@mail.gmail.com>
From: Harsh J <harsh@cloudera.com>
Date: Mon, 25 Mar 2013 21:01:24 +0530
Message-ID: 
 <CAOcnVr0oT94wjkiutedbXUKGxwwgd6_37wKXsowgMgV3k+r9Kw@mail.gmail.com>
Subject: Re: DataNode heartbeat average time peaks
To: "<user@hadoop.apache.org>" <user@hadoop.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

What's your fsimage size? If its too high you would want to control
the checkpoint transfer bandwidth to not affect the load at the NN.
This is available via the JIRA HDFS-1457.


On Mon, Mar 25, 2013 at 8:13 PM, Ivan Tretyakov
<itretyakov@griddynamics.com> wrote:
> Hi!
>
> We see DataNode heartbeat average time peaks in Ganglia up to 20-70 seconds
> while SecondaryNameNode performs checkpointing.
> See attached screenshots please.
>
> I would like to clarify if it is Ok, or not. And what kind of consequences
> and risks it could bring up.
>
> --
> Best Regards
> Ivan Tretyakov


--
Harsh J