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
However, given that may_fill_backward_compatible_state_table_info_delta happens after the initialization and the replay of the existing hummock version delta. The stale table watermark cleanup triggered by replaying old version deltas will be skipped and cause panic in
Describe the bug
We introduced a new field
StateTableInfo
in HummockVersion in #15896 and implemented a logic to init this new field viarisingwave/src/storage/hummock_sdk/src/version.rs
Line 324 in cc44276
and we leverage this new field to clean up stale hummock table watermark in
risingwave/src/storage/hummock_sdk/src/compaction_group/hummock_version_ext.rs
Line 649 in cc44276
However, given that
may_fill_backward_compatible_state_table_info_delta
happens after the initialization and the replay of the existing hummock version delta. The stale table watermark cleanup triggered by replaying old version deltas will be skipped and cause panic inrisingwave/src/storage/hummock_sdk/src/compaction_group/hummock_version_ext.rs
Line 218 in cc44276
Error message/log
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: