https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42835
--- Comment #44 from Martin Renvoize (ashimema) <[email protected]> --- The items-index availability/facets caches (_get_available_biblionumbers(), _get_item_facets() in Koha/SearchEngine/Elasticsearch/Search.pm) now uses a 15s TTL to avoid re-scanning the items index on every "available" search. I looked at adding immediate cache invalidation on every circulation event (checkout/checkin/transfer/edit), but decided against it: it would require a global invalidation trigger that fires on any item change anywhere in the instance, which significantly reduces the caching benefit during busy circulation periods — exactly when the caching matters most for protecting Elasticsearch from load. I felt a 15s worst-case staleness window on availability/facets is close enough to real-time that it shouldn't be perceptible to end users in normal use. Documenting this as a known, accepted trade-off rather than fixing it: for up to 15 seconds after a checkout/checkin, the "available" search filter and item-count facets may not yet reflect the very latest circulation activity for an affected biblio. Everything else (item state itself, the items index, non-cached lookups) is updated synchronously. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
