Do "HttpError"s cause cold starts in Google Cloud callable functions?

userCs04 0
Viewed 32

this google cloud functions documentation says

Uncaught exceptions or executions that crash the process can result in cold starts

Does that also apply to callable functions, defined with functions.https.onCall? My understanding is that the proper way to handle failures was to thow an HttpsError, e.g., throw new HttpsError("failed-precondition", "...")

Am I incorrect in that, or are HttpsErrors handled differently? What about other uncaught errors? Are they logged in cloud functions logs, or just returned to the user?

Thanks!

error-handling google-cloud-functions firebase
1 Answers

I would fully expect that HttpsError is internally caught by the functions framework so that it can execute code to issue the correct response to the caller. You can examine the source code yourself here.

The point that the documentation is trying to make is essentially that uncaught exceptions could mean something truly disastrous happened, and that it's not safe to leave the server instance around any more to serve further requests. Therefore, another server instance might take its place on the next request if needed, causing a cold start. If you want to minimize cold starts, you should strive to capture non-fatal errors and decide for yourself if they warrant a server restart.

Doug Stevenson0
Related