In Stash Data Center and Bitbucket Data Center versions up to and including 4.7, the comment drift processor uses a Spring Cache (DriftCommentUpdateProcessor.failedAttemptsCache) backed by a Hazelcast IMap to record a count of failed comment drift attempts cluster-wide. In Bitbucket Data Center 4.8.0 and higher, this IMap-backed Cache has been eliminated, and the count is maintained in the DB record directly. This eliminates some synchronous remote calls between cluster nodes, improving reliability and performance in situations where a remote cluster node is slow or unresponsive.