Increasing retries in AWS Lambda The Next CEO of Stack OverflowSqlBulkCopy with retry logicIncrease number of shards in DynamoDB to spin up more lambdas in parallelAWS Lambda with Node.JS in productionWhat is the maximum number of event source mappings per AWS Lambda?How much AWS Lambda Function consume computation resources for executing jobs ?Quarz retry / misfireDownload files using AWS LambdaHow to handle aws Lambda retry in pythonCan an AWS lambda be set up to retry if it fails?Scala - Retry HTTP request with timeout

Why do we say “un seul M” and not “une seule M” even though M is a “consonne”?

Why did early computer designers eschew integers?

How should I connect my cat5 cable to connectors having an orange-green line?

My ex-girlfriend uses my Apple ID to login to her iPad, do I have to give her my Apple ID password to reset it?

What is the difference between 'contrib' and 'non-free' packages repositories?

Is a distribution that is normal, but highly skewed, considered Gaussian?

How to find if SQL server backup is encrypted with TDE without restoring the backup

Does the Idaho Potato Commission associate potato skins with healthy eating?

Could you use a laser beam as a modulated carrier wave for radio signal?

MT "will strike" & LXX "will watch carefully" (Gen 3:15)?

Mathematica command that allows it to read my intentions

Can this transistor (2n2222) take 6V on emitter-base? Am I reading datasheet incorrectly?

Shortening a title without changing its meaning

Can you teleport closer to a creature you are Frightened of?

How do I secure a TV wall mount?

Planeswalker Ability and Death Timing

Read/write a pipe-delimited file line by line with some simple text manipulation

Create custom note boxes

A hang glider, sudden unexpected lift to 25,000 feet altitude, what could do this?

What day is it again?

How to pronounce fünf in 45

Can a PhD from a non-TU9 German university become a professor in a TU9 university?

Is it possible to make a 9x9 table fit within the default margins?

"Eavesdropping" vs "Listen in on"



Increasing retries in AWS Lambda



The Next CEO of Stack OverflowSqlBulkCopy with retry logicIncrease number of shards in DynamoDB to spin up more lambdas in parallelAWS Lambda with Node.JS in productionWhat is the maximum number of event source mappings per AWS Lambda?How much AWS Lambda Function consume computation resources for executing jobs ?Quarz retry / misfireDownload files using AWS LambdaHow to handle aws Lambda retry in pythonCan an AWS lambda be set up to retry if it fails?Scala - Retry HTTP request with timeout










0

















I had a few questions about AWS lambdas and I couldn't find much details in the documentation

How can I increase the number of retries in AWS Lambda?

In case the maximum number of retries have occurred and whole Lambda has failed how can I get some sort of a notification?










share|improve this question






















  • did you get a chance to look into my answer?

    – Thales Minussi
    Mar 26 at 12:15















0

















I had a few questions about AWS lambdas and I couldn't find much details in the documentation

How can I increase the number of retries in AWS Lambda?

In case the maximum number of retries have occurred and whole Lambda has failed how can I get some sort of a notification?










share|improve this question






















  • did you get a chance to look into my answer?

    – Thales Minussi
    Mar 26 at 12:15













0












0








0










I had a few questions about AWS lambdas and I couldn't find much details in the documentation

How can I increase the number of retries in AWS Lambda?

In case the maximum number of retries have occurred and whole Lambda has failed how can I get some sort of a notification?










share|improve this question
















I had a few questions about AWS lambdas and I couldn't find much details in the documentation

How can I increase the number of retries in AWS Lambda?

In case the maximum number of retries have occurred and whole Lambda has failed how can I get some sort of a notification?







aws-lambda retry-logic






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 8 at 19:09









Venkat DabriVenkat Dabri

62




62












  • did you get a chance to look into my answer?

    – Thales Minussi
    Mar 26 at 12:15

















  • did you get a chance to look into my answer?

    – Thales Minussi
    Mar 26 at 12:15
















did you get a chance to look into my answer?

– Thales Minussi
Mar 26 at 12:15





did you get a chance to look into my answer?

– Thales Minussi
Mar 26 at 12:15












1 Answer
1






active

oldest

votes


















0














Lambda retries are based upon many factors. I suggest you take a look into the official docs to understand every single type of retry, but long story short:



  1. Stream-Based Synchronous Event sources can either retry or not. It depends on the Service.

  2. Asynchronous Event sources will retry up to three times. If all messages fail, you can then configure a DLQ to receive the failed messages

  3. (Stream-Based && Poll-Based Event Sources) (like Kinesis or Dynamo) will retry until the configured data retention. Be careful because if one message fails and the message itself is poisonous, it will keep retrying until it expires and no new messages will be processed

  4. (Non-Stream-Based && Poll-Based Event Sources) (SQS) will discard messages in case of failure (unless it was an invocation failure or a timeout). If discarded, they will be sent to a DLQ if you previously configured one.

So, based on the information above, we can then tackle your question around notifications: you can have another Lambda subscribed to your DLQ to receive the message and notify the way you want. Either by sending an e-mail from the function itself or sending it to SNS (to possibly send an e-mail directly or do whatever you want with it).



For the retry amount, that's not configurable for the already built-in values. The furthest you can go is to invoke a Lambda function synchronously from your code and, in case of exception, retry it as you wish (the exponential backoff, if desired, would also need to be coded manually)






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55069519%2fincreasing-retries-in-aws-lambda%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Lambda retries are based upon many factors. I suggest you take a look into the official docs to understand every single type of retry, but long story short:



    1. Stream-Based Synchronous Event sources can either retry or not. It depends on the Service.

    2. Asynchronous Event sources will retry up to three times. If all messages fail, you can then configure a DLQ to receive the failed messages

    3. (Stream-Based && Poll-Based Event Sources) (like Kinesis or Dynamo) will retry until the configured data retention. Be careful because if one message fails and the message itself is poisonous, it will keep retrying until it expires and no new messages will be processed

    4. (Non-Stream-Based && Poll-Based Event Sources) (SQS) will discard messages in case of failure (unless it was an invocation failure or a timeout). If discarded, they will be sent to a DLQ if you previously configured one.

    So, based on the information above, we can then tackle your question around notifications: you can have another Lambda subscribed to your DLQ to receive the message and notify the way you want. Either by sending an e-mail from the function itself or sending it to SNS (to possibly send an e-mail directly or do whatever you want with it).



    For the retry amount, that's not configurable for the already built-in values. The furthest you can go is to invoke a Lambda function synchronously from your code and, in case of exception, retry it as you wish (the exponential backoff, if desired, would also need to be coded manually)






    share|improve this answer



























      0














      Lambda retries are based upon many factors. I suggest you take a look into the official docs to understand every single type of retry, but long story short:



      1. Stream-Based Synchronous Event sources can either retry or not. It depends on the Service.

      2. Asynchronous Event sources will retry up to three times. If all messages fail, you can then configure a DLQ to receive the failed messages

      3. (Stream-Based && Poll-Based Event Sources) (like Kinesis or Dynamo) will retry until the configured data retention. Be careful because if one message fails and the message itself is poisonous, it will keep retrying until it expires and no new messages will be processed

      4. (Non-Stream-Based && Poll-Based Event Sources) (SQS) will discard messages in case of failure (unless it was an invocation failure or a timeout). If discarded, they will be sent to a DLQ if you previously configured one.

      So, based on the information above, we can then tackle your question around notifications: you can have another Lambda subscribed to your DLQ to receive the message and notify the way you want. Either by sending an e-mail from the function itself or sending it to SNS (to possibly send an e-mail directly or do whatever you want with it).



      For the retry amount, that's not configurable for the already built-in values. The furthest you can go is to invoke a Lambda function synchronously from your code and, in case of exception, retry it as you wish (the exponential backoff, if desired, would also need to be coded manually)






      share|improve this answer

























        0












        0








        0







        Lambda retries are based upon many factors. I suggest you take a look into the official docs to understand every single type of retry, but long story short:



        1. Stream-Based Synchronous Event sources can either retry or not. It depends on the Service.

        2. Asynchronous Event sources will retry up to three times. If all messages fail, you can then configure a DLQ to receive the failed messages

        3. (Stream-Based && Poll-Based Event Sources) (like Kinesis or Dynamo) will retry until the configured data retention. Be careful because if one message fails and the message itself is poisonous, it will keep retrying until it expires and no new messages will be processed

        4. (Non-Stream-Based && Poll-Based Event Sources) (SQS) will discard messages in case of failure (unless it was an invocation failure or a timeout). If discarded, they will be sent to a DLQ if you previously configured one.

        So, based on the information above, we can then tackle your question around notifications: you can have another Lambda subscribed to your DLQ to receive the message and notify the way you want. Either by sending an e-mail from the function itself or sending it to SNS (to possibly send an e-mail directly or do whatever you want with it).



        For the retry amount, that's not configurable for the already built-in values. The furthest you can go is to invoke a Lambda function synchronously from your code and, in case of exception, retry it as you wish (the exponential backoff, if desired, would also need to be coded manually)






        share|improve this answer













        Lambda retries are based upon many factors. I suggest you take a look into the official docs to understand every single type of retry, but long story short:



        1. Stream-Based Synchronous Event sources can either retry or not. It depends on the Service.

        2. Asynchronous Event sources will retry up to three times. If all messages fail, you can then configure a DLQ to receive the failed messages

        3. (Stream-Based && Poll-Based Event Sources) (like Kinesis or Dynamo) will retry until the configured data retention. Be careful because if one message fails and the message itself is poisonous, it will keep retrying until it expires and no new messages will be processed

        4. (Non-Stream-Based && Poll-Based Event Sources) (SQS) will discard messages in case of failure (unless it was an invocation failure or a timeout). If discarded, they will be sent to a DLQ if you previously configured one.

        So, based on the information above, we can then tackle your question around notifications: you can have another Lambda subscribed to your DLQ to receive the message and notify the way you want. Either by sending an e-mail from the function itself or sending it to SNS (to possibly send an e-mail directly or do whatever you want with it).



        For the retry amount, that's not configurable for the already built-in values. The furthest you can go is to invoke a Lambda function synchronously from your code and, in case of exception, retry it as you wish (the exponential backoff, if desired, would also need to be coded manually)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 8 at 20:10









        Thales MinussiThales Minussi

        1,585419




        1,585419





























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55069519%2fincreasing-retries-in-aws-lambda%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Identity Server 4 is not redirecting to Angular app after login2019 Community Moderator ElectionIdentity Server 4 and dockerIdentityserver implicit flow unauthorized_clientIdentityServer Hybrid Flow - Access Token is null after user successful loginIdentity Server to MVC client : Page Redirect After loginLogin with Steam OpenId(oidc-client-js)Identity Server 4+.NET Core 2.0 + IdentityIdentityServer4 post-login redirect not working in Edge browserCall to IdentityServer4 generates System.NullReferenceException: Object reference not set to an instance of an objectIdentityServer4 without HTTPS not workingHow to get Authorization code from identity server without login form

            2005 Ahvaz unrest Contents Background Causes Casualties Aftermath See also References Navigation menue"At Least 10 Are Killed by Bombs in Iran""Iran"Archived"Arab-Iranians in Iran to make April 15 'Day of Fury'"State of Mind, State of Order: Reactions to Ethnic Unrest in the Islamic Republic of Iran.10.1111/j.1754-9469.2008.00028.x"Iran hangs Arab separatists"Iran Overview from ArchivedConstitution of the Islamic Republic of Iran"Tehran puzzled by forged 'riots' letter""Iran and its minorities: Down in the second class""Iran: Handling Of Ahvaz Unrest Could End With Televised Confessions""Bombings Rock Iran Ahead of Election""Five die in Iran ethnic clashes""Iran: Need for restraint as anniversary of unrest in Khuzestan approaches"Archived"Iranian Sunni protesters killed in clashes with security forces"Archived

            Can't initialize raids on a new ASUS Prime B360M-A motherboard2019 Community Moderator ElectionSimilar to RAID config yet more like mirroring solution?Can't get motherboard serial numberWhy does the BIOS entry point start with a WBINVD instruction?UEFI performance Asus Maximus V Extreme