Closed filipski closed 2 years ago
@selitvin we see this problem, too - any idea what causes this?
This is my single greatest annoyance with Petastorm. It forces us to run_training 2> errors.txt just to hide this.
It is actually causing our application to crash. Because some modules are not imported when the worker is initialzied, some modules, which we are using withing the worker's workflow, are not available for the sub-process, and the application throws an exception.
How shall we fix that?
I can take a look at this later this week. This is something regarding the way we spawn a process-pool worker and the way unpickling works. Feel free to poke that piece of the code if you need it sooner.
Could have a look at it? I also makes our application crash.
Thank you
petastorm==0.11.4 with the fix is now available on pypi
I noticed the following warnings while running benchmarks with pure Pyton reader using process workers (code snippet available in https://github.com/uber/petastorm/issues/584):
This warning is repeated as many times as the amount of workers in the pool.