-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: None
-
Component/s: Data Center, Enterprise, Pull Requests
Stash uses Hibernate L2 caching which can be configured in two modes: DISTRIBUTED and LOCAL. Stash versions up to and including 3.11 are hard wired to use DISTRIBUTED mode, but can be configured to use LOCAL Hibernate cache mode by modifying hidden properties.
In Stash Data Center versions prior to 3.11, the L2 Hibernate caches in LOCAL mode may intermittently become inconsistent. If affected by the consistency issue, it looks confusing (for example, Pull Request reviewers may appear different on different cluster nodes) but there is no possibility of data loss or other bad effects as a result of this. The actual data in the DB is fully consistent and any cluster node that is out of synch will reload the true state from the DB eventually, either the first time the PR is modified (for example) or when the data in the caches expire or get evicted.
- relates to
-
BSERV-7903 Bitbucket Data Center: Make LOCAL mode Hibernate cache the default
- Closed