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
But GcAllType won't, it'll use a small time (ttl value, not the expire time, e.g. ttl=1m, time value will be 1970-01-01) to do gc. Normally, no row will be gc cuz row ts > small time, so the data never expire, you can check by show table status.
The text was updated successfully, but these errors were encountered:
OpenMLDB/src/storage/segment.cc
Lines 437 to 458 in 21184d5
ref https://utqcxc5xn1.feishu.cn/docx/FTbtdV25eoZDkjxODpCc44qhnlc , if we have a table with indexes in same keys but different ts, e.g.
index0 and index1 will in the same segment and
ts_cnt_==2
, so segment gc will triggerGcAllType
, it'll use the wrong expire time.when
ts_cnt_<=1
,ExecuteGc
will calc expire time:OpenMLDB/src/storage/segment.cc
Lines 398 to 408 in 21184d5
But
GcAllType
won't, it'll use a small time (ttl value, not the expire time, e.g. ttl=1m, time value will be 1970-01-01) to do gc. Normally, no row will be gc cuz row ts > small time, so the data never expire, you can check byshow table status
.The text was updated successfully, but these errors were encountered: