[MCOL-2206] Replication of mysql schema - Replication stops when a user is altered Created: 2019-03-01  Updated: 2023-10-26  Resolved: 2019-04-26

Status: Closed
Project: MariaDB ColumnStore
Component/s: ?
Affects Version/s: 1.2.2
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: David Hill (Inactive) Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

2 UM, 2 PM system with local query



 Description   

Reported by a customer

2 UM, 2 PM system with local query. Replication stops when a user is altered from UM1. A simple grant to a user on UM1 will stop replication to the other servers with these errors:

Slave_IO_Running: Yes
Slave_SQL_Running: No
Last_Error: Error 'Can't find any matching row in the user table' on query. Default database: ''. Query: 'grant select on test.dairy_comm_pred to ro_dairy'

First, this user, along with others, are intentionally not on the other servers of UM2, PM1 and PM2 as they do not need to access anything from there. Second, the rsync command for replication also excludes the mysql dir, so shouldn't this also be skipped over when replicating?

rsync -vopgr -e ssh --exclude=mysql/ --exclude=test/ --exclude=infinidb_vtable/ --exclude=infinidb_querystats/ --exclude=calpontsys/ --include=/ --include=/* --exclude=* $INSTALLDIR/mysql/db/ $USERNAME@$SERVER:$INSTALLDIR/mysql/db/

I believe this could be set as a variable in Replicate_Ignore_DB=mysql



 Comments   
Comment by Andrew Hutchings (Inactive) [ 2019-04-26 ]

This is to be expected with MariaDB replication. Either skip the events when this happens or:

https://mariadb.com/kb/en/library/replication-filters/

Generated at Thu Feb 08 02:34:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.