[
https://issues.apache.org/jira/browse/OAK-10918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved OAK-10918.
-------------------------------
Fix Version/s: 1.66.0
Resolution: Fixed
[PR|https://github.com/apache/jackrabbit-oak/pull/1559] merged, marking ticket
done.
> Embed and log an explain for the fullgc mongo query
> ---------------------------------------------------
>
> Key: OAK-10918
> URL: https://issues.apache.org/jira/browse/OAK-10918
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: documentmk
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Major
> Fix For: 1.66.0
>
>
> We should do an {{explain}} of the query that is ultimately used in
> MongoGCSupport for fullgc, and log (at INFO) the most relevant pieces of the
> winning plan (or just the entire winning plan). Doing this once per reconfig
> (which is probably currently once per JVM-incarnation) shouldn't be intrusive
> - but it would make it observable which, if any, index is being used. Eg it
> should say something like
> {noformat}
> "stage": "IXSCAN",
> "indexName": "_modified_1__id_1",
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
