[GH-ISSUE #390] S3 bucket that creates Lambda events generates 2 #206

New issue

Closed

opened 2026-03-04 01:43:14 +03:00 by kerem · 5 comments

kerem commented

2026-03-04 01:43:14 +03:00

Owner

Originally created by @graysoncash on GitHub (Apr 8, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/390

When I drop a file into my S3 bucket through an s3fs mount and events for my Lambda function get generated, there's always 2 identical ones that are created. Otherwise, uploading the file through the S3 gui just creates 1 event.

Setup isn't anything different from the instructions.

Originally created by @graysoncash on GitHub (Apr 8, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/390 When I drop a file into my S3 bucket through an s3fs mount and events for my Lambda function get generated, there's always 2 identical ones that are created. Otherwise, uploading the file through the S3 gui just creates 1 event. Setup isn't anything different from the instructions.

kerem closed this issue

2026-03-04 01:43:15 +03:00

kerem commented

2026-03-04 01:43:16 +03:00

Author

Owner

@ggtakec commented on GitHub (Apr 10, 2016):

@cashgl
When s3fs makes(updalods) the file(object) to S3, first s3fs makes zero file on S3 and second uploads it.
Thus it is probably the two events will generate.
This behavior is due to FUSE.
FUSE always creates a zero file or sets the file size to zero just before FUSE copies the file.
s3fs more than a FUSE-based, which can not be avoided.

Regards,

@ggtakec commented on GitHub (Apr 10, 2016): @cashgl When s3fs makes(updalods) the file(object) to S3, first s3fs makes zero file on S3 and second uploads it. Thus it is probably the two events will generate. This behavior is due to FUSE. FUSE always creates a zero file or sets the file size to zero just before FUSE copies the file. s3fs more than a FUSE-based, which can not be avoided. Regards,

kerem commented

2026-03-04 01:43:16 +03:00

Author

Owner

@ingageco commented on GitHub (Aug 25, 2016):

@ggtakec - So can we assume that when the second event fires, the upload is 100% complete?

@ingageco commented on GitHub (Aug 25, 2016): @ggtakec - So can we assume that when the second event fires, the upload is 100% complete?

kerem commented

2026-03-04 01:43:16 +03:00

Author

Owner

@ingageco commented on GitHub (Aug 25, 2016):

I'm dealing with large video files, so that's the context of my question.

@ingageco commented on GitHub (Aug 25, 2016): I'm dealing with large video files, so that's the context of my question.

kerem commented

2026-03-04 01:43:16 +03:00

Author

Owner

@ggtakec commented on GitHub (Sep 19, 2016):

@ingageco
The first event(HTTP PUT) is for creating a file as 0 size.
The second's PUT event means that s3fs starts to upload the file contents, it does not finish to upload.probablyprobablyprobably
Probably, your application(ex. cp command) will be waited to finish to upload all of file constents.

Regards,

@ggtakec commented on GitHub (Sep 19, 2016): @ingageco The first event(HTTP PUT) is for creating a file as 0 size. The second's PUT event means that s3fs starts to upload the file contents, it does not finish to upload.probablyprobablyprobably Probably, your application(ex. cp command) will be waited to finish to upload all of file constents. Regards,

kerem commented

2026-03-04 01:43:16 +03:00

Author

Owner

@ingageco commented on GitHub (Sep 20, 2016):

@ggtakec Thank you for clarifying!

@ingageco commented on GitHub (Sep 20, 2016): @ggtakec Thank you for clarifying!