Skip to content

[fix](regression) Stabilize base compaction E-808 case#65320

Open
Yukang-Lian wants to merge 1 commit into
apache:masterfrom
Yukang-Lian:fix/doris-26893-compaction-case-master
Open

[fix](regression) Stabilize base compaction E-808 case#65320
Yukang-Lian wants to merge 1 commit into
apache:masterfrom
Yukang-Lian:fix/doris-26893-compaction-case-master

Conversation

@Yukang-Lian

@Yukang-Lian Yukang-Lian commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: The compaction regression case expected the manual base compaction HTTP response to synchronously contain E-808. The backend only waits 2 seconds for manual base compaction before returning a successful trigger response, while the background compaction task can record BE_NO_SUITABLE_VERSION later. This makes the case flaky when the expected E-808 is written after the HTTP response. The case now accepts a synchronous E-808 response and otherwise polls the tablet compaction status until the background task records E-808.

### What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: The compaction regression case expected the manual base compaction HTTP response to synchronously contain E-808. The backend only waits 2 seconds for manual base compaction before returning a successful trigger response, while the background compaction task can record BE_NO_SUITABLE_VERSION later. This makes the case flaky when the expected E-808 is written after the HTTP response. The case now accepts a synchronous E-808 response and otherwise polls the tablet compaction status until the background task records E-808.

### Release note

None

### Check List (For Author)

- Test: Manual test
    - Ran git diff --check for the modified regression case
    - Did not run the full regression case because no isolated local master Doris cluster is running and the case requires TPCH SF100 S3 data
- Behavior changed: No
- Does this need documentation: No
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@Yukang-Lian Yukang-Lian marked this pull request as ready for review July 7, 2026 09:12
@Yukang-Lian

Copy link
Copy Markdown
Collaborator Author

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants