Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation improvement for multiprocessing: a script which spawns processes on import will cause system failure #7308

Closed
stscijgbot-jp opened this issue Oct 19, 2022 · 3 comments · Fixed by #8408

Comments

@stscijgbot-jp
Copy link
Collaborator

stscijgbot-jp commented Oct 19, 2022

Issue JP-2980 was created on JIRA by Tyler Pauly:

A help desk ticket (INC0182968) has exposed a weakness in our documentation regarding the use of parallel processing in the pipeline.

If multiprocessing is active, when running from a script (i.e. python multiproc_detector1.py), importing that script must not spawn more processes. This is typically prevented by placing process-spawning code inside the if __name__ == '__main__': block.

Users are not warned of this requirement in the documentation; if not followed, this will lead to a system crash as the code will attempt to spawn an ever-increasing number of processes.

@stscijgbot-jp stscijgbot-jp changed the title Multiprocessed ramp_fit data leads to parallel Detector1Pipeline processes? Documentation improvement for multiprocessing: a script which spawns processes on import will cause system failure Oct 20, 2022
@stscijgbot-jp
Copy link
Collaborator Author

Comment by Tyler Pauly on JIRA:

From standup discussion today, this ticket links to the "nested multiprocessing" issue described by a user: https://jira.stsci.edu/browse/JP-3586

@stscijgbot-jp
Copy link
Collaborator Author

Comment by Maria Pena-Guerrero on JIRA:

Documentation included by: #8408

@stscijgbot-jp
Copy link
Collaborator Author

Comment by Howard Bushouse on JIRA:

Fixed by #8408

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment