Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent event duplication when archiving to bucket #244

Closed
reisingerf opened this issue Apr 23, 2024 · 2 comments · Fixed by #247
Closed

Prevent event duplication when archiving to bucket #244

reisingerf opened this issue Apr 23, 2024 · 2 comments · Fixed by #247
Assignees
Labels

Comments

@reisingerf
Copy link
Member

See:
s3://event-archive-bucket/events/year=2024/month=04/day=23/Event_from_aws_sqs_1713843860.201574.json
s3://event-archive-bucket/events/year=2024/month=04/day=23/Event_from_aws_sqs_1713843918.998975.json
s3://event-archive-bucket/events/year=2024/month=04/day=23/Event_from_aws_sqs_1713844049.748956.json

All have the same JSON payload including ICA correlationId and timestamp.
Probably due to the same event being handled multiple times.

We need to investigate where that duplication happens, ICA side or EventBus, and how to best avoid it (or if need be collapse the events).

@raylrui
Copy link
Contributor

raylrui commented Apr 23, 2024

From the events timestamp 1713843860.201574 1713843918.998975 1713844049.748956, these events are different events, or at least trigger the lambda at different time, I will have a check of archiver logic now

@raylrui
Copy link
Contributor

raylrui commented Apr 23, 2024

It may come from error in logger.info , please refer PR #247

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants