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
In hummock, automatically triggered compaction and manual compaction are supported to meet the needs of most scenarios.
However, each time manual compaction is initiated, only one compact task is triggered, which cannot meet the needs of full compaction.
In what scenarios does Full Compaction need to be introduced?
When there is a large amount of redundant data in hummock, it needs to be cleaned.
When a table_id contains a large number of stale keys, it needs to be cleaned immediately to improve query performance.
When testing, it is necessary to verify whether the newly introduced compaction cleaning logic can work.
When under low load, we can trigger full compaction to reorganize the data in hummock.
feat request:
trigger full compaction at table granularity via SQL request by @chenzl25
trigger full compaction to verify the table-watermark cleaning capabilities request by @wenym1
The text was updated successfully, but these errors were encountered:
In hummock, automatically triggered compaction and manual compaction are supported to meet the needs of most scenarios.
However, each time manual compaction is initiated, only one compact task is triggered, which cannot meet the needs of full compaction.
In what scenarios does Full Compaction need to be introduced?
feat request:
The text was updated successfully, but these errors were encountered: