-
Suggestion
-
Resolution: Fixed
Spring Cache's in Stash and Bitbucket DC versions up to and including 4.7.0 are backed by Hazelcast IMap's internally. In some scenarios, this can cause cache accesses from 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 hybrid-mode atlassian-cache Cache's which do not block on other cluster nodes even if they are affected by OS or JVM issues.
- relates to
-
BSERV-8844 Eliminate IMap-backed Cache in DriftCommentUpdateProcessor
- Closed
- was cloned as
-
BSERV-9041 Don't do blocking remote cluster calls from CachingPermissionGraphFactory
- Closed
Form Name |
---|
[BSERV-8890] Back Spring caches with hybrid atlassian-cache Caches instead of Hazelcast (IMap-backed) caches
Workflow | Original: JAC Suggestion Workflow [ 3393494 ] | New: JAC Suggestion Workflow 3 [ 3620303 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: BSERV Suggestions Workflow [ 2683823 ] | New: JAC Suggestion Workflow [ 3393494 ] |
Workflow | Original: Stash Workflow [ 1423721 ] | New: BSERV Suggestions Workflow [ 2683823 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Remote Link | Original: This issue links to "Page (Extranet)" [ 291536 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 291536 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Quality Review [ 10029 ] | New: Closed [ 6 ] |
Remote Link |
New:
This issue links to "Stash › BSERVDEV-10717-Stash-stops-triggering-bamboo-build › |
Remote Link |
New:
This issue links to "Stash › Pull Request Build › |
Status | Original: To be reviewed [ 10026 ] | New: Quality Review [ 10029 ] |
Description |
Original:
Spring {{Cache}}'s in Stash and Bitbucket DC versions up to and including 4.7.0 are backed by a Hazelcast {{IMap}} internally. In some scenarios, this can cause cache accesses from 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 hybrid-mode atlassian-cache {{Cache}}'s which do not block on other cluster nodes even if they are affected by OS or JVM issues. |
New:
Spring {{Cache}}'s in Stash and Bitbucket DC versions up to and including 4.7.0 are backed by Hazelcast {{IMap}}'s internally. In some scenarios, this can cause cache accesses from 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 hybrid-mode atlassian-cache {{Cache}}'s which do not block on other cluster nodes even if they are affected by OS or JVM issues. |