mikebridge opened a new pull request, #45647:
URL: https://github.com/apache/superset/pull/45647

   ### SUMMARY
   
   TL;DR: Avoid intermittent Hive CI startup failures by keeping Hadoop's web 
UI ports off the runner host.
   
   The Hive job can fail before tests start with `failed to bind host port 
0.0.0.0:50070/tcp: address already in use` ([example failed 
job](https://github.com/apache/superset/actions/runs/39874426313/job/120157174987)).
 The Compose stack publishes namenode port 50070 and datanode port 50075, both 
within Linux's default ephemeral port range of 32768–60999 ([kernel 
documentation](https://docs.kernel.org/networking/ip-sysctl.html#ip-variables)).
 Publishing them can collide with a port already allocated on the runner.
   
   Remove those two host mappings. Inter-service readiness checks still use 
`namenode:50070` and `datanode:50075` on the Compose network. Hive's host 
connection on port 10000 and the metastore mapping on 9083 stay unchanged. A 
short comment explains how contributors can publish the web UIs through a local 
Compose override.
   
   No docs or scripts reference these web UIs through localhost.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   
   Not applicable; CI service configuration only.
   
   ### TESTING INSTRUCTIONS
   
   - `UPLOAD_FOLDER=/tmp/superset-hive-config-uploads docker compose -f 
scripts/databases/hive/docker-compose.yml config` passes. The existing obsolete 
`version` warning is unchanged.
   - Parsed configuration comparison confirms only the two web UI host mappings 
are removed; 10000/9083 and inter-service checks are retained.
   - Changed-file pre-commit hooks pass.
   - The Hive stack was not started locally. `test-postgres-hive` on this draft 
PR is the integration validation; its result is pending.
   
   ### ADDITIONAL INFORMATION
   
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   


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