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

Change log level to warning for replay checksum errors

    XMLWordPrintable

Details

    • MXS-SPRINT-266, MXS-SPRINT-267

    Description

      When a transaction is replayed after a disconnect, but returns a different result than expected the
      client will receive this error:

      ERROR 1927 (70100): Transaction checksum mismatch encountered when replaying transaction.

      On the MaxScale side the corresponding message

      Checksum mismatch, transaction replay failed. Closing connection.

      is only written if log_info is enabled though, so when using default settings it will not occur in the Maxscale error log.

      As an error is sent to the client it would probably make more sense to also have it logger on error, or at least warning, level on the Maxscale side.

      Attachments

        Activity

          People

            markus makela markus makela
            hholzgra Hartmut Holzgraefe
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.