[MXS-6289] Change log level to warning for replay checksum errors - Jira

XML

Word

Printable

Sprint:
MXS-SPRINT-266, MXS-SPRINT-267
Bug Category:
Unexpected results
Release Note Summary:

Hide
Readwritesplit now logs a warning whenever the transaction replay fails due to a checksum mismatch. The log event can be customized with the `event_transaction_replay_failure_level` and `event_transaction_replay_failure_facility` settings and can be demoted to an info level message with `event_transaction_replay_failure_level=LOG_INFO`.

Show
Readwritesplit now logs a warning whenever the transaction replay fails due to a checksum mismatch. The log event can be customized with the `event_transaction_replay_failure_level` and `event_transaction_replay_failure_facility` settings and can be demoted to an info level message with `event_transaction_replay_failure_level=LOG_INFO`.

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.

Estimated:

0.25d

Remaining:

Logged:

Not Specified

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