bvolpato opened a new pull request, #40859: URL: https://github.com/apache/beam/pull/40859
Expansion service startup currently accepts any TCP listener on the selected port. Another process can claim that port before the Java jar binds, leaving the helper with an unrelated service address. In [this CI run](https://github.com/apache/beam/actions/runs/40123572933), the failed expansion address also appeared as a Python worker endpoint. Check the expansion RPC before caching the address, detect an exited jar, and clean up failed startup. A wrong-service response gets a bounded retry on a fresh port. Expand-only services remain supported through a single probe within the startup deadline. Reproduced the old helper accepting an unrelated gRPC listener and a real jar failing to bind the occupied port. Focused tests, the race detector, vet, and the Windows process-wrapper build passed. Real-jar startup, early exit, and startup-deadline cleanup were also checked. The full GoPortable container workflow was not run locally. <!-- Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). - [x] Replace these instructions with a description of your change and why you have made it. - [ ] Mention the appropriate issue in your description (for example: `addresses #123` or `fixes #456`). - [ ] Update `CHANGES.md` with noteworthy changes. See [CONTRIBUTING.md]() for more details. --> -- 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]
