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

Hinder Events from duplicating events when storing them to the database #307

Closed
1 task
Tracked by #570
acn-sbuad opened this issue Mar 14, 2023 · 3 comments
Closed
1 task
Tracked by #570
Labels
kind/user-story Used for issues that describes functionality for our users. status/blocked pending the completion of some other task/PoC/issue status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@acn-sbuad
Copy link
Contributor

acn-sbuad commented Mar 14, 2023

Description

Erorrhandling of inbound events can result in an event being persisted multiple times in the database.

Additional Information

No response

Tasks

  • Investigate logs and see if we can find the point of failiure

Acceptance Criterias

No response

@acn-sbuad acn-sbuad added kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Mar 14, 2023
@SandGrainOne SandGrainOne changed the title Filter duplicate events before returning events from GET request Hinder Events from duplicating events when storing them to the database Mar 21, 2023
@SandGrainOne
Copy link
Member

SandGrainOne commented Mar 21, 2023

Refinement 21.03.2023:
Primarily an analysis issue where we try to find the cause of the duplication. A simple fix can be implemented, but a larger issue should be posponed. The idea is to replace Azure Storage Queue with Kafka.

@olebhansen
Copy link

Pending implementation of #573 and subsequent observations to determine if additional work is needed.

@olebhansen olebhansen added the status/blocked pending the completion of some other task/PoC/issue label Aug 12, 2024
@olebhansen
Copy link

Closing - resolving this in #588

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story Used for issues that describes functionality for our users. status/blocked pending the completion of some other task/PoC/issue status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
None yet
Development

No branches or pull requests

3 participants