[MDEV-9902] Replication filters does not saved between instance restarts Created: 2016-04-12  Updated: 2016-04-19  Resolved: 2016-04-19

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.0.24
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Den Hrybkov Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: replication
Environment:

Oracle Linux Server release 6.7


 Description   

Hello,

I have using MariaDB multi-source replication feature together with replication filters which are different for each slave set. When MariaDB instance was restarted the filter variables are lost and all slaves were in inoperable state until filters will be enabled again. I have tried to add the configuration file values like:
slave1.replicate-wild-do-table=db_name1.table1
slave2.replicate-wild-do-table=db_name2.table2
similarly to described in your documentation but unfortunately it did not work.

I have studied your docs a lot but didn't find appropriate answer regarding described behavior. In my opinion replication filters settings should be saved somewhere (file,table) or described in configuration but I could be wrong.

Please advice.

Thank you.

 Comments   
Comment by Elena Stepanova [ 2016-04-18 ]

den,
What exactly do you mean by "it did not work"? Are the values that you set not shown in the slave status, or do the filters not work as you expect them too?
Please attach your cnf file(s) from the slave (with the variables that you added), and paste the output of show all slaves status.
Thanks.

Comment by Den Hrybkov [ 2016-04-19 ]

Unfortunately I can't reproduce this issue now. I'm 100% sure that it was present before but unfortunately didn't saved any logs.
The only thing that was changed during last time - I performed the reset one of masters to change the gtid-domain-id, unlike another master
which was reset before previously, it had the default one (0-0-xxx).

Please close this issue, I'll update it if I've got it again but this time will collect all needed info.

Thank you.

Comment by Elena Stepanova [ 2016-04-19 ]

Thanks for the update. Please indeed comment if you observe the problem again, and we'll re-open the report.

Generated at Thu Feb 08 07:38:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.