zhangshenghang opened a new pull request, #12653:
URL: https://github.com/apache/seatunnel/pull/12653

   ## Purpose of the pull request
   
   Several storage-related e2e suites wait a fixed amount of time for a 
container to become *usable* (not merely started) and then proceed with a 
single attempt. Under CI load the service can need longer than the fixed 
budget, and the first real operation (bucket creation, first HDFS write, 
Gravitino catalog creation against MySQL) fails intermittently. This PR 
replaces those fixed sleeps with bounded readiness polling while keeping all 
assertions and test flows unchanged:
   
   - `HdfsFileIT`: the DataNode has no wait strategy of its own; the fixed 5s 
post-start sleep is replaced with polling `hdfs dfsadmin -report` on the 
NameNode until it reports `Live datanodes (1)` (2min bound).
   - `HdfsFileViewFsIT`: same replacement, polling until *each* of the two 
NameNodes reports its DataNode.
   - `LocalFileWithMetadataIT`: the container healthcheck only covers the MySQL 
server process; the fixed 10s sleep is replaced with polling `mysql -u.. -p.. 
-e "SELECT 1"` inside the container until the root account is usable — 
Gravitino's catalog creation connects to MySQL right after this.
   - `DatabendIT` / `DatabendCDCSinkIT`: the fixed 5s "MinIO starting" sleep 
followed by a single best-effort `createMinIOBucketWithAWSSDK` attempt (which 
only *warned* on failure) is replaced with bounded retry (60s) of the same 
bucket-creation call, so a slow MinIO startup can no longer leave Databend 
booting against a missing bucket.
   
   ## Verification
   
   - `./mvnw spotless:apply`
   - `./mvnw -pl 
seatunnel-e2e/seatunnel-connector-v2-e2e/connector-file-hadoop-e2e,seatunnel-e2e/seatunnel-connector-v2-e2e/connector-file-local-e2e,seatunnel-e2e/seatunnel-connector-v2-e2e/connector-databend-e2e
 -am -DskipTests package`
   
   No assertion / expected value was changed — only how the tests wait for 
infrastructure readiness.
   


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

Reply via email to