Environment
Adobe Experience Manager
Issue
The error SegmentNotFoundException
occurs in Author Cold Standby, similar to this example error:
*DEBUG* standby-run-46189 org.apache.jackrabbit.oak.segment.standby.client.StandbyClientSyncExecution Found reference from 451216fa-7d43-4b3a-a262-03abfc3c3fb1 to fbb91bad-9051-4ace-a77b-35fda8a358c6
org.apache.jackrabbit.oak.segment.SegmentNotFoundException: Segment fbb91bad-9051-4ace-a77b-35fda8a358c6 not found
Cause
The logs that point to SegmentNotFoundException
on the standby instances only are false positives, and the segment is found later.
If such logs are only seen in standby, and not when starting the instance as primary, then they can be ignored.
Solution
When this error occurs, follow these steps:
SegmentNotFoundException
are only seen in cold standby logs, and not when starting the instance as primary, then they can be ignored.org.apache.jackrabbit.oak.plugins.segment.SegmentNotFoundException
(related article Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6.x in AEM Documentation in Adobe Experience League) and org.apache.jackrabbit.oak.segment.SegmentNotFoundException
(related article at Fix Inconsistencies by restarting AEM when SegmentNotFound Issue is reported in AEM 6.3 in the AEM Documentation in Adobe Help Center) are two different exceptions.org.apache.jackrabbit.oak.segment.SegmentNotFoundException
seen in the standby logs is not the one that needs recovery steps from the article Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6.x in AEM Documentation in Adobe Experience League.org.apache.jackrabbit.oak.plugins.segment.SegmentNotFoundException
after starting standby as primary, you may need to perform a recovery process Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6.x in AEM Documentation in Adobe Experience League.