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

Readwritesplit logs wrong warning when replication lag is not available

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.5.14
    • Fix Version/s: 2.5.15
    • Component/s: readwritesplit
    • Labels:
      None

      Description

      The following message is logged if the replication lag is not measurable.

      warning: (1) (My-Service) Replication lag of 'server2' is -1 seconds, which is above the configured limit 10s. 'server2' is excluded from query routing.

      The correct message to log would be that the reason why the server is removed from routing is not the lag itself but the inability to measure it.

        Attachments

          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.