xylaaaaa opened a new pull request, #64113: URL: https://github.com/apache/doris/pull/64113
### What problem does this PR solve? Issue Number: None Related PR: #61932 Problem Summary: The master external regression suite can hang in `test_paimon_jdbc_catalog` while running `docker exec ... spark-sql`. Root cause: - the Spark seed path used `http://${externalEnvIp}:${minioPort}` as the MinIO endpoint - that host-mapped endpoint may be reachable from the host but not from inside the `spark-iceberg` container - Spark can then block in repeated S3A metadata retries - the local `ProcessBuilder` helper waited without consuming stdout/stderr or enforcing a timeout, so the suite could stay stuck until the CI job timeout This change makes only the Spark seed command use the paired MinIO container endpoint when it exists in the Docker network. The Doris catalog configuration still uses the configured external endpoint. The command helper now consumes stdout/stderr and applies bounded timeouts so future command failures surface instead of silently hanging. ### Release note None ### Check List (For Author) - Test: Manual test - Source guard for the Paimon JDBC seed command failed before the change and passed after the change - `git diff HEAD~1..HEAD --check -- regression-test/suites/external_table_p0/paimon/test_paimon_jdbc_catalog.groovy` - Attempted `timeout 180 ./run-regression-test.sh --run -d external_table_p0/paimon -s test_paimon_jdbc_catalog`; it timed out during regression framework shade/package before running the suite - Behavior changed: Yes (the regression Spark seed step uses the Docker-network MinIO endpoint when the paired MinIO container exists; Doris catalog access still uses the configured external endpoint) - Does this need documentation: No -- 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]
