Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-8889

Replace Spring Cache and IAtomicLong in DefaultLicensedUserCountCache with TopicService and SchedulerService

    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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.

            [BSERV-8889] Replace Spring Cache and IAtomicLong in DefaultLicensedUserCountCache with TopicService and SchedulerService

            No work has yet been logged on this issue.

              cszmajda Cristan Szmajda (Inactive)
              cszmajda Cristan Szmajda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: