sollhui opened a new pull request, #63180:
URL: https://github.com/apache/doris/pull/63180
### What problem does this PR solve?
Problem Summary:
In a single-BE deployment, Kafka routine load fetches topic metadata through
the only BE. If that BE cannot connect to Kafka, the metadata request fails and
the BE is skipped in the current retry loop. Then FE may have no normal
candidate backend left and falls back to backend ids in the routine load
blacklist.
The blacklist can contain stale backend ids that no longer exist in
`SystemInfoService`. In that case, `KafkaUtil` may get a null `Backend` and
throw a NullPointerException when calling `be.getHost()`. This hides the real
Kafka metadata error, such as broker connection failure.
This PR filters stale backend ids when reading the routine load blacklist
and adds a final null check before creating the BE address. The original Kafka
metadata error is preserved instead of being replaced by the secondary NPE.
A regression case is added with an invalid `kafka_broker_list` to verify
that routine load reports the expected Kafka metadata error path.
### Release note
None
### Check List (For Author)
- Test <!-- At least one of them must be included. -->
- [ ] Regression test
- [ ] Unit Test
- [ ] Manual test (add detailed scripts or steps below)
- [ ] No need to test or manual test. Explain why:
- [ ] This is a refactor/code format and no logic has been changed.
- [ ] Previous test can cover this change.
- [ ] No code files have been changed.
- [ ] Other reason <!-- Add your reason? -->
- Behavior changed:
- [ ] No.
- [ ] Yes. <!-- Explain the behavior change -->
- Does this need documentation?
- [ ] No.
- [ ] Yes. <!-- Add document PR link here. eg:
https://github.com/apache/doris-website/pull/1214 -->
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR should
merge into -->
--
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]
