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

Type: Suggestion
Resolution: Fixed
Fix Version/s: 4.8.0
Component/s: Data Center, Enterprise
Labels:
None

Feedback Policy:

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.

is related to

BSERV-8890 Back Spring caches with hybrid atlassian-cache Caches instead of Hazelcast (IMap-backed) caches

Closed

Form Name

There are no comments yet on this issue.

Assignee:: Cristan Szmajda (Inactive)

Reporter:: Cristan Szmajda (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 02/Jun/2016 4:01 AM

Updated:: 19/Sep/2019 5:49 AM

Resolved:: 27/Jun/2016 5:26 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates

Backbone Issue Sync