aspnet/DataProtection

[1.x] KeyRingProvider initialization causes thread pool starvation when server starts under load

natemcmaster opened this issue · 4 comments

natemcmaster commented

Consider back-porting #241 to 1.x.

cref original issue #233 (fixed for 2.0)

brockallen commented

Sorry, repeating from the PR:

Ok, thanks. One my my customers was on the original issue/thread here, and from their perspective data protection is in essence broken and unusable until this fix makes it into a release (as I'd imagine anyone else trying to use data protection, especially in azure). They aren't really in a position to move to 2.0 anytime soon.

Tratcher commented

Looks like there's a trivial workaround, does it have any catches?

brockallen commented

Looks like there's a trivial workaround, does it have any catches?

Well, I can only say that my customer was close to dropping ASP.NET Core support (and going back to the ancient days of Katana even!) given that this felt like a critical issue "out of the box". Perhaps fixing perception is more important?

aspnet-hello commented

This issue was moved to dotnet/aspnetcore#2510