What is the best method for monitoring Group Replication conflict resolution?

Question

Options

• AThe PERFORMANCE_SCHEMA tables
• BThe SHOW PROCESSLIST command
• CThe INNODB Lock Monitor details
• DThe SHOW STATUS command
• EThe INFORMATION_SCHEMA tables

• A
  71% (41)
• B
  14% (8)
• C
  9% (5)
• D
  5% (3)
• E
  2% (1)

Explanation

PERFORMANCE_SCHEMA is the correct tool because it exposes dedicated tables - specifically replication_group_member_stats - that track conflict detection metrics like COUNT_TRANSACTIONS_IN_QUEUE, COUNT_CONFLICTS_DETECTED, and COUNT_TRANSACTIONS_REMOTE_APPLIED, giving real-time visibility into Group Replication's optimistic concurrency control process. SHOW PROCESSLIST (B) only shows active thread states, not replication-specific conflict statistics. InnoDB Lock Monitor (C) covers row-level locking within a single node, not the distributed certification-based conflict detection that Group Replication uses. SHOW STATUS (D) provides general server counters but lacks Group Replication-specific conflict metrics. INFORMATION_SCHEMA (E) holds metadata about schema objects and plugins, not runtime replication performance data.

Memory tip: Think "Performance Schema = Precise Stats" - whenever a question asks about monitoring or diagnosing replication internals in MySQL, PERFORMANCE_SCHEMA is almost always the answer because it was purpose-built for that observability layer.

No community discussion yet for this question.