[
https://issues.apache.org/jira/browse/OAK-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-6121.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.7.12
Implemented in trunk: http://svn.apache.org/r1816718
> Add a metric to measure find document call resulting in null
> ------------------------------------------------------------
>
> Key: OAK-6121
> URL: https://issues.apache.org/jira/browse/OAK-6121
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: documentmk
> Reporter: Chetan Mehrotra
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 1.8, 1.7.12
>
>
> At times some calls are often seen which result in findDocument call
> resulting in null. In normal flow such occurrence should not be high. However
> due to way some code is written this can result in higher number of such
> calls.
> # As seen in OAK-5511 where code always looks for "oak:index" node under each
> changed node
> # In another case a caller may fetch a path as Item via {{Session#getItem}}
> {noformat}
> 22.02.2017 12:36:33.832 *TRACE* [sling-oak-observation-149]
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreStats.perf
> findUncached on
> key=8:/content/dam/test.png/jcr:content/renditions/original/jcr:primaryType,
> isSlaveOk=false [took 0ms]
> {noformat}
> To check if this is happening we should have a metric defined to measure rate
> of such calls
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
