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

Eliminate IMap-backed Cache in DriftCommentUpdateProcessor

XMLWordPrintable

    • 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.

      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.

            [BSERV-8844] Eliminate IMap-backed Cache in DriftCommentUpdateProcessor

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3395991 ] New: JAC Suggestion Workflow 3 [ 3618398 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: BSERV Suggestions Workflow [ 2686618 ] New: JAC Suggestion Workflow [ 3395991 ]
            Owen made changes -
            Workflow Original: Stash Workflow [ 1404264 ] New: BSERV Suggestions Workflow [ 2686618 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Brent P made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 291481 ]
            Brent P made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 291481 ]
            Cristan Szmajda (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Quality Review [ 10029 ] New: Closed [ 6 ]
            Cristan Szmajda (Inactive) made changes -
            Description Original: 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. New: 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.
            Cristan Szmajda (Inactive) made changes -
            Sprint Original: Enterprise 4.7-M4 [ 3215 ] New: Enterprise 4.7-M4, Enterprise 4.8-M1 [ 3215, 3238 ]
            Cristan Szmajda (Inactive) made changes -
            Description Original: In Stash Data Center and Bitbucket Data Center versions up to and including 4.7.0, 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. New: 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.
            Cristan Szmajda (Inactive) made changes -
            Summary Original: Back DriftCommentUpdateProcessor.failedAttemptsCache with something other than an IMap or a Spring Cache New: Eliminate IMap-backed Cache in DriftCommentUpdateProcessor

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

                Created:
                Updated:
                Resolved: