bobhan1 opened a new pull request, #68434:
URL: https://github.com/apache/doris/pull/68434
### What problem does this PR solve?
Issue Number: N/A
Related PR: #49332, #48400
Problem Summary:
The tablet state change publish regression still expects NULL in two
shadow-column values after an INT-to-VARCHAR schema change. Since #49332,
concurrent INSERTs correctly populate these values as `99` and `88`. Regenerate
the expected output with the regression framework.
A local run also hit `EHOSTDOWN` in the first concurrent INSERT after
restarting a BE. `startBackends()` waits for heartbeat and HTTP readiness,
while the peer BE's cached brpc connection can still be recovering. Add a
five-second wait after restart, while `ReportHandler.block` remains enabled,
before resuming the existing fault-injection sequence. The case already uses a
one-second FE heartbeat interval.
### Release note
None
### Check List (For Author)
- Test
- [x] Regression test
- `./build.sh --be --fe --cloud -j100` passed; FE, BE and MS runtime
logs confirmed the rebuilt base revision.
- The scoped Docker Cloud suite passed with `-forceGenOut` before
adding the restart wait. The generated output changes only the two expected
cells; no uncaught worker-thread exception occurred in that run.
- Final normal-mode validation was blocked before suite execution by a
missing local runtime image (`ImageNotFound`). The added restart wait is not
yet runtime-validated; CI validation is pending.
- `git diff --check` passed.
- [ ] Unit Test
- [ ] Manual test
- [ ] No need to test or manual test
- Behavior changed:
- [x] No.
- [ ] Yes.
- Does this need documentation?
- [x] No.
- [ ] Yes.
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
