Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <422849617.1248389534807.JavaMail.jira@brutus>
Date: Thu, 23 Jul 2009 15:52:14 -0700 (PDT)
From: "Jim Kellerman (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-1691) Cannot connect to 0.20 HBase from an
 MR job running on a 0.19.0 version of Hadoop
In-Reply-To: <648694310.1248387615204.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734827#action_12734827 ] 

Jim Kellerman commented on HBASE-1691:
--------------------------------------

HBase 0.20 is supposed to run on Hadoop 0.20. Running it on 0.19 is not supported.

> Cannot connect to 0.20 HBase from an MR job running on a 0.19.0 version of Hadoop
> ---------------------------------------------------------------------------------
>
>                 Key: HBASE-1691
>                 URL: https://issues.apache.org/jira/browse/HBASE-1691
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.20.0
>            Reporter: Eric Tschetter
>         Attachments: hbase-1691-0.20.0.patch
>
>
> When running MR jobs on 0.19.0 Hadoop, the hadoop core libraries get loaded by the classloader before 0.20 libraries included in the job jar.  HBaseClient makes a call to org.apache.hadoop.net.NetUtils.connect on line 305 which does not exist in previous versions of the hadoop jars and therefore results in NoSuchMethodErrors getting thrown.
> As a simple workaround, you can replace the call
> NetUtils.connect(socket, remoteId.getAddress(), 20000);
> with
> socket.connect(remoteId.getAddress(), 20000);
> Note, however, that the javadoc on the NetUtils.connect() method makes mention of sun's implementation of stuff being less than wonderful, so the existence of this JIRA and this workaround should not be taken as meaning that this is actually a recommended solution.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.