MySQL High Availability with InnoDB Cluster ELS — Lesson 2: Cluster Creation, Member Management, Recovery, Consistency, and Quorum

Learning Objectives

• Describe prerequisites, ownership, dependencies, and failure conditions for cluster creation, member management, recovery, consistency, and quorum.
• Construct the course-specific workflow while recording evidence at each material checkpoint.
• Evaluate the solution against security, control, reliability, performance, and support criteria.

Detailed Topics

• Cluster Creation
• Member Management
• Recovery
• Consistency
• Quorum
• ownership, prerequisites, data, and acceptance criteria for cluster creation, member management, recovery, consistency, and quorum
• security, control, integration, performance, recovery, and support implications

Instructor Demonstration

Demonstrate cluster creation, member management, recovery, consistency, and quorum within a MySQL InnoDB Cluster designed to preserve service during member failure, maintenance, and controlled recovery. Use representative data and capture member state, replication status so another practitioner can verify the result.

Hands-On Exercise

Complete a controlled MySQL High Availability with InnoDB Cluster ELS activity focused on cluster creation, member management, recovery, consistency, and quorum. Introduce a realistic case of lost quorum, isolate its cause, apply a reversible correction, and rerun the acceptance checks.

1. Record the requirement, environment, identities, dependencies, data, controls, and expected result.
2. Perform the workflow and capture course-specific evidence before and after each material change.
3. Test normal, boundary, failure, security, reconciliation, recovery, and operational conditions.
4. Document the root cause, correction, rollback, owner, support action, and next improvement priority.

Scenario Analysis

• Establish current state, desired state, constraints, and acceptable service impact.
• Compare alternative implementation or diagnostic approaches and their rollback consequences.
• Document the decision, evidence, exception, corrective action, and measurable improvement target.

Troubleshooting Guidance

When cluster creation, member management, recovery, consistency, and quorum does not produce the expected result, confirm scope, effective dates, identities, data context, dependencies, and recent changes. Review the most relevant member state, replication status before editing configuration. Test one reversible hypothesis at a time, verify recovery, and confirm that the fix does not create lost quorum elsewhere.

Validation Checklist

• Prerequisites, ownership, data context, settings, and expected outcomes are documented.
• The result is reproducible and supported by member state, replication status.
• Security, controls, data quality, integration, performance, recovery, and support conditions are reviewed.
• Exceptions, corrective action, rollback, approvals, monitoring, and handover are recorded.

Lesson Outcome

Learners can apply Cluster Creation, Member Management, Recovery, Consistency, and Quorum in a realistic MySQL High Availability with InnoDB Cluster ELS situation and defend the result with course-specific evidence.