Bug 39194 - Add a cronjob to report record IDs that have failed to be indexed (Elasticsearch - ES)
Summary: Add a cronjob to report record IDs that have failed to be indexed (Elasticsea...
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Elasticsearch (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Aleisha Amohia
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-24 22:46 UTC by Aleisha Amohia
Modified: 2025-12-15 19:58 UTC (History)
0 users

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aleisha Amohia 2025-02-24 22:46:37 UTC
If a record is catalogued but does not successfully get indexed by Elasticsearch, it is called 'missing'. A summary of this can be seen on the Koha About page, under the System information tab. A user may see something like this:

Records are not indexed in Elasticsearch 
Warning 	27 record(s) missing on a total of 1807413 in index koha_kohadev_biblios. 

However we can't see from this view which record(s) are missing from the indices. It would be great to have a list of the IDs that are in the Koha database, but not in the ES indices.

Probably need this to be a cronjob as with large catalogues, a request like that would crash Koha. So would also want to report the time the script was run last to the page as well.
Comment 1 Aleisha Amohia 2025-03-10 02:06:21 UTC
Forgot about the /misc/maintenance/compare_es_to_db.pl script, which does this already!