I am experiencing a really bizarre downside with userstore_tokenperm clerk lately.
Now we have an surroundings with some databases in contained mode executing in model SQL Server 2017. Anyway i am going through this downside for the reason that SQL Server 2016.
At a sure second this cache begins to develop at a price of 6GB by day. When this ocurr we now have to do a failover and restart the principal node of AG.
Run DBCC FREESYSTEMCACHE (‘TokenAndPermUserStore’) doesn’t clear the cache. We’re contemplating to make use of the hint flags 4621 as recommended by microsoft to keep away from this reminiscence stress, however i need to know if somebody has a tip to assist me to know this habits. This looks as if a reminiscence leak, as a result of even operating DBCC FREESYSTEMCACHE the objects aren’t launched from reminiscence.
Now we have round to 70 customers in contained mode on this server and when the cache begins to develop it develop till starve the server for reminiscence.
I attempted to search out out what sort of class of token is current and the more serious occasion have solely this entrys.
In sys.dm_os_memory_clerks we already confronted greater than 30GB of consumption
Somebody please will help with some troubleshooting trace and even with an expertise about this sort of downside.