hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiang Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17878) java.lang.NoSuchMethodError: org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter when starting HBase with hbase.rootdir on S3
Date Wed, 12 Apr 2017 14:47:41 GMT

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

Xiang Li commented on HBASE-17878:
----------------------------------

1. The joda-time can not be excluded, or there will be some test failures in hbase-shell,
as Zach mentioned.

2. If joda-time is not excluded, I found another error (when running UT TestShell),
{code}
testRunShellTests(org.apache.hadoop.hbase.client.TestShell)  Time elapsed: 0.119 sec  <<<
ERROR!
org.jruby.embed.EvalFailedException: (LoadError) no such file to load -- rubygems
	at org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:136)
	at org.jruby.embed.ScriptingContainer.runUnit(ScriptingContainer.java:1263)
	at org.jruby.embed.ScriptingContainer.runScriptlet(ScriptingContainer.java:1308)
	at org.apache.hadoop.hbase.client.TestShell.testRunShellTests(TestShell.java:36)
Caused by: org.jruby.exceptions.RaiseException: (LoadError) no such file to load -- rubygems
	at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1062)
	at (Anonymous).(root)(src/test/ruby/tests_runner.rb:20)


Results :

Tests in error:
  TestShell.testRunShellTests:36 ยป EvalFailed (LoadError) no such file to load -...
{code}
My basic idea is to use jruby-core instead of jruby-complete, because jruby-complete is an
all-in-one package, one jar to contains all, while by using jruby-core, exclusion(joda-time
or others) can be performed. But it appears jruby-complete contains more, other than jruby-core
and the dependencies of jruby-core, at least it contains rubygems.


> 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)

Mime
View raw message