From hdfs-issues-return-250781-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Feb 8 23:54:05 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 00D1318060E for ; Sat, 9 Feb 2019 00:54:04 +0100 (CET) Received: (qmail 30055 invoked by uid 500); 8 Feb 2019 23:54:04 -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 30044 invoked by uid 99); 8 Feb 2019 23:54:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2019 23:54:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id A74D6C0467 for ; Fri, 8 Feb 2019 23:54:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Cpw7fCyXvQg9 for ; Fri, 8 Feb 2019 23:54:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id BA759623E2 for ; Fri, 8 Feb 2019 23:54:01 +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 AEDD6E274A for ; Fri, 8 Feb 2019 23:54: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 2DB3F24452 for ; Fri, 8 Feb 2019 23:54:00 +0000 (UTC) Date: Fri, 8 Feb 2019 23:54:00 +0000 (UTC) From: "Erik Krogen (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-14162) Balancer should work with ObserverNode MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763971#comment-16763971 ] Erik Krogen commented on HDFS-14162: ------------------------------------ I had some discussion offline with [~shv] and he pointed me towards {{ProtocolProxy}}, which appears to maintain some mapping of the methods implemented by the proxy. After looking into this further, I realized that it is actually keeping track of which methods are implemented by the _server_, rather than the proxy on the client. Actually, its methods won't even work on HDFS proxies, because HDFS protocol interfaces do not implement {{VersionedProtocol}}, and {{ProtocolProxy}} does a cast to {{VersionedProtocol}} to fetch the server-side information. However this pointer inspired me to make some modifications, relying more on reflection, to greatly simplify the {{CombinedProxyBuilder}} (renamed to {{ProxyCombiner}}). [~shv], let me know your thoughts on v001. > Balancer should work with ObserverNode > -------------------------------------- > > Key: HDFS-14162 > URL: https://issues.apache.org/jira/browse/HDFS-14162 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Konstantin Shvachko > Assignee: Erik Krogen > Priority: Major > Attachments: HDFS-14162-HDFS-12943.wip0.patch, HDFS-14162.000.patch, HDFS-14162.001.patch, testBalancerWithObserver-3.patch, testBalancerWithObserver.patch > > > Balancer provides a substantial RPC load on NameNode. It would be good to divert Balancer RPCs {{getBlocks()}}, etc. to ObserverNode. The main problem is that Balancer uses {{NamenodeProtocol}}, while ORPP currently supports only {{ClientProtocol}}. -- 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