You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Kristof degrave (@kristofdegrave) thanks for the suggestion! For now, we’d prefer to keep MaxParallelSecretResolutions as an implementation detail unless there’s a concrete need to tune it. Is the current limit too low or too high for your scenario? If it’s causing issues, we can revisit exposing it as configuration.
Thx for thr quick response. We are currently investigating IOExceptions where the connection was closed by the remote host. They seem to appear when we have a higher load.
This is still in investigation. But it might becaused due to many concurrent request to the keyvault. We aren't hitting ratelimits on Azure, otherwise we would get 429, but maybe the firewall is having issue processing the load.
Thx for thr quick response. We are currently investigating IOExceptions where the connection was closed by the remote host. They seem to appear when we have a higher load.
This is still in investigation. But it might becaused due to many concurrent request to the keyvault. We aren't hitting ratelimits on Azure, otherwise we would get 429, but maybe the firewall is having issue processing the load.
Thanks for the additional context. The current implementation allows up to 16 concurrent secret resolutions per provider during configuration load or refresh.
Could you share how many Key Vault references your application resolves? This will help us better understand the scenario. We’ll discuss making the parallel resolution limit configurable with the team and follow up here.
Activity
linglingye001 commentedon Aug 27, 2026
Hi Kristof degrave (@kristofdegrave) thanks for the suggestion! For now, we’d prefer to keep
MaxParallelSecretResolutionsas an implementation detail unless there’s a concrete need to tune it. Is the current limit too low or too high for your scenario? If it’s causing issues, we can revisit exposing it as configuration.kristofdegrave commentedon Aug 27, 2026
Hi linglingye001,
Thx for thr quick response. We are currently investigating IOExceptions where the connection was closed by the remote host. They seem to appear when we have a higher load.
This is still in investigation. But it might becaused due to many concurrent request to the keyvault. We aren't hitting ratelimits on Azure, otherwise we would get 429, but maybe the firewall is having issue processing the load.
linglingye001 commentedon Aug 27, 2026
Thanks for the additional context. The current implementation allows up to 16 concurrent secret resolutions per provider during configuration load or refresh.
Could you share how many Key Vault references your application resolves? This will help us better understand the scenario. We’ll discuss making the parallel resolution limit configurable with the team and follow up here.