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

Tombstone Events Discussion #3398

Open
ericgreenmix opened this issue Sep 5, 2024 · 0 comments
Open

Tombstone Events Discussion #3398

ericgreenmix opened this issue Sep 5, 2024 · 0 comments

Comments

@ericgreenmix
Copy link
Contributor

After moving an event store to be partitioned, the prevalence of tombstone events is much more apparent in the default partition, since tombstone events don't get archived. The purpose of partitioning the event store is to help the scaling/speed in larger stores. Having the tombstone events stick around in the active partition, after they have already served their purpose for the high water mark detection, doesn't seem optimal.

Questions for discussion:

  • Does archiving tombstone events provide more value than removing them entirely? I can't see much value in keeping archived tombstone events around, unless I am missing something about them.
  • At what point could this process happen to the tombstone events? It clearly has to be after the High Water Mark Detection has happened and used it.
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

No branches or pull requests

1 participant