diff options
author | Shreyas Kalyan <shreyas.kalyan@10gen.com> | 2020-03-31 18:58:19 -0700 |
---|---|---|
committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2020-04-01 18:59:40 +0000 |
commit | c51dbb8eb4d81e6b70c542065eb66b9e36082d38 (patch) | |
tree | c5068a799df0504a96cc6ff4ffa44ee6401bf333 | |
parent | 304a4e70c21b31cce2201f532a538dd8f0b9e677 (diff) | |
download | mongo-c51dbb8eb4d81e6b70c542065eb66b9e36082d38.tar.gz |
SERVER-46834 Use monotonic time in UserCacheInvalidator
-rw-r--r-- | src/mongo/db/auth/user_cache_invalidator_job.cpp | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/src/mongo/db/auth/user_cache_invalidator_job.cpp b/src/mongo/db/auth/user_cache_invalidator_job.cpp index 526f97500b0..682f288933f 100644 --- a/src/mongo/db/auth/user_cache_invalidator_job.cpp +++ b/src/mongo/db/auth/user_cache_invalidator_job.cpp @@ -149,7 +149,10 @@ void UserCacheInvalidator::run() { Date_t sleepUntil = lastInvalidationTime + Seconds(userCacheInvalidationIntervalSecs.load()); Date_t now = Date_t::now(); - while (now < sleepUntil) { + + // The second clause in the if statement is if we've jumped back in time due to an NTP + // sync; we should always trigger a cache refresh in that case. + while (now < sleepUntil && now >= lastInvalidationTime) { MONGO_IDLE_THREAD_BLOCK; invalidationIntervalChangedCondition.wait_until(lock, sleepUntil.toSystemTimePoint()); sleepUntil = lastInvalidationTime + Seconds(userCacheInvalidationIntervalSecs.load()); |