phoerious commented on issue #24357: URL: https://github.com/apache/beam/issues/24357#issuecomment-1331471035
No, it does not happen consistently. it is probably dependent on the host's utilisation or IO saturation. I also don't think it's Flink-related. There is nothing special in the logs. It usually hangs after pip's last installation log dump, just before the final "Successfully installed pkg1 pkg2 ..." line. Reading pip's or the worker's stdout via `cat` will let it continue like nothing happened. Redirecting everything `/dev/null` may be a bit harsh, but redirecting pip's output to the worker's stdout is definitely useless. What is shown as the container's log output is the worker pool output, which displays only the pool's own stdout and log.Printf() messages as well as log.Printf() messages from the workers (apparently). It does not include normal stdout of child processes, including the workers. Therefore no pip output gets logged anywhere, really. In order to read or log it, you have to attach to the container and read from `/proc/PID/fd/1` directly. -- 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]
