Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B9AF617F02 for ; Tue, 19 May 2015 08:57:41 +0000 (UTC) Received: (qmail 88755 invoked by uid 500); 19 May 2015 08:57:37 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 88620 invoked by uid 500); 19 May 2015 08:57:37 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 88609 invoked by uid 99); 19 May 2015 08:57:36 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2015 08:57:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 521191A2F58 for ; Tue, 19 May 2015 08:57:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.13 X-Spam-Level: *** X-Spam-Status: No, score=3.13 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id HiG2WQOTX-JD for ; Tue, 19 May 2015 08:57:32 +0000 (UTC) Received: from mail-vn0-f51.google.com (mail-vn0-f51.google.com [209.85.216.51]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 4F63123151 for ; Tue, 19 May 2015 08:57:31 +0000 (UTC) Received: by vnbf129 with SMTP id f129so559903vnb.10 for ; Tue, 19 May 2015 01:56:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=AqgOQSQOt1ZxWgvq1VXnfc8LRwSrmhhYBG3Ge7+I2q4=; b=p2E0Npv20Jt1t6VaHssbaNW+yfJvUZHSA46xxLtOL9xfuFWGsdyKdbr0YZMdGh09K1 Gpql6/wasyTj4wi6o48wFJ4J5Zd1bssHWbZXRJai2RdJ2H3ozgawYtSbRuzrBiHCZ84u i+Hp9ePg2sSBccC/EdpX1K7KIgfeOJIdlO+HyQUivxF3FWliYpZHPiVPYYri71w3dhsu 1J+9FaCWa64/rHeybE3LNz7srMQPHcVuWaEDd0HejH+2oFFJ+JJCRIkszWJr0yEWsDK8 H/W7SB2NOxDsAfE9PpXqE8SxzcIdBciG4jlSSnp4jsM+6avxAfZ7q/vtpfAYrrXhB0Tr NhAw== MIME-Version: 1.0 X-Received: by 10.52.65.38 with SMTP id u6mr26525285vds.24.1432025798730; Tue, 19 May 2015 01:56:38 -0700 (PDT) Received: by 10.52.34.243 with HTTP; Tue, 19 May 2015 01:56:38 -0700 (PDT) Received: by 10.52.34.243 with HTTP; Tue, 19 May 2015 01:56:38 -0700 (PDT) In-Reply-To: References: Date: Tue, 19 May 2015 14:26:38 +0530 Message-ID: Subject: Re: how namenode decided which datanode are ready for a client From: rajesh damera To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11363e940aeb8105166b7dfa --001a11363e940aeb8105166b7dfa Content-Type: text/plain; charset=UTF-8 Namenode usually checks for the jobs running on the datanodes, of which tasktrackers keep a track of and decides if it still busy running a task. On May 19, 2015 14:23, "rajesh damera" wrote: > Datanode availability is monitored and decided by Namenode. You usually > get permissions, based on the type of user you are, to use a certain number > of nodes to run your jobs. These limitations are set by administrators at > user level > > Warm regards > Rajesh Damera > On May 19, 2015 14:08, "Himawan Mahardianto" > wrote: > >> Hi guys, I know that every datanode where sending heartbeat to prove that >> their alive but what method are used by namenode to decide which datanode >> are available to client if all datanode where available? >> >> Best Regards >> >> > --001a11363e940aeb8105166b7dfa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Namenode usually checks for the jobs running on the datanode= s, of which tasktrackers keep a track of and decides if it still busy runni= ng a task.

On May 19, 2015 14:23, "rajesh damera"= <d.rajesh15@gmail.com> w= rote:

Datanode availability is monitored and decided by Namenode. You usually ge= t permissions, based on the type of user you are, to use a certain number o= f nodes to run your jobs. These limitations are set by administrators at us= er level

Warm regards
Rajesh Damera

On May 19, 2015 14:08, "Himawan Mahardianto= " <mahar= dianto@ugm.ac.id> wrote:
Hi guys,=C2=A0I know that every datanode whe= re sending heartbeat to prove that their alive but=C2=A0what method are use= d by namenode to decide which datanode are available to client if all datan= ode where available?

Best Regards
=C2=A0
--001a11363e940aeb8105166b7dfa--