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

Added information about Lambda Interruption #199

Merged
merged 6 commits into from
Oct 20, 2016
Merged

Added information about Lambda Interruption #199

Changes from 3 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
71b3cbc
Added some Redshift tips.
Oct 14, 2016
d433e5c
Lambda stopping issue added.
Oct 14, 2016
c99bddb
Lambda stopping issue added.
Oct 14, 2016
994ca7b
date typo
Oct 15, 2016
25df505
Added link and undocumented icon.
Oct 17, 2016
cc1c153
dev -> development
Oct 18, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: "(as of October, 2016)"

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link

@mklopets mklopets Oct 30, 2016 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

Expand Down