-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CDS client doesn't work on kubernetes #93
Comments
Thanks, |
@BetimBeja all the Execute commands run though our longstanding API interface which the CdsServiceClient uses. Can you tell me the instance/orgid that your connecting to so we can look at the other end of this to see where these requests went? And or can you provide the verbose logs for there requests? you can get them out of the in memory logger in the client and write them to a file that you can get at after the run if you need to . Thanks. |
Sorry about the delay getting back to you here.. there was a bit of a long discussion around this. tagging @JimDaly here. |
Thank you @MattB-msft, I am sorry I wasn't able to provide any more logs, I have been busy lately and have had very little time for this. |
@BetimBeja as a heads up... we discovered and fixed number of issues that could have been impacting this in the ServiceClient, and a rather big issue with the way MSAL deals with cache locking we are working though actively. However many of the updates we have recently provided may substantially improve the perf on Kubernetes, |
@MattB-msft I will try to replicate the test this weekend! I will email you the details of the test! |
@BetimBeja were you successfull? |
@MattB-msft I sent the email with subject "Stress-Test Azure Function v3 DV ServiceClient" to [email protected] as in your github profile, I will try to test again since a lot of time has passed. |
Ah, sorry about that. Will check to see if I still have it . Thanks, |
Just sent an update 😄 |
We tried using some two different approaches:
static CdsServiceClient client = ...
using(var clone = client.Clone()) { ... cds business ... }
using(var client = new CdsServiceClient(...))
Both attempts choked up the cluster pretty quickly (load test = hitting cluster with 100 threads per second), after few seconds it was choked up.
There is somehow similar issue described here - dotnet/wcf#3344
However in our case it doesn't look like thread congestion (the measured numbers were not that high - more like a leakage of some sort). It does not reproduce on windows.
Sample with full repro here:
src.zip
The text was updated successfully, but these errors were encountered: