You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[2024-05-23T14:52:01,565][INFO ][logstash.inputs.s3 ][main][..] object-in-bucket-xyz is updated at 2024-05-23 13:58:33 UTC and will process in the next cycle
Which means the file is not deleted. In the next cycle, the timestamps still don't match so it again is not deleted.
When changing the log output to include both timestamps here the issue becomes clear:
object.last_modified: 2024-05-23 13:33:33.000000000 Z
log.last_modified: 2024-05-23 13:33:33.898000000 Z
An easy fix would be to change line 380 to:
if object.last_modified.floor == log.last_modified.floor
I have not tested this against S3, but i assume they give the timestamp in miliseconds while ceph-rgw does not. I totally understand it if you don't want to fix it, in that case i'll just leave this information here as a workaround for anyone having the same problem.
The text was updated successfully, but these errors were encountered:
I am aware that I am using an S3-compatible solution and this is not supported. However, this is an easy fix.
Logstash information:
Please include the following information:
Description of the problem including expected versus actual behavior:
When running the S3 input-plugin, files are not deleted or backed up when using Ceph-RGW as S3 storage
Steps to reproduce:
Provide logs (if relevant):
This gives the following output:
Which means the file is not deleted. In the next cycle, the timestamps still don't match so it again is not deleted.
When changing the log output to include both timestamps here the issue becomes clear:
An easy fix would be to change line 380 to:
I have not tested this against S3, but i assume they give the timestamp in miliseconds while ceph-rgw does not. I totally understand it if you don't want to fix it, in that case i'll just leave this information here as a workaround for anyone having the same problem.
The text was updated successfully, but these errors were encountered: