We are running our App Pools in web garden mode. IE: App Pool Max Worker Processes is greater than 1.
We been noticing that when the App Pool allows more than 1 Worker Process, we tend to get a “No Key Found in Dictionary” error.
However, when we minimize it down to 1 Worker, it does not present the error, however the site would lack responsive performance.
Has there been such an issue reported? Or is there anything we may be missing?
We are connecting to our Analysis Cube using Accelerator proxy approach within our dotnet site.
Thank you for posting your question.
This is a known issue, and it is related to how the Accelerator processes the received inquiries. Some inquiries require the data to be stored locally within the instance that served the previous request. Being redirected by the load balancer to another instance, the request can not be served since the current instance does not contain the required data.
Therefore, the current Accelerator data loading approach is not compatible with load balancing.
With that in mind, we would suggest refraining from scaling your application in a way that more than one Accelerator instance is used. Instead, it’d be better to only use one instance which processes all the requests. Alternatively, you could also scale your main application but have Accelerator as a separate non-scaled app.
Please let us know if there is anything else we can help you with.