How to import edit/editor database dumps into a replicated database on musicbrainz-docker?

[Jim_DeLaHunt]

@Jim_DeLaHunt

I seem to have editor and edit* tables which I can use, now.

Ah, not so fast!

Shortly after I imported these tables, I noticed that my replication was broken. As discussed in the topic, Replication error: “current row … contains a different value … than the replication packet suggests it should have”, it seems that:

@Bitmap

MBImport.pl updates the replication_control table by default. So importing those would have rolled back the current_replication_sequence in that table. Now it’s trying to apply packets that have already been applied.

That meant that the replication jobs failed.

Apparently, it is advisable to give the --noupdate-replication-control to MBImport.pl when importing editor and edit* tables, like so:

% docker compose run --rm musicbrainz bash -c 'carton exec -- 
admin/MBImport.pl --noupdate-replication-control /.../mbdump-edit.tar.bz2' 

(Line breaks added for legibility.)

That topic also had a way to repair the replication_control table:

@Bitmap

don’t want to re-import everything, but also don’t mind hacking a Perl file, a potential fast workaround may be to edit admin/replication/ProcessReplicationChanges inside the container, and initialize $ignore_conflicts to 1. That will just cause it to ignore any conflicting statements until you’re able to catch up to the correct packet again.

That worked for me. I changed $ignore_conflicts to 1. Then I ran a few replication cycles manually, which despite intermittent failures caught me part-way up. I restored $ignore_conflicts to 0. Further manual replication cycles continued to work.