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
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.
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: