Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16263
@holdenk @dusenberrymw There are timeouts for connection and reading data.
If we want to keep the connection timeout, which I think is reasonable, eagerly
evaluating of the first element is necessary in both JVM and Python sides.
Timeout for reading data needs to be removed if we want to completely solve
this. As the newer test case shows, the materialization time of RDD partitions
is unpredictable and can easily cause timeout problem. I removed the timeout
for reading operation on the socket. This can solve the test cases locally.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
