Skip to content

Conversation

@dati18
Copy link
Contributor

@dati18 dati18 commented Jan 22, 2026

Bug: T414813

@tarrow
Copy link
Contributor

tarrow commented Jan 23, 2026

Seems like a likely cause of the issue. I was able to replicate it by
docker compose down -v
docker compose up -d
docker compose down
docker compose up -d

and saw in the logs:

mysql-replica-1  | 2026-01-23 16:37:34 16 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000002' at position 342, relay log './mysqld-relay-bin.000001' position: 4
mysql-replica-1  | 2026-01-23 16:37:34 15 [Note] Slave I/O thread: connected to master 'repl@mysql:3306',replication started in log 'mysql-bin.000002' at position 342
mysql-replica-1  | 2026-01-23 16:37:34 16 [ERROR] Slave SQL: Error 'Operation CREATE USER failed for 'repl'@'%'' on query. Default database: ''. Query: 'CREATE USER 'repl'@'%'', Gtid 0-1-186, Internal MariaDB error code: 1396
mysql-replica-1  | 2026-01-23 16:37:34 16 [Warning] Slave: Operation CREATE USER failed for 'repl'@'%' Error_code: 1396
mysql-replica-1  | 2026-01-23 16:37:34 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000002' position 342
mysql-replica-1  | 2026-01-23 16:37:34 16 [Note] Slave SQL thread exiting, replication stopped in log 'mysql-bin.000002' at position 342
mysql-replica-1  | 2026-01-23 16:37:34 16 [Note] master was mysql:3306

which no longer happens after checking out this PR

@tarrow tarrow merged commit 1a99610 into main Jan 23, 2026
9 checks passed
@tarrow tarrow deleted the fix-replica branch January 23, 2026 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants