You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that during the nightly replication cron that the annotations index table slips from the db. The only way to resolve this is to delete the index for this table and rebuild from scratch. However, the next time the replication cron runs, the index for annotations is off again. Is this expected?
root@HTPC-Xeon:/storage/musicbrainz-docker/admin# ./check-search-indexes all
CORE STATUS INDEX DB
editor OK 0 /0
instrument OK 987 /987
series OK 10893 /10893
place OK 39509 /39509
event OK 40295 /40295
tag OK 94581 /94581
area OK 118047 /118047
label OK 172950 /172950
cdstub OK 293492 /293492
annotation -- 341650 /341606
work OK 1259182 /1259182
artist OK 1592742 /1592742
release-group OK 1907204 /1907204
release OK 2413385 /2413385
url OK 6296267 /6296267
recording OK 21730554 /21730554
The text was updated successfully, but these errors were encountered:
Search indexer skip annotations that contain control characters that may still be added due to the bug MBS-10416 in MusicBrainz Server, that would explain search indexes missing a few annotations. But in your case, there seems to be more entries in search indexes than annotations in the database. I am not sure how to explain this. Please note that requests sent to Solr are asynchronous. Deletion is not taking effect immediately, you might want to wait a few seconds before checking indexes again.
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 for all tables then including annotations. However, when checking this afternoon after my replication cron ran last night, annotation index count is off
I've noticed that during the nightly replication cron that the annotations index table slips from the db. The only way to resolve this is to delete the index for this table and rebuild from scratch. However, the next time the replication cron runs, the index for annotations is off again. Is this expected?
The text was updated successfully, but these errors were encountered: