Skip to content

Support triggering compaction on a timely basis #8086

@MichaelScofield

Description

@MichaelScofield

What problem does the new feature solve?

When the region is being edited too quick, the compaction could fail:

{"timestamp":"2026-05-08T10:00:53.661486Z","level":"ERROR","fields":{"message":"Region 9491877724160(2210, 0) failed to compact, cancel all pending tasks","err":"0: Region 9491877724160(2210, 0) is in Leader(Editing) state, which does not permit manifest updates., at greptimedb/src/mito2/src/[region.rs:1000](http://region.rs:1000/):13"},"target":"mito2::compaction"}

What does the feature do?

Better if the compaction can be triggered as configured at business off-peak period. Besides, compaction costs cpu and memory, making it triggered as desired could better manage the resources against read and write.

Implementation challenges

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions