Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 425C49500 for ; Fri, 16 Dec 2011 21:35:05 +0000 (UTC) Received: (qmail 22113 invoked by uid 500); 16 Dec 2011 21:35:04 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 22065 invoked by uid 500); 16 Dec 2011 21:35:04 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 21920 invoked by uid 99); 16 Dec 2011 21:35:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Dec 2011 21:35:04 +0000 X-ASF-Spam-Status: No, hits=-2001.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Dec 2011 21:34:54 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 6D49411724D for ; Fri, 16 Dec 2011 21:34:32 +0000 (UTC) Date: Fri, 16 Dec 2011 21:34:32 +0000 (UTC) From: "Suresh Srinivas (Updated) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <27984002.20771.1324071272448.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <231197017.18798.1324026510904.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (HDFS-2694) Removal of Avro broke non-PB NN services MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-2694: ---------------------------------- Attachment: HDFS-2694.txt Aaron, this patch should fix it without any need for change in common. > Removal of Avro broke non-PB NN services > ---------------------------------------- > > Key: HDFS-2694 > URL: https://issues.apache.org/jira/browse/HDFS-2694 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node > Affects Versions: 0.24.0 > Reporter: Aaron T. Myers > Assignee: Aaron T. Myers > Attachments: HDFS-2694.patch, HDFS-2694.txt > > > RpcEngine implementations have to register themselves associated with an RpcKind. Both WritableRpcEngine and ProtobufRpcEngine do this registration in static initialization blocks. It used to be that the static initializer block for WritableRpcEngine was triggered when AvroRpcEngine was initialized, since this instantiated a WritableRpcEngine object. With AvroRpcEngine gone, there's nothing in the NN to trigger the WritableRpcEngine static initialization block. Therefore, those RPC services which still use Writable and not PB no longer work. > For example, if I try to run `hdfs groups' on trunk, which uses the GetUserMappingsProtocol, this error gets spit out: > {noformat} > $ hdfs groups > log4j:ERROR Could not find value for key log4j.appender.NullAppender > log4j:ERROR Could not instantiate appender named "NullAppender". > Exception in thread "main" java.io.IOException: Unknown rpc kind RPC_WRITABLE > at org.apache.hadoop.ipc.Client.call(Client.java:1136) > at org.apache.hadoop.ipc.WritableRpcEngine$Invoker.invoke(WritableRpcEngine.java:205) > at $Proxy6.getGroupsForUser(Unknown Source) > at org.apache.hadoop.tools.GetGroupsBase.run(GetGroupsBase.java:71) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:69) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:83) > at org.apache.hadoop.hdfs.tools.GetGroups.main(GetGroups.java:56) > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira