suxiaogang223 opened a new pull request, #66313:
URL: https://github.com/apache/doris/pull/66313
### What problem does this PR solve?
Issue Number: None
Related PR: #66254
Problem Summary:
The branch-4.0 fix in #66254 also applies to master in four places:
- The lightweight Kerberos environment creates principals with random keys
on every container start, so keytabs provisioned to Doris hosts no longer match
after the KDC is rebuilt.
- A successful Hive baseline restore skips `init-hive-baseline.sh`, while
the incremental Hive module list does not include the Paimon HMS table
definitions. The restored environment therefore misses the Paimon databases.
- `test_file_cache_query_limit` sends BE brpc and HTTP requests to
`externalEnvIp`, which identifies the third-party Docker host rather than the
backend host in a multi-host deployment.
- `test_file_cache_statistics` treats each queue's `max_size` as a hard
limit even though queues may borrow unused capacity from one another. The
actual hard bound is the total file-cache capacity.
This PR uses deterministic Kerberos keys, registers Paimon HMS as an
incremental Hive module, resolves the single live backend before accessing BE
endpoints, and validates normal-queue usage against the sum of all queue
capacities.
The ES database-name fix from #66254 is intentionally not included because
master has already migrated this suite to external ES catalogs and no longer
switches to the old internal P0 database.
### Release note
None
### Check List (For Author)
- Test
- [ ] Regression test
- [ ] Unit Test
- [x] Manual test
- `bash -n` for all changed shell scripts
-
`docker/thirdparties/test/run-thirdparties-docker-hive-bootstrap-groups-test.sh`
- Paimon HMS module selection and refresh harness
- Groovy CONVERSION-phase parse for both changed regression suites
- Full external regression was not run because it requires a
multi-host Doris cluster and the third-party Docker stack
- Behavior changed:
- [x] No
- [ ] Yes
- Does this need documentation?
- [x] No
- [ ] Yes
--
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]
