You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mxnet.apache.org by GitBox <gi...@apache.org> on 2018/11/20 02:40:10 UTC
[GitHub] zhreshold commented on issue #13318: Improving multi-processing
reliability for gluon DataLoader
zhreshold commented on issue #13318: Improving multi-processing reliability for gluon DataLoader
URL: https://github.com/apache/incubator-mxnet/pull/13318#issuecomment-440116619
@YutingZhang I think it's okay to terminate worker processes right after shutdown, but I don't understand why you mentioned "The shutdown mechanism could not guarantee that all worker processes can be terminated".
In some cases, if worker has a propagated key queue(i.e., workers are busy), it's likely workers need longer time to exit, but the terminate signal (None, None) would make sure these daemon processes will quit when they finish their jobs, or get killed by the main process.
So I am curious do you know what caused the dangling processes?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services