[
https://issues.apache.org/jira/browse/HADOOP-15735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-15735:
------------------------------------
Resolution: Fixed
Fix Version/s: 2.7.8
Status: Resolved (was: Patch Available)
thanks for doing this, especially the testing. Fix will be in 2.7.8
Note that spark rolled back from 2.7.7 to 2.7.6 because part of a security
lockdown broke things...that will need to be addressed in the same release
before they can move up
> backport HADOOP-11687 for hadoop-aws 2.7.x
> ------------------------------------------
>
> Key: HADOOP-15735
> URL: https://issues.apache.org/jira/browse/HADOOP-15735
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 2.7.7
> Reporter: MunShik JOUNG
> Assignee: MunShik JOUNG
> Priority: Trivial
> Fix For: 2.7.8
>
> Attachments:
> 0001-HADOOP-12970-Intermitent-SignatureDoesNotMatch-Excep.patch
>
>
> HADOOP-12970 Intermitent SignatureDoesNotMatch Exception is fixed by
> HADOOP-11687.
> And from hadoop-aws >= 2.8, HADOOP-11687 is applied. but Spark 2.3.1 is still
> using hadoop-aws 2.7.7.
> I was stumpled upon Intermitent SignatureDoesNotMatch Exception with s3 with
> spark 2.3.1. So I guess backporting might benefit some spark users. In my
> situation, SignatureDoesNotMatch was reliably reproducible (4 out of 8
> attemp). And after using patched version symptom was not seen (0 out of 10)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
