Fuzz test: fuzz_failover_mito_regions fails

[killme2008]

What type of bug is this?

Incorrect result

What subsystems are affected?

Other

Minimal reproduce step

See https://github.com/GreptimeTeam/greptimedb/actions/runs/9731119264/job/26855350465

2024-06-30T10:56:40.7542618Z artifact_prefix='tests-fuzz/artifacts/fuzz_failover_mito_regions/'; Test unit written to tests-fuzz/artifacts/fuzz_failover_mito_regions/timeout-adc83b19e793491b1c6ea0fd8b46cd9f32e592fc
2024-06-30T10:56:40.7543574Z Base64: Cg==
2024-06-30T10:56:40.7543870Z ==43558== ERROR: libFuzzer: timeout after 1672 seconds
2024-06-30T10:56:40.7544254Z SUMMARY: libFuzzer: timeout
2024-06-30T10:56:40.7749506Z
2024-06-30T10:56:40.7750467Z ────────────────────────────────────────────────────────────────────────────────
2024-06-30T10:56:40.7751159Z
2024-06-30T10:56:40.7751327Z Failing input:
2024-06-30T10:56:40.7751581Z
2024-06-30T10:56:40.7752384Z    tests-fuzz/artifacts/fuzz_failover_mito_regions/timeout-adc83b19e793491b1c6ea0fd8b46cd9f32e592fc
2024-06-30T10:56:40.7753254Z
2024-06-30T10:56:41.5361650Z Output of `std::fmt::Debug`:
2024-06-30T10:56:41.5362449Z
2024-06-30T10:56:41.5362813Z    FuzzInput {
2024-06-30T10:56:41.5363186Z        seed: 10,
2024-06-30T10:56:41.5363665Z        columns: 20,
2024-06-30T10:56:41.5364113Z        rows: 1185,
2024-06-30T10:56:41.5364539Z        tables: 55,
2024-06-30T10:56:41.5364986Z        inserts: 2,
2024-06-30T10:56:41.5365430Z    }
2024-06-30T10:56:41.5365866Z
2024-06-30T10:56:41.5366077Z Reproduce with:
2024-06-30T10:56:41.5366329Z
2024-06-30T10:56:41.5367641Z    cargo fuzz run --fuzz-dir tests-fuzz -D --sanitizer=none fuzz_failover_mito_regions tests-fuzz/artifacts/fuzz_failover_mito_regions/timeout-adc83b19e793491b1c6ea0fd8b46cd9f32e592fc
2024-06-30T10:56:41.5368488Z
2024-06-30T10:56:41.5368762Z Minimize test case with:
2024-06-30T10:56:41.5368955Z
2024-06-30T10:56:41.5369780Z    cargo fuzz tmin --fuzz-dir tests-fuzz -D --sanitizer=none fuzz_failover_mito_regions tests-fuzz/artifacts/fuzz_failover_mito_regions/timeout-adc83b19e793491b1c6ea0fd8b46cd9f32e592fc
2024-06-30T10:56:41.5370589Z
2024-06-30T10:56:41.5370904Z ────────────────────────────────────────────────────────────────────────────────
2024-06-30T10:56:41.5371252Z
2024-06-30T10:56:41.5371396Z Error: Fuzz target exited with exit status: 70
2024-06-30T10:56:41.5384310Z ##[error]Process completed with exit code 1.
2024-06-30T10:56:41.5429659Z ##[group]Run kubectl describe nodes
2024-06-30T10:56:41.5430061Z kubectl describe nodes
2024-06-30T10:56:41.6471568Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

What did you expect to see?

Should pass

What did you see instead?

Failed

What operating system did you use?

Not relevant

What version of GreptimeDB did you use?

Not relevant

Relevant log output and stack trace

No response

[WenyXu]

I reduced the inserting data size of test in 94e24fe870e47ebeb2717aeecded1252b45842a8.
It seems like it takes too much time due to too much compaction and flushing.

[killme2008]

Another case

https://github.com/GreptimeTeam/greptimedb/actions/runs/9846576576/job/27184816015

@WenyXu