Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 7350818BA0 for ; Fri, 19 Jun 2015 23:25:59 +0000 (UTC) Received: (qmail 31896 invoked by uid 500); 19 Jun 2015 23:25:54 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 31786 invoked by uid 500); 19 Jun 2015 23:25:54 -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 31776 invoked by uid 99); 19 Jun 2015 23:25:54 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jun 2015 23:25:54 +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 CA36A1A5DBB for ; Fri, 19 Jun 2015 23:25:53 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.73 X-Spam-Level: * X-Spam-Status: No, score=1.73 tagged_above=-999 required=6.31 tests=[KAM_INFOUSMEBIZ=0.75, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Received: from mx1-us-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 lqvSPDUsJWEp for ; Fri, 19 Jun 2015 23:25:53 +0000 (UTC) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id CFC9C249EA for ; Fri, 19 Jun 2015 23:25:52 +0000 (UTC) Received: by wicgi11 with SMTP id gi11so30785276wic.0 for ; Fri, 19 Jun 2015 16:25:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=OtqeGIdgrtHFdvhnEsURKCh175O62piDAtCmvMUEK0I=; b=ENztg71F+erjO8nHlIjjUyfhEalMHWSKAHCezyJEvPozSZ6PrP8GXxhLl+okEvjufO kuAbCNtoe6BY5a6y6LLZCBYCxmqxywUm/i77k9wVNU3k9JX6XlGEPZ6t7OduMfuy4bmU 4sf7LIUbQBl005XH/c2KilPh7LvPWd3XRcdbN8NIKuI77e57mAmpeo6+1C6fhH4k3cqf MWhdglCClg4AJvK++ZWGCwjIjQW6wn4Oj8oAOoYR277K7f84eQMqKnCWFgoaYKgueK/D YUZhxEYZKezbAnfLz/naUO5mZdh48mv/uMR5VxxEPuS/UBt4VFZURATnYDK88m2Q+JoC UhKg== X-Gm-Message-State: ALoCoQkDLqYB2cbR4YSxuUD07btcqFQOgtdO+Vj+kS8iK3KXJknn+64Fxl5fiZGWPPZijefigwj4 MIME-Version: 1.0 X-Received: by 10.180.75.78 with SMTP id a14mr10824117wiw.43.1434756351628; Fri, 19 Jun 2015 16:25:51 -0700 (PDT) Received: by 10.27.11.199 with HTTP; Fri, 19 Jun 2015 16:25:51 -0700 (PDT) X-Originating-IP: [67.71.177.104] Date: Fri, 19 Jun 2015 19:25:51 -0400 Message-ID: Subject: How to monitor what hdfs block is served to a client? From: Shiyao Ma To: user@hadoop.apache.org Content-Type: text/plain; charset=UTF-8 Hi. How to monitor the block transmission log of datanodes? A more detailed example: My hdfs block size is 128MB. I have a file stored on hdfs with size 167.08MB. Also, I have a client, requesting the whole file with three splits, e.g., hdfs://myserver:9000/myfile:0+58397994 (0-56MB) hdfs://myserver:9000/myfile:58397994+58397994 (56MB-112MB) hdfs://myserver:9000/myfile:116795988+58397994 (112MB-168MB) The situation is kinda fixed and I cannot modify the split size. Nevertheless, I'd like to know what block tranmission is happening under the earth.