hello-stephen opened a new pull request, #69204:
URL: https://github.com/apache/doris/pull/69204

   ### What problem does this PR solve?
   
   Branch-4.1 External #330 failed two Kerberos/HDFS suites: 
`test_two_hive_kerberos` hit a DataNode SASL handshake error and 
`iceberg_on_hms_and_filesystem_and_dlf` sent a SIMPLE RPC to a Kerberos 
NameNode. BE logs show Kerberos handlers and Hadoop security properties were 
present while other SIMPLE HDFS handlers were active on the same BE. Both 
suites passed in isolated serial External #331 (`test_two_hive_kerberos`: 27.6 
s; `iceberg_on_hms_and_filesystem_and_dlf`: 856 s). This points to mixed HDFS 
client concurrency, while leaving the deeper BE/library cause open.
   
   The regression runner starts `nonConcurrent` suites after normal suites 
finish, but currently waits for Docker suites only **after** it starts 
`nonConcurrent` work. Move that wait before the single-suite stage. Mark the 
two affected Kerberos/HDFS suites `nonConcurrent`, so they run after normal and 
Docker suites, and serially with each other. This also ensures Docker futures 
finish when `runNonConcurrent=false`.
   
   ### Validation
   
   - Exact case statuses from isolated External #331: both Kerberos/HDFS suites 
passed. This is diagnostic evidence, not patched-code validation.
   - `git diff --check` passed.
   - Targeted patched case execution with `-runNonConcurrent true` and parallel 
normal/Docker suites is pending. Keep the PR as draft until terminal CI 
verifies scheduling and case results.
   
   ### Release note
   
   None. Regression scheduler and test tags only.
   


-- 
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]

Reply via email to