Info

The ldap_user_cache_refresher.js test has seen sporadic failures for quite some time now. Since this test uses a locally-running mock server, these failures cannot be explained by external LDAP server slowness. The test currently enforces that it must see cache invalidations within a configurable ldapUserCacheStalenessInterval seconds after the last successful refresh. This sometimes fails because in the worst case scenario, a failed refresh completes at just under ldapUserCacheStalenessInterval seconds. As a result, the server waits another ldapUserCacheRefreshInterval seconds before trying another refresh and only invalidates the cache if that refresh also fails. To temporarily fix this and make the build green, we should relax this interval to be ldapUserCacheStalenessInterval + ldapUserCacheRefreshInterval. Eventually, we should update the behavior of the cache so that it actually performs the invalidation when the ldapUserCacheStalenessInterval is reached.

Top User Comments

xgen-internal-githook commented on Fri, 29 Apr 2022 13:22:23 +0000: Author: {'name': 'Varun Ravichandran', 'email': 'varun.ravichandran@mongodb.com', 'username': 'varunravi98'} Message: SERVER-65507: Relax LDAP user cache refresher test staleness timeouts (cherry picked from commit 3ab0e06aa4452c0d16cc1e7b98a88f447c254404) Branch: v6.0 https://github.com/10gen/mongo-enterprise-modules/commit/936a44ac1331401ee95df8fbb1b785a74efa3097 xgen-internal-githook commented on Wed, 20 Apr 2022 17:46:08 +0000: Author: {'name': 'Varun Ravichandran', 'email': 'varun.ravichandran@mongodb.com', 'username': 'varunravi98'} Message: SERVER-65507: Relax LDAP user cache refresher test staleness timeouts Branch: master https://github.com/10gen/mongo-enterprise-modules/commit/3ab0e06aa4452c0d16cc1e7b98a88f447c254404

Steps to Reproduce