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

Large load heavy import causes nodes to leave cluster

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not a Bug
    • Affects Version/s: None
    • Fix Version/s: N/A
    • Component/s: maxadmin
    • Labels:
      None

      Description

      Is it correct to assume that maxscale periodically checks the 'mysql' db for monitoring purposes?
      On large imports it seems to take too long to connect (or the table is locked) and the check runs into a timeout.

      This leads to following action:
      every node that cant be checked gets removed from the cluster.
      Log: Readwritesplit service can't locate the master. Client sessions will be closed.

      The only way to get around it is to up the timeout values of the instances monitor settings.

      Is this intended behaviour? Should we do something other than tweaking the timeout values?

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            petkro Peter Kröll
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration