Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-90883545
Yeah, it happens frequently that the Java side dies without calling
`close()`, for example when the TaskManager encounters an unrecoverable error
and terminates.
+1 for having a safety net, timeout sounds good. It can be a rather high
timeout, though (order of several minutes)
Ideally, the python process would also be a child process of the JVM
process, to it is killes anyways by the kernel when the JVM process exists, as
another safety net.
---
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.
---
