[SERVER-55172] Add and use a fail point to wait for user cache invalidation Created: 11/Mar/21 Updated: 29/Oct/23 Resolved: 22/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Security 2021-03-22 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 14 | ||||||||
| Description |
|
Currently, if we want to wait for a cached user to be invalidated, we have to set the authLocalGetUser fail point. This in of itself does not guarantee that we experience cache invalidation because external delays may be greater than the delay associated with that fail point. We should have a separate fail point that explicitly waits for cache invalidation. Then we can use that fail point with user-cache-invalidation.js. |
| Comments |
| Comment by Githook User [ 22/Mar/21 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |