Scaling implications of maxInFlightUpdates and maxTotalUpdates

Community Support
1

Hi team,

We have recently encountered the following error:

RESOURCE_EXHAUSTED: limit on number of concurrent in-flight updates has been reached (10)

and while reading limits documentation, we came across the default maximum total updates which is 2000. In our use case, we need more than 10 concurrent in-flight updates and more than 2000 total updates.

Thus, the question is what are the implications of configuring those numbers to be bigger? from both Temporal and our services side.

Thank you for your support.

2

This is configurable with dynamic config history.maxInFlightUpdates, default 10, can set to 0 to disable having a limit.

From what I understand its similar implications as with buffered events limit which is in place to prevent higher memory use (shard mutable state)