# Frontend resource\_exhausted ConcurrentLimit

**URL:** <https://community.temporal.io/t/frontend-resource-exhausted-concurrentlimit/13278>\
**Category:** Server Deployment\
**Tags:** frontend\
**Created:** [August 25, 2024, 3:34pm UTC](https://community.temporal.io/t/frontend-resource-exhausted-concurrentlimit/13278 "2024-08-25T15:34:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![frko](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/frko/32/4160_2.png) [@frko](https://community.temporal.io/u/frko)\
**Post date:** [August 25, 2024, 3:34pm UTC](https://community.temporal.io/t/frontend-resource-exhausted-concurrentlimit/13278/1 "2024-08-25T15:34:30Z")

</div>

We’re running into an issue with our Temporal setup where we see the following error counter increase to about 300 errors per second.

`service_errors_resource_exhausted{resource_exhausted_cause="ConcurrentLimit", service_name="frontend"}`

\*\*

 ![image](https://us1.discourse-cdn.com/flex016/uploads/temporal/original/2X/1/13c9ee8adf82201c62dae60cf8a4973d7f8be932.png)  
\*\*

I am trying to understand what is causing this exactly and how I can configure an higher upper limit (if possible) in the dynamic config.

By reading the forum I was under the impression that I needed to increase `frontend.namespaceRPS` or `frontend.rps` but increasing them N fold does not have any impact so I am assuming I am turning the wrong knob here.

I tried finding `ConcurrentLimit` in the Temporal github repository but wasnt able to find it on the mainline so either I am running an older version (albeit we started our setup using recent public docker images & the helm charts) or I am overseeing something altogether.

Would love to get some help in resolving our problem!

@antonio.perez @tihomir @Donald_Forbes maybe you’d be able to share your wisdom with us?

Regards, Frank

---

<div class="post-metadata">

**Author:** ![frko](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/frko/32/4160_2.png) [@frko](https://community.temporal.io/u/frko)\
**Post date:** [August 25, 2024, 4:30pm UTC](https://community.temporal.io/t/frontend-resource-exhausted-concurrentlimit/13278/2 "2024-08-25T16:30:32Z")

</div>

Ok, I found the knob to turn `namespaceCount`. Not very intuitive but very effective nontheless.

---

<div class="post-metadata">

**Author:** ![Donald\_Forbes](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/donald_forbes/32/5557_2.png) [@Donald\_Forbes](https://community.temporal.io/u/Donald_Forbes)\
**Post date:** [August 26, 2024, 9:28am UTC](https://community.temporal.io/t/frontend-resource-exhausted-concurrentlimit/13278/3 "2024-08-26T09:28:45Z")

</div>

Good spot. Others that might be of interest are documented [here](https://docs.temporal.io/references/dynamic-configuration#service-level-rps-limits).