Disable user/group caching when requested
Description
Problem/Justification
None
Impact
None
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Show:
Zack September 10, 2019 at 11:29 PM
Confirmed fixed in TrueNAS 11.2-U6.
Testing notes:
Followed the clearly written acceptance criteria, going back and forth between AD and LDAP. Used the dataset permissions editor user/group as the GUI dropdown to test.
Bug Clerk July 29, 2019 at 11:28 AM
Caleb July 24, 2019 at 10:55 PM
Attaching debug from the system NOTE this is after I had already restarted django and disabled caching.
Complete
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Andrew WalkerReporter
CalebLabels
Support Ticket
DPK-973-23052
Components
Fix versions
Affects versions
Priority
HighMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created July 24, 2019 at 4:10 PM
Updated July 1, 2022 at 4:34 PM
Resolved September 11, 2019 at 10:50 AM
Customer is using AD and had caching of users and groups turned on. This particular AD environment had 330k+ user objects in AD and probably even more group objects.
Either way, the AD environment was quite large. the freenascache.py file was being run to try and cache all users and groups which locked a django thread. This thread never returned and held it indefinitely. The customer then started to make more changes in the webUI (i.e add SMB shares, add NFS shares etc etc) and since those dialog boxes have UI elements that allow you to insert a username/groupname, freenascache.py was being called again.
I'm attaching gdb about of all django threads showing what they were locked on and I'm also attaching procstat output.
When this scenario occurs, the API and the webUI become non-responsive.