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.

Sign up for GitHub

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

Jump to bottom

AsyncInit only makes sense for regular lambda mode #507

Closed
smirnoal opened this issue Feb 28, 2023 · 0 comments · Fixed by #659
Closed

AsyncInit only makes sense for regular lambda mode #507

smirnoal opened this issue Feb 28, 2023 · 0 comments · Fixed by #659
Assignees
@richarddavison
Labels
enhancement
Milestone
Release 2.0

Comments

@smirnoal
Copy link

Excerpt from
https://github.com/awslabs/aws-serverless-java-container/wiki/Quick-start---Spring-Boot2#asynchronous-initialization

However, AWS Lambda limits the initialization phase to 10 second

this is only true for regular invokes. Provisioned concurrency and SnapStart have different timeouts. Async Init doesn't make much sense for the SnapStart usecase in particular, so it would be good to keep this option for regular invokes only.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@richarddavison richarddavison

Labels
enhancement
Projects
None yet
Milestone
Release 2.0
Development

Successfully merging a pull request may close this issue.

Deprecate asyncInit & account for other initialization types richarddd/aws-serverless-java-container
3 participants
@deki @smirnoal @richarddavison