latest good state of segmentstore not found | Community
Skip to main content
RitendraS11
RitendraS11
Level 4
December 20, 2023
Solved

latest good state of segmentstore not found

  • December 20, 2023
  • 4 replies
  • 1364 views

Hi All,

 

I have one author and two publisher instances for my AEM setup. On publisher 1, error.log was increasing abruptly. When I checked logs, I found a lot of logs in error.log related to segment store - 

*ERROR* [async-index-update-async] org.apache.jackrabbit.oak.segment.SegmentNotFoundExceptionListener Segment not found: d977b6a3-8045-4d95-af34-89f80c1a1cb5. SegmentId age=19590979ms

 

I suspected that there is an issue with datastore, below URL  is something that I referred to fix the issue on publisher 1 -

https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-16542.html?lang=en

 

When I checked to revert a corrupt segment store to its latest good state, I got that there is no latest segment store available. What should be the next step? Is there a possibility to map the existing datastore of publisher 2 to publisher 1?

 

Thanks in advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Saravanan_Dharmaraj

@ritendras11 Technically speaking if you feel the other publisher is having gold copy of all the contents correct without any issue you can copy the whole repository (crx-quickstart) folder into the publisher having issue. But i would do that as last option and make sure all the runmodes and configs are correct. I am assuming its non cloud aem instances. 

4 replies

Saravanan_Dharmaraj
Community Advisor
Saravanan_DharmarajCommunity AdvisorAccepted solution
Community Advisor
December 21, 2023

@ritendras11 Technically speaking if you feel the other publisher is having gold copy of all the contents correct without any issue you can copy the whole repository (crx-quickstart) folder into the publisher having issue. But i would do that as last option and make sure all the runmodes and configs are correct. I am assuming its non cloud aem instances. 

    RitendraS11
    RitendraS11Author
    Level 4
    December 21, 2023

    Thanks a lot @saravanan_dharmaraj. I am worried that copying crx-quickstart folder can cause problems with configurations related to the author instance (replication agents etc). 

      Saravanan_Dharmaraj
      Community Advisor
      Saravanan_DharmarajCommunity Advisor
      Community Advisor
      December 21, 2023

      I meant copying from working Publish to non working Publish instance not from Author. 

        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        January 8, 2024

        @ritendras11  Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

        Kautuk Sahni
        RitendraS11
        RitendraS11Author
        Level 4
        January 9, 2024

        To fix the issue, I have copied CRX-Quickstart folder of one publisher to the other. Since, every configuration is same - it didn't created any issue. 

         

        Thanks everyone for valuable suggestions!! 

          kautuk_sahni
          Community Manager
          kautuk_sahniCommunity Manager
          Community Manager
          January 15, 2024

          @ritendras11 Did you find the suggestions from users helpful?

          Kautuk Sahni
          Terms & ConditionsAccessibility statement

          Loading footer...