-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
None
-
None
Updating Digital Media child order pulled the trigger search_medium_format_update which sent the following message:
{ "_table" : "medium_format", "_operation" : "update", "id" : 12 }
This message ended in the queue search.failed with the following exception:
Traceback (most recent call last): File "sir/amqp/handler.py", line 120, in wrapper f(self=self, parsed_message=parsed_message) File "sir/amqp/handler.py", line 262, in index_callback self._index_by_pk(parsed_message) File "sir/amqp/handler.py", line 361, in _index_by_pk self._index_data(core_name, ids, extra_data) File "sir/amqp/handler.py", line 331, in _index_data raise INDEX_LIMIT_EXCEEDED(core_name, total_ids, extra_data) INDEX_LIMIT_EXCEEDED: Index limit exceeded. Entity: recording, Total Rows: 4712506, Extra Data: {'path': 'tracks.medium.format', 'table_name': u'medium_format', 'select_query': 'SELECT recording_1.id AS recording_1_id FROM musicbrainz.recording AS recording_1 JOIN musicbrainz.track AS track_1 ON recording_1.id = track_1.recording JOIN musicbrainz.medium AS medium_1 ON medium_1.id = track_1.medium JOIN musicbrainz.medium_format ON musicbrainz.medium_format.id = medium_1.format WHERE musicbrainz.medium_format.id = :id_1'}
Issue is twofold:
1. Updating child_order column in the medium_format should not pull the trigger as only name column is actually used for search index;
2. Even though updating the name of a medium format that has above 2M occurrences is uncommon, it should probably not fail.
- has related issue
-
SEARCH-669 Indexer hanging on type description update
- Closed