Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9D5D0200C2C for ; Fri, 17 Feb 2017 02:50:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 9C026160B6F; Fri, 17 Feb 2017 01:50:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E6E45160B61 for ; Fri, 17 Feb 2017 02:50:44 +0100 (CET) Received: (qmail 29976 invoked by uid 500); 17 Feb 2017 01:50:43 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 29965 invoked by uid 99); 17 Feb 2017 01:50:43 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Feb 2017 01:50:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 7553BC14BE for ; Fri, 17 Feb 2017 01:50:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ibYLsFjUf_RP for ; Fri, 17 Feb 2017 01:50:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id AA9D55F613 for ; Fri, 17 Feb 2017 01:50:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E7566E0223 for ; Fri, 17 Feb 2017 01:50:41 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A4D4F2411B for ; Fri, 17 Feb 2017 01:50:41 +0000 (UTC) Date: Fri, 17 Feb 2017 01:50:41 +0000 (UTC) From: "Weiwei Yang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-11401) Reduce verbosity of logs with favored nodes and block pinning enabled MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 17 Feb 2017 01:50:45 -0000 [ https://issues.apache.org/jira/browse/HDFS-11401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871037#comment-15871037 ] Weiwei Yang commented on HDFS-11401: ------------------------------------ Hi [~rakeshr] Thanks for your comments, it makes sense to me. I just uploaded the patch with the change you suggested, thank you! > Reduce verbosity of logs with favored nodes and block pinning enabled > --------------------------------------------------------------------- > > Key: HDFS-11401 > URL: https://issues.apache.org/jira/browse/HDFS-11401 > Project: Hadoop HDFS > Issue Type: Improvement > Components: balancer & mover, datanode > Affects Versions: 2.8.0 > Reporter: Thiruvel Thirumoolan > Assignee: Weiwei Yang > Priority: Minor > Attachments: HDFS-11401.01.patch, HDFS-11401.02.patch, HDFS-11401.03.patch, testBalancerWithPinnedBlocks.output.txt > > > I am working on enabling favored nodes for HBase (HBASE-15531). Was trying out what happens if favored nodes is used and HDFS balancer is enabled. Ran the unit test TestBalancer#testBalancerWithPinnedBlocks from branch-2.8. There were too many exceptions and error messages with this (output attached) since pinned blocks can't be moved. > Is there any way to reduce this logging since block pinning is intentional? On a real cluster, this could be too much. HDFS-6133 enabled block pinning. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org