branch-4.0: [improvement](regression) Reduce external regression memory#65812
Open
suxiaogang223 wants to merge 2 commits into
Open
branch-4.0: [improvement](regression) Reduce external regression memory#65812suxiaogang223 wants to merge 2 commits into
suxiaogang223 wants to merge 2 commits into
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Member
Author
|
run buildall |
…#65459) Problem Summary: The P0 external regression pipeline currently starts several memory-intensive Docker services for relatively low-priority compatibility coverage. This PR reduces the P0 resource footprint by moving the following service-specific cases and expected results to P2: - DB2 - SQL Server / MSSQL, including the SQL Server Trino connector and row-count coverage - OceanBase - Elasticsearch 5/6/7/8, including ES MTMV coverage The SQL Server row-count checks are split from the mixed P0 JDBC suite so the existing MySQL, PostgreSQL, and Oracle P0 coverage remains unchanged. The ES MTMV database reference is updated to match its new P2 directory. Kerberos was evaluated separately but remains required in P0 for safety. The earlier Kerberos move has been fully reverted, so the cumulative diff of this PR contains no Kerberos file changes. This PR only changes regression-suite grouping and paths. It does not change Docker service configuration, runtime behavior, query behavior, or expected test results. (cherry picked from commit 394740c)
…ache#65564) Problem Summary: The external regression pipeline currently runs two heavyweight Kerberos containers. Each container starts HiveServer2, YARN ResourceManager/NodeManager, MariaDB, and other processes that the Doris Kerberos cases do not use, resulting in roughly 4.3 GB of combined memory usage. This PR replaces those images with a minimal reusable environment based on Apache Hive 3.1.3. Each realm now runs only: - a native MIT Kerberos KDC - one HDFS NameNode and DataNode - one Kerberos-enabled Hive Metastore backed by embedded Derby The existing realm names, ports, service principals, client principals, and keytab filenames remain unchanged. JVM heaps are explicitly bounded, and each container has a 1.5 GB memory limit. HDFS listeners bind independently from their advertised Kerberos hostnames, and startup now waits until each DataNode is registered with its NameNode. The container no longer owns Hive test fixtures. `test_single_hive_kerberos` and `test_two_hive_kerberos` now create their test database, Hive table, and four rows through Doris. `test_non_catalog_kerberos` also creates its database so it no longer depends on suite execution order. Existing expected output files remain unchanged. (cherry picked from commit 52e1545)
suxiaogang223
force-pushed
the
codex/backport-65564-4.0
branch
from
July 20, 2026 08:11
2d2a3f9 to
9ecc953
Compare
suxiaogang223
changed the title
Member
Author
|
run buildall |
suxiaogang223
marked this pull request as ready for review
July 20, 2026 08:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Issue Number: None
Related PRs: #65459, #65564
Problem Summary: Backport two external regression memory optimizations from master to branch-4.0 in their master merge order:
394740cc350b0c1fb082d2fc5040d9617c2da0fcfrom [test](regression) Move memory-intensive external cases to P2 #65459 to move DB2, SQL Server, OceanBase, and Elasticsearch compatibility cases from P0 to P2.52e154530ff72b53d205f77d845a3072e44ea5f1from [improvement](regression) Reduce Kerberos test environment memory #65564 to replace the heavyweight Kerberos containers with the minimal KDC, HDFS, and Hive Metastore environment.Both automatic backports conflicted with release-branch suite layout, deleted ES coverage, Kerberos bootstrap configuration, and third-party launcher differences. The conflicts were resolved manually while retaining branch-4.0 changes, including keeping the ES predicate-correctness case deleted.
Release note
None
Check List (For Author)
bash -nfor the changed Kerberos and third-party startup scriptsgit diff --check origin/branch-4.0..HEAD