wsrep_debug only logs DDL information on originating node

Description

When wsrep_debug is enabled, Galera Cluster logs more verbose information to the error log.

For example, when DDL is executed on a particular node, the node logs some information like this:

1 2 3 4 5 6 160222 15:30:44 [Note] WSREP: TO BEGIN: -1, 0 : ALTER ONLINE TABLE test_table DROP KEY str 160222 15:30:44 [Note] WSREP: TO BEGIN: 1100033, 2 160222 15:30:44 [Note] WSREP: TO END: 1100033, 2 : ALTER ONLINE TABLE test_table DROP KEY str 160222 15:30:44 [Note] WSREP: Set WSREPXid for InnoDB: fbeb045d-b94f-11e5-8504-4ae80b892690:1100033 160222 15:30:44 [Note] WSREP: TO END: 1100033, update seqno 160222 15:30:44 [Note] WSREP: TO END: 1100033

However, when wsrep_OSU_method is set to TOI and the DDL command is replicated to the other nodes in the cluster, those other nodes do not log anything about the DDL to their error logs, even if wsrep_debug is enabled on those other nodes.

It would be useful to see some kind of information in the error logs about replicated DDL when wsrep_debug is ON. The main use case is when trying to track exactly what DDL is being replicated to other nodes.

Environment

None

Status

Assignee

Nirbhay Choubey

Reporter

Geoff Montee

Labels

External issue ID

None

External issue ID

None

Components

Affects versions

10.0.23-galera

Priority

Major