Exponential backoff time on Firebase cloud function retries
274 views
Skip to first unread message
Deepak Kumar
Jul 27, 2022, 1:06:32 PM7/27/22
to Firebase Google Group
Hi all,
Disclaimer: This message and its attachment(s) are confidential and privileged. The information is solely intended for the individual or the entity it is addressed to. If you are not the intended recipient of this message, you are not authorized to read, forward, print, retain, copy or disseminate this message or any part of it. Please reply to this message and follow with its deletion, so that we can ensure further emails are not sent in the future. However, we have taken reasonable precautions to ensure that any attachment to this e-mail has been swept for viruses, e-mail communications cannot be guaranteed to be secure or error-free, as information can be corrupted, intercepted, lost, or contain viruses. We do not accept liability for such matter or their consequences.
Is there any option to add exponential back off in cloud function retry on failure so that retry
invocation won't happen immediately ?
Currently, I am using the cloud function default retries mechanism. but, the problem is retries are invoked immediately after the execution is failed, this has few issues like increased function invocation, it can overload existing 3rd party API if thousand of user are connected and failure occurs.
invocation won't happen immediately ?
Currently, I am using the cloud function default retries mechanism. but, the problem is retries are invoked immediately after the execution is failed, this has few issues like increased function invocation, it can overload existing 3rd party API if thousand of user are connected and failure occurs.
Having an exponential backoff time at cloud function retry could fix the issue, so I just wanted to know whether firebase has any feature which can solve my purpose or planning to add this feature in upcoming releases ?
Disclaimer: This message and its attachment(s) are confidential and privileged. The information is solely intended for the individual or the entity it is addressed to. If you are not the intended recipient of this message, you are not authorized to read, forward, print, retain, copy or disseminate this message or any part of it. Please reply to this message and follow with its deletion, so that we can ensure further emails are not sent in the future. However, we have taken reasonable precautions to ensure that any attachment to this e-mail has been swept for viruses, e-mail communications cannot be guaranteed to be secure or error-free, as information can be corrupted, intercepted, lost, or contain viruses. We do not accept liability for such matter or their consequences.
Kato Richardson
Jul 27, 2022, 1:40:39 PM7/27/22
to Firebase Google Group
Hi Deepak,
It looks like you could use a queue strategy with Cloud Tasks; explained here. I hope that helps!
☼, Kato
--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/171ac01f-b630-481d-a346-9d9f2587a91cn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages