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

Log transaction contents on replay checksum mismatch

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Do
    • None
    • N/A
    • readwritesplit
    • None
    • MXS-SPRINT-220

    Description

      Whenever a transaction replay checksum mismatch occurs, it is sometimes difficult to find out exactly why the replay failed. In MaxScale 23.08, the checksums are done on a per-statement basis which makes it possible to identify the failing query. Making it possible to either log the whole transaction or at least the failing statement would make it easier reason about the source of the checksum mismatch.

      Attachments

        Activity

          markus makela markus makela added a comment -

          The log_info output in 23.08 already identifies the individual statement that caused the mismatch. The output also already shows whether there was a change in the result type or just in the checksum.

          markus makela markus makela added a comment - The log_info output in 23.08 already identifies the individual statement that caused the mismatch. The output also already shows whether there was a change in the result type or just in the checksum.

          People

            markus makela markus makela
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.