Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.5.20
-
Component/s: Documentation
-
Labels:None
-
Sprint:MXS-SPRINT-156
Description
The documentation currently is not clear enough about how the feature works and why complex conflict resolution strategies are not needed. Explaning that the probability of a conflict is small due to the randomness involved in the lock acquisition goes a long way to help the users understand why MaxScale behaves the way it does.
Attachments
Issue Links
- relates to
-
MXS-3234 Resolve cooperative monitoring deadlocks
-
- Closed
-