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

Added information about Lambda Interruption #199

Merged
merged 6 commits into from Oct 20, 2016
Jump to file or symbol
Failed to load files and symbols.
+1 −0
Diff settings

Always

Just for now

View
@@ -1055,6 +1055,7 @@ Lambda
- 🔸Lambda is a new technology. As of mid 2016, only a few companies are using it for large-scale production applications.
- 🔸Managing lots of Lambda functions is a workflow challenge, and tooling to manage Lambda deployments is still immature.
- 🔸AWS’ official workflow around managing function [versioning and aliases](https://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases.html) is painful.
- ❗Currently (October,2016) Lambda functions can sometimes stop working for 2-3 minutes for failure recovery purposes according to a support ticket answer from Lambda dev team. They are working to prevent this in the future.

This comment has been minimized.

@ThanosBaskous

ThanosBaskous Oct 15, 2016

Collaborator

Suggestion: "(as of October, 2016)"

@ThanosBaskous

ThanosBaskous Oct 15, 2016

Collaborator

Suggestion: "(as of October, 2016)"

This comment has been minimized.

@halilduygulu
@halilduygulu

This comment has been minimized.

@ThanosBaskous

ThanosBaskous Oct 15, 2016

Collaborator

I'm not 100% clear on what "for failure recovery purposes" means - is it 2-3 minutes while recovering from failure?

@ThanosBaskous

ThanosBaskous Oct 15, 2016

Collaborator

I'm not 100% clear on what "for failure recovery purposes" means - is it 2-3 minutes while recovering from failure?

This comment has been minimized.

@halilduygulu

halilduygulu Oct 15, 2016

As i sad it was a support ticket response. I don't have link to it because it is in our account, but i can copy paste the exact response here.

I've received an update from the engineering team.
They replied that customer may see their stream stop processing for three minute or less very infrequently due to certain failure recovery modes in our system. Their stream processing should then resume and recover from the delay.
They are working improvements to our system that should eliminate these sorts of pauses, we don't have a solid ETA on when that will be available.

@halilduygulu

halilduygulu Oct 15, 2016

As i sad it was a support ticket response. I don't have link to it because it is in our account, but i can copy paste the exact response here.

I've received an update from the engineering team.
They replied that customer may see their stream stop processing for three minute or less very infrequently due to certain failure recovery modes in our system. Their stream processing should then resume and recover from the delay.
They are working improvements to our system that should eliminate these sorts of pauses, we don't have a solid ETA on when that will be available.

This comment has been minimized.

@halilduygulu

halilduygulu Oct 15, 2016

Also it happened to my 2 functions 4 times in total last week.

@halilduygulu

halilduygulu Oct 15, 2016

Also it happened to my 2 functions 4 times in total last week.

This comment has been minimized.

@mklopets

mklopets Oct 30, 2016

There's a huge difference between "Lambda functions can stop working" and "streams can stop processing" though. This should belong in the Kinesis section then, imo.

@mklopets

mklopets Oct 30, 2016

There's a huge difference between "Lambda functions can stop working" and "streams can stop processing" though. This should belong in the Kinesis section then, imo.

🚧 [*Please help expand this incomplete section.*](CONTRIBUTING.md)
ProTip! Use n and p to navigate between commits in a pull request.