MySQL to Elasticsearch
real-time replication
TwinCommit replicates MySQL to Elasticsearch in real time by reading the MySQL transaction log and applying every committed change exactly once and in commit order. Use it to keep Elasticsearch search indexes current with MySQL, with no triggers or capture tables on the source.
MySQL
log reader
commit-ordered · exactly-once
Elasticsearch
native writer
How capture works on MySQL
TwinCommit connects as a replica, reads the row-based binary log and tracks position by GTID, so failovers and replica promotions are seamless.
Prerequisites
- ✓binlog_format = ROW and binlog_row_image = FULL
- ✓GTID mode recommended
- ✓REPLICATION SLAVE and REPLICATION CLIENT grants
How apply works on Elasticsearch
Changes are sent through the _bulk API with the document ID set to the primary key and external versioning derived from the log position, so late or replayed writes can never overwrite newer data.
Requirements
- ✓An index template or mapping per table
- ✓API key with index and write privileges
- ✓TLS endpoint
Setup
Set up MySQL → Elasticsearch in four steps
- 1
Prepare MySQL
Run twincommit check. It verifies binlog_format = row and binlog_row_image = full and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at Elasticsearch
Add a target block for Elasticsearch. TwinCommit can generate target DDL with twincommit ddl -apply.
- 3
Snapshot
twincommit snapshot copies each table under a brief share lock and records the exact log position.
- 4
Stream
twincommit run streams every committed change from that position, exactly once and in commit order.
source:
type: mysql
dsn: ${SOURCE_DSN}
server_id: 4201
target:
type: elasticsearch
url: https://search.internal:9200
api_key: ${ES_API_KEY}
index_template: "{schema}-{table}"
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]MySQL to Elasticsearch replication FAQ
How does TwinCommit replicate MySQL to Elasticsearch?
+
TwinCommit reads changes from the MySQL transaction log, buffers them per transaction, and applies each committed transaction to Elasticsearch in commit order. Changes are sent through the _bulk API with the document ID set to the primary key and external versioning derived from the log position, so late or replayed writes can never overwrite newer data.
Does MySQL to Elasticsearch replication need triggers or capture tables?
+
No. TwinCommit reads the MySQL log directly and creates no objects in the source database.
Is MySQL to Elasticsearch replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Elasticsearch transaction as the data, so a crash or restart never loses or duplicates a transaction.
What MySQL versions are supported?
+
MySQL 5.7, 8.0, 8.4, 9.x · Amazon RDS & Aurora MySQL · Azure Database for MySQL · Cloud SQL.
Use cases for this route
Related replication routes
Stream MySQL to Elasticsearch today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.