[
https://issues.apache.org/jira/browse/HADOOP-15735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16609120#comment-16609120
]
Hadoop QA commented on HADOOP-15735:
------------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s{color}
| {color:red} HADOOP-15735 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-15735 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12939007/0001-HADOOP-12970-Intermitent-SignatureDoesNotMatch-Excep.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/15168/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> 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
> Priority: Trivial
> 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: [email protected]
For additional commands, e-mail: [email protected]