Skip to content

branch-4.1: [regression-test](variant) Fix schema change wait timeout #65139#65317

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-65139-branch-4.1
Open

branch-4.1: [regression-test](variant) Fix schema change wait timeout #65139#65317
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-65139-branch-4.1

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #65139

### What problem does this PR solve?

Fixes a flaky Cloud P0 failure in
`variant_p0/schema_change/schema_change.groovy`.

The case waits for the latest schema-change job before issuing the next
ALTER. The old helper could return after timeout without observing
`FINISHED`, because `useTime == OpTimeout` still passed
`assertTrue(useTime <= OpTimeout)`. Then the case could run `DROP INDEX`
while the table was still in `SCHEMA_CHANGE`.

Remote logs from a failing run showed:

- the case polled `SHOW ALTER TABLE COLUMN` for about 60s without
logging `latest alter job finished`
- `DROP INDEX` failed about 9s before the schema-change job actually
finished
- the schema-change RUNNING phase took about 69s in that run

### How is this fixed?

- Increase the schema-change wait timeout from 60s to 120s.
- Make the helper require an explicit `FINISHED` observation.
- Include the last `SHOW ALTER TABLE COLUMN` result in the timeout
failure message.

### Check

- `git diff --check`

No local regression rerun was performed.
@github-actions github-actions Bot requested a review from yiguolei as a code owner July 7, 2026 08:15
@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?

@hello-stephen

Copy link
Copy Markdown
Contributor

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