Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4079

Document cooperative monitoring conflict probability

    XMLWordPrintable

    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

          New Feature - A new feature of the product, which has yet to be developed. MXS-3234 Resolve cooperative monitoring deadlocks

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.