Bart van Bragt d8eebb183a fix: prevent ES CPU saturation from has_child scoring all posts ... Without minimum_should_match=1 on the inner post bool query, Elasticsearch defaults MSM to 0 whenever a filter clause is present. This caused has_child to score every non-hidden post on every search request, saturating CPU on shared ES nodes with large corpora (3.7M+ posts). - Add BoolQuery subclass with create() override and minimumShouldMatch() (spatie/elasticsearch-query-builder 1.x uses `new self()` in create(), so subclassing requires overriding it) - Set minimumShouldMatch(1) on the inner post query after adding the is_hidden filter, so only genuinely matching posts are scored - Remove the operator('or') clause from buildShouldClauses() — with Turkish min_ngram=2, 'or' generates 2-gram tokens that match nearly every post, causing near-total index scans - Add ES client timeouts (connect: 2s, query: 10s) to prevent Apache mod_php worker saturation when ES is slow or unreachable		2026-04-14 16:07:50 +02:00
..
Controllers	fix: prevent ES CPU saturation from has_child scoring all posts	2026-04-14 16:07:50 +02:00
Client.php	Apply fixes from StyleCI	2022-11-18 09:33:13 +00:00