From hdfs-issues-return-257590-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Mar 22 21:27:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id EE09618064D for ; Fri, 22 Mar 2019 22:27:01 +0100 (CET) Received: (qmail 15996 invoked by uid 500); 22 Mar 2019 21:27:01 -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 15983 invoked by uid 99); 22 Mar 2019 21:27:00 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Mar 2019 21:27:00 +0000 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 746F8E07DC for ; Fri, 22 Mar 2019 21:27:00 +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 329852459A for ; Fri, 22 Mar 2019 21:27:00 +0000 (UTC) Date: Fri, 22 Mar 2019 21:27:00 +0000 (UTC) From: "Sergey Shelukhin (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HDFS-14387) create a client-side override for dfs.namenode.block-placement-policy.default.prefer-local-node MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sergey Shelukhin created HDFS-14387: --------------------------------------- Summary: create a client-side override for dfs.namenode.block-placement-policy.default.prefer-local-node Key: HDFS-14387 URL: https://issues.apache.org/jira/browse/HDFS-14387 Project: Hadoop HDFS Issue Type: Bug Reporter: Sergey Shelukhin It should be possible for a service to decide whether it wants to use the local node preference; as it stands, if dfs.namenode.block-placement-policy.default.prefer-local-node is enabled, the services that run far fewer instances than there are DNs in the cluster unnecessarily concentrate their write load; the only way around it seems to be to disable prefer-local-node globally. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org