Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 3 May 2017 03:21:05 +0000 (UTC)
From: "Xiang Li (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13061638.1491375151000.111038.1493781665317@Atlassian.JIRA>
In-Reply-To: <JIRA.13061638.1491375151000@Atlassian.JIRA>
References: <JIRA.13061638.1491375151000@Atlassian.JIRA> <JIRA.13061638.1491375151320@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (HBASE-17878) java.lang.NoSuchMethodError:
 org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter
 when starting HBase with hbase.rootdir on S3
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 03 May 2017 03:21:12 -0000


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

Xiang Li edited comment on HBASE-17878 at 5/3/17 3:20 AM:
----------------------------------------------------------

We are using HBase 1.2.x with Hadoop 2.7.x.
HBase uses jruby-complete 1.6.8 as its dependency, which somehow packages a lot of joda-time classes(version is 1.6) directly. While hadopp-aws module uses aws-java-sdk-s3 as its dependency and aws-java-sdk-s3 introduces joda-time.

When runtime, in HBase classpath, jruby-complete in hbase lib stays in front of hadoop-mapreduce dir, but it appears that jruby-complete packages a lower version of joda-time than needed, and withZoneUTC() is not provided.

I checked branch-1 of HBase, and it is using Hadoop 2.5.1(lower than 2.7.x we are using). I am checking if branch-1 has the same issue and will contribute a patch after it is confirmed.


was (Author: water):
We are using HBase 1.2.x with Hadoop 2.7.x.
HBase uses jruby-complete 1.6.8 as its dependency, which somehow packages a lot of joda-time classes directly. While hadopp-aws module uses aws-java-sdk-s3 as its dependency and aws-java-sdk-s3 introduces joda-time.

When runtime, in HBase classpath, jruby-complete in hbase lib stays in front of hadoop-mapreduce dir, but it appears that jruby-complete packages a lower version of joda-time than needed, and withZoneUTC() is not provided.

I checked branch-1 of HBase, and it is using Hadoop 2.5.1(lower than 2.7.x we are using). I am checking if branch-1 has the same issue and will contribute a patch after it is confirmed.


> java.lang.NoSuchMethodError: org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter when starting HBase with hbase.rootdir on S3
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17878
>                 URL: https://issues.apache.org/jira/browse/HBASE-17878
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: Xiang Li
>            Assignee: Xiang Li
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-17878.master.000.patch, jruby-core-dep-tree.txt
>
>
> When setting up HBASE-17437 (Support specifying a WAL directory outside of the root directory), we specify
> (1) hbase.rootdir on s3a
> (2) hbase.wal.dir on HDFS
> When starting HBase, the following exception is thrown:
> {code}
> Caused by: java.lang.NoSuchMethodError: org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter;
>         at com.amazonaws.auth.internal.AWS4SignerUtils.<clinit>(AWS4SignerUtils.java:26)
>         at com.amazonaws.auth.internal.AWS4SignerRequestParams.<init>(AWS4SignerRequestParams.java:85)
>         at com.amazonaws.auth.AWS4Signer.sign(AWS4Signer.java:184)
>         at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:709)
>         at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:489)
>         at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:310)
>         at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3785)
>         at com.amazonaws.services.s3.AmazonS3Client.headBucket(AmazonS3Client.java:1107)
>         at com.amazonaws.services.s3.AmazonS3Client.doesBucketExist(AmazonS3Client.java:1070)
>         at org.apache.hadoop.fs.s3a.S3AFileSystem.initialize(S3AFileSystem.java:232)
>         at org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2669)
>         at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:94)
>         at org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2703)
>         at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2685)
>         at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:373)
>         at org.apache.hadoop.fs.Path.getFileSystem(Path.java:295)
>         at org.apache.hadoop.hbase.util.FSUtils.getRootDir(FSUtils.java:1007)
>         at org.apache.hadoop.hbase.util.FSUtils.isValidWALRootDir(FSUtils.java:1050)
>         at org.apache.hadoop.hbase.util.FSUtils.getWALRootDir(FSUtils.java:1032)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.initializeFileSystem(HRegionServer.java:627)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.<init>(HRegionServer.java:570)
>         at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:393)
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>         at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>         at org.apache.hadoop.hbase.master.HMaster.constructMaster(HMaster.java:2456)
>         ... 5 more
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)