[
https://issues.apache.org/jira/browse/HBASE-20582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479101#comment-16479101
]
Josh Elser commented on HBASE-20582:
------------------------------------
Test failure was
{noformat}
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 69.215
s <<< FAILURE! - in
org.apache.hadoop.hbase.replication.TestReplicationKillMasterRSWithSeparateOldWALs
[ERROR]
killOneMasterRS(org.apache.hadoop.hbase.replication.TestReplicationKillMasterRSWithSeparateOldWALs)
Time elapsed: 66.462 s <<< ERROR!
org.apache.hadoop.hbase.client.RetriesExhaustedException:
Failed after attempts=16, exceptions:
Wed May 16 19:07:48 UTC 2018, null, java.net.SocketTimeoutException:
callTimeout=60000, callDuration=61018: Call to bcdc9c6c7e68/172.17.0.2:38822
failed on local exception: org.apache.hadoop.hbase.ipc.CallTimeoutException:
Call id=79, waitTime=58812, rpcTimeout=58800 row 'ccc' on table 'test' at
region=test,ccc,1526497597339.d09793b3665a04d8bc5dda08f0e15de3.,
hostname=bcdc9c6c7e68,38822,1526497586868, seqNum=2
at
org.apache.hadoop.hbase.replication.TestReplicationKillMasterRSWithSeparateOldWALs.killOneMasterRS(TestReplicationKillMasterRSWithSeparateOldWALs.java:45)
Caused by: java.net.SocketTimeoutException: callTimeout=60000,
callDuration=61018: Call to bcdc9c6c7e68/172.17.0.2:38822 failed on local
exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=79,
waitTime=58812, rpcTimeout=58800 row 'ccc' on table 'test' at
region=test,ccc,1526497597339.d09793b3665a04d8bc5dda08f0e15de3.,
hostname=bcdc9c6c7e68,38822,1526497586868, seqNum=2
Caused by: java.io.IOException: Call to bcdc9c6c7e68/172.17.0.2:38822 failed on
local exception: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=79,
waitTime=58812, rpcTimeout=58800
Caused by: org.apache.hadoop.hbase.ipc.CallTimeoutException: Call id=79,
waitTime=58812, rpcTimeout=58800{noformat}
Re-running this locally, but I suspect this to be unrelated to this change.
Folks happy with this for 2.1? ([~busbey] I think you had the strongest
opinions)
> Bump up JRuby version because of some reported vulnerabilities
> --------------------------------------------------------------
>
> Key: HBASE-20582
> URL: https://issues.apache.org/jira/browse/HBASE-20582
> Project: HBase
> Issue Type: Bug
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Priority: Major
> Fix For: 2.1.0
>
> Attachments: HBASE-20582.002.patch, HBASE-20582.patch
>
>
> There are some vulnerabilities reported with two of the libraries used in
> HBase.
> {code:java}
> Jruby(version:9.1.10.0):
> CVE-2009-5147
> CVE-2013-4363
> CVE-2014-4975
> CVE-2014-8080
> CVE-2014-8090
> CVE-2015-3900
> CVE-2015-7551
> CVE-2015-9096
> CVE-2017-0899
> CVE-2017-0900
> CVE-2017-0901
> CVE-2017-0902
> CVE-2017-0903
> CVE-2017-10784
> CVE-2017-14064
> CVE-2017-9224
> CVE-2017-9225
> CVE-2017-9226
> CVE-2017-9227
> CVE-2017-9228
> {code}
> Tool somehow able to relate the vulnerability of Ruby with JRuby(Java
> implementation). (Jackson will be handled in a different issue.)
> Not all of them directly affects HBase but [~elserj] suggested that it is
> better to be on the updated version to avoid issues during an audit in
> security sensitive organization.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
