debezium / debezium/dbz

Support for MySQL/MariaDB Galera Clusters [DBZ-4323]

Open
#533 0 comments 0 reactions 0 assignees View on GitHub
migrated-from-jira type/enhancement
Dominant language
HTML
Stars
6
Forks
8
Avg merge
2d 19h
Merged PRs (30d)
1

Description

Migrated from [DBZ-4323](https://issues.redhat.com/browse/DBZ-4323)

The request is specifically for Galera and MariaDB but it wouldn't hurt to potentially cover MySQL as well.

Galera provides for primary / primary database nodes. This means that each node is taking updates at the same time and synching those changes with the other primary nodes.

Typically CDC solutions monitor one of the nodes in the Galera cluster and take the transactions from that log. The question is can we support Galera MariaDB cluster so that in the event of that node failing, we will auto connect to one of the other primaries and take the events from there.

fyi, my investigation so far show's that Galera only has limited support for GTID's and doesn't use binlog as it has its own synchronisation processes.

Is there potentially a solution whereby we have each node in the cluster connected to Debezium and each instance works of its own binlog. I can't say I understand what goes on at this level of the DB though...

 

 

Contributor guide

Open the contributing guide

Research direction

Start by investigating how Galera synchronizes primary nodes, including its GTID and binlog limitations, and how Debezium currently consumes MySQL or MariaDB transaction logs. Define what failover between nodes and event continuity should mean, then validate whether a workable support approach exists for Galera clusters.

Written by the indexing model from the issue text.

Assessment

Tech stack
mariadb, mysql
Domain
databases, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.