Skip to content

S3 multipart: Do not store completed parts in state#2326

Merged
goto-bus-stop merged 2 commits into
transloadit:masterfrom
yaegor:patch-2
Jun 22, 2020
Merged

S3 multipart: Do not store completed parts in state#2326
goto-bus-stop merged 2 commits into
transloadit:masterfrom
yaegor:patch-2

Conversation

@yaegor
Copy link
Copy Markdown
Contributor

@yaegor yaegor commented Jun 17, 2020

Do not store completed parts in state as they can be retrieved from S3 and do not need to be stored locally (this also fixes #2324)

closes #2325

…3 and do not need to be stored locally (alternative fix to transloadit#2324)
@yaegor
Copy link
Copy Markdown
Contributor Author

yaegor commented Jun 17, 2020

From what I see, storing the parts in the state is not necessary, as when the upload is restarted, the plugin queries already uploaded parts via S3 API and fills the actual parts (see MultipartUploader._resumeUpload).

This might be a better fix for #2324 (than #2325 which I originally submitted) as it eliminates the duplicating structures all together.

Copy link
Copy Markdown
Contributor

@goto-bus-stop goto-bus-stop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, I think you're right!

@goto-bus-stop goto-bus-stop merged commit 988a7ed into transloadit:master Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

S3 Multipart: Second retry after offline mode breaks file upload (parts duplicate)

2 participants