-
Suggestion
-
Resolution: Fixed
-
None
The DefaultLicensedUserCountCache in Stash and Bitbucket DC versions up to and including 4.7 uses a Spring Cache (backed by a Hazelcast IMap) and a Hazelcast IAtomicLong internally. In some scenarios, this can cause the licensed user count computation on one cluster node to block waiting for another cluster node, which in the event of OS or JVM issues (e.g., excessive GC pauses) may be slow or unresponsive.
In Bitbucket Data Center 4.8.0 and higher, this has been replaced with the SchedulerService and TopicService which do not block on other cluster nodes even if they are affected by OS or JVM issues.