JoshDi

Thank you, yvanzo. This issue can be replicated many hours after the replication is complete. I even deleted my annotation index table and reindexed it yesterday. The check index matches...

@nikosmichas have you figured out how to modify the local/compose/memory-settings.yml file to accomplish this? I believe this is working for me ``` version: '3.1' # Description: Customize memory settings services:...

using the values above cause my slave server to sometimes timeout for MQ queue or checking the index count vs the DB. I have removed these redis-server modifications and I...

Correction, the error I am getting is below and started to occur after upgrading to ubuntu x64 22.04.1 LTS. `OCI runtime exec failed: exec failed: unable to start container process:...

> 128GB of RAM is probably the exception and we should not hardcode this into the repo. Also most of those values vary by the amount of RAM you have...

> > **work_mem** > > We set it to `128MB` for `musicbrainz.org`, we should probably set it in MusicBrainz Docker too. > > > **maintenance_work_mem** > > **effective_cache_size** > >...

this should be fixed in one of the last few releases of musicbrainz-docker. Replication packets for a slave server only take a few minutes now to process the index update...

If I add this line below after line 5 of /lib/udev/rules.d/69-bcache.rules, the errors go away and when I reboot the bcache is correctly mounted/registered. ACTION=="change", GOTO="bcache_end" Is there any risk...

@myopenflixr have you tried using the search indexing recently? There were some commits that speed up the indexing by like 100x. It allowed me to run search indexing hourly and...

Thats a powerful enough server to run replication every hour. Look at the config files below - update those first and then run the following steps. Your memory-settings.yml looks good....