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 "Stefan Egli (Jira)" <ji...@apache.org> on 2024/06/13 10:08:00 UTC
[jira] [Commented] (OAK-10880) Logging for hitting an orphaned UUIDs and reference indexes.
[ https://issues.apache.org/jira/browse/OAK-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854696#comment-17854696 ]
Stefan Egli commented on OAK-10880:
-----------------------------------
Upon revisiting this, I believe introducing a logging as is described in this ticket is actually not possible.
The parameter passed to session.getNodeByUUID/.getNodeByIdentifier doesn't come with any guarantee as to where it comes from. The caller could have made it up - it could be a dangling id it keeps in a non-reference property - it could be a proper one as well. Everything is possible there. The fact that the node cannot be found doesn't necessarily imply that /oak:index/uuid contains a dangling pointer (for which it was the intention to log).
I don't think we can implement this.
> Logging for hitting an orphaned UUIDs and reference indexes.
> ------------------------------------------------------------
>
> Key: OAK-10880
> URL: https://issues.apache.org/jira/browse/OAK-10880
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: documentmk
> Reporter: Ionut Pirlogea
> Priority: Minor
>
> Lookups of a node by uuid (getNodeByUuid) can hit a uuid index entry that points to a no-longer-existing node - i.e. it can point to an orphaned node, and thereby the uuid index entry is also "kind of orphaned" (but it can actually be reached via the jcr tree). Upon such an encounter, we should increment a metric and log the encounter with relevant information (eg just the uuid), if that's not already done.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)