Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8258#discussion_r37317128
--- Diff: core/src/main/scala/org/apache/spark/deploy/PythonRunner.scala ---
@@ -52,10 +52,16 @@ object PythonRunner {
gatewayServer.start()
}
})
- thread.setName("py4j-gateway")
+ thread.setName("py4j-gateway-init")
thread.setDaemon(true)
thread.start()
+ // Wait until the gateway server has started, so that we know which
port is it bound to.
+ // `gatewayServer.start()` will start a new thread and run the server
code there, after
+ // initializing the socket, so the thread started above will end as
soon as the server is
+ // ready to serve connections.
+ thread.join()
--- End diff --
I wish there was something, but the GatewayServer API is super weird.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
