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

Can't be used in AWS Lambda #51

Open
yilinjuang opened this issue Sep 10, 2018 · 5 comments
Open

Can't be used in AWS Lambda #51

yilinjuang opened this issue Sep 10, 2018 · 5 comments

Comments

@yilinjuang
Copy link

When setting use_signal to False, it uses multiprocessing.Queue which isn't support in AWS Lambda.
Are we gonna have other approach to not use signal? Maybe use multiprocessing.Pipe? Thanks

AWS Document: https://aws.amazon.com/blogs/compute/parallel-processing-in-python-with-aws-lambda/

@pnpnpn
Copy link
Owner

pnpnpn commented Sep 10, 2018

Good point. Do you want to make a PR for that?

@yilinjuang
Copy link
Author

Sure. How about adding another argument other than use_signal? Or change the implementation inside use_signal?

@bitranox
Copy link

can You provide a code snippet to test please

@yilinjuang
Copy link
Author

@bitranox any lambda can reproduce the issue. Can refer to here and here for how to create one.

@bitranox
Copy link

bitranox commented Sep 13, 2018

ok, I changed the implementation to use multiprocess.pipe (halfduplex). It is faster, more elegant and probably can work with AWS (let me know).
See : https://github.com/bitranox/wrapt-timeout-decorator
or
#53
yours sincerely
Robert

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants