[
https://issues.apache.org/jira/browse/HADOOP-18706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714672#comment-17714672
]
ASF GitHub Bot commented on HADOOP-18706:
-----------------------------------------
cbevard1 commented on PR #5563:
URL: https://github.com/apache/hadoop/pull/5563#issuecomment-1516625886
Nevermind. I was running verify from a new terminal window where JAVA_HOME
was set to version 18. That was causing issues with the com.google.inject:guice
dependency in hadoop-yarn-server-resourcemanager. It looks like that version of
java was also messing up the maven-surefire-plugin because the
`ITestTerasortOnS3A` test wasn't being skipped when it should have been.
Anyways, rolling back the version of java fixed the issue. I ran the scale
tests too this time so `ITestTerasortOnS3A` wasn't skipped and I could make
sure it succeeded. All unit and integration tests are passing.
> The temporary files for disk-block buffer aren't unique enough to recover
> partial uploads.
> -------------------------------------------------------------------------------------------
>
> Key: HADOOP-18706
> URL: https://issues.apache.org/jira/browse/HADOOP-18706
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Reporter: Chris Bevard
> Priority: Minor
> Labels: pull-request-available
>
> If an application crashes during an S3ABlockOutputStream upload, it's
> possible to complete the upload if fast.upload.buffer is set to disk by
> uploading the s3ablock file with putObject as the final part of the multipart
> upload. If the application has multiple uploads running in parallel though
> and they're on the same part number when the application fails, then there is
> no way to determine which file belongs to which object, and recovery of
> either upload is impossible.
> If the temporary file name for disk buffering included the s3 key, then every
> partial upload would be recoverable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
