You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (Jira)" <ji...@apache.org> on 2026/09/18 12:48:00 UTC

[jira] [Created] (OAK-12403) oak-search-elastic: better handling of parse_exception

Thomas Mueller created OAK-12403:
------------------------------------

             Summary: oak-search-elastic: better handling of parse_exception
                 Key: OAK-12403
                 URL: https://issues.apache.org/jira/browse/OAK-12403
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: elastic-search
            Reporter: Thomas Mueller


Quite often we get  errors like

{noformat}
org.apache.jackrabbit.oak.plugins.index.elastic.query.async.ElasticResultRowAsyncIterator 
Error while fetching results from Elastic for  ...
co.elastic.clients.elasticsearch._types.ElasticsearchException: 
[es/search] failed: [search_phase_execution_exception] all shards failed
{noformat}

We should improve the handling of these cases:

* log parse_exceptions as WARN instead of ERROR
* reduce load on ES. These requests are might be quite frequent (in the reported case it's a clear attack some bot is trying to do). Every request is a call to ES that reply always in the same way. We should detect these cases and avoid to call ES. I see 2 options:
we pre-parse every request before calling ES and only forward it if valid
we cache the invalid queries and when we receive other same requests we skip the ES call



--
This message was sent by Atlassian Jira
(v8.20.10#820010)