[SERVER-40529] Ensure pinned user refresh happens outside of batch application Created: 08/Apr/19  Updated: 29/Oct/23  Resolved: 28/May/19

Status: Closed
Project: Core Server
Component/s: Admin, Replication, Security, Storage
Affects Version/s: None
Fix Version/s: 4.1.13

Type: Bug Priority: Major - P3
Reporter: Spencer Jackson Assignee: Jonathan Reams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-39611 AuthzLock may be released early if co... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Security 2019-04-22, Security 2019-05-06, Security 2019-05-20, Security 2019-06-03
Participants:
Linked BF Score: 6

 Description   

Application of oplog entries happens in parallel on secondaries, without having a stable point in time. We need to ensure that refresh doesn't occur during a period of instability.



 Comments   
Comment by Githook User [ 28/May/19 ]

Author:

{'name': 'Jonathan Reams', 'email': 'jbreams@mongodb.com', 'username': 'jbreams'}

Message: SERVER-40529 Refresh pinned users in background thread
Branch: master
https://github.com/mongodb/mongo/commit/c926e1a80996bb41997e2ec28b117cc3a1c25e7d

Comment by Githook User [ 28/May/19 ]

Author:

{'email': 'jbreams@mongodb.com', 'name': 'Jonathan Reams', 'username': 'jbreams'}

Message: SERVER-40529 Move locking out of external state
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/84eb9af923ad14903c0031759c47c38462ce68ad

Generated at Thu Feb 08 04:55:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.