search

shinesolutions / aem-opencloud-manager

A set of Jenkins pipelines for provisioning and managing AEM OpenCloud environments
Apache License 2.0
6 stars 6 forks source link

Promoting author-standby -> author-primary fails with AEM 6.4 & 6.5 #71

Closed mbloch1986 closed 4 years ago

mbloch1986 commented 4 years ago

Describe the bug After promoting the author-standby to author-primary using the promote-author pipeline the author instance isn't accessible on AEM 6.4 & AEM 6.5

To Reproduce Steps to reproduce the behavior:

  1. Run the operational-task promote-author
  2. Access the author instance
  3. AEM Login page appears
  4. after login nothing happens or you are able to login but no assets can be load

Expected behavior The promoted author-primary instance should act like the original author-primary instance

Environment (please complete the following information if relevant):

Additional context Solution to fix is to generate the config file org.apache.jackrabbit.oak.segment.SegmentNodeStoreService.config & org.apache.jackrabbit.oak.segment.standby.store.StandbyStoreService.config with the content of an author-primary instance

Reference: https://docs.adobe.com/content/help/en/experience-manager-65/deploying/deploying/tarmk-cold-standby.html

A solution implementation should also fix the issue https://github.com/shinesolutions/puppet-aem-curator/issues/200 reported by @henrykuijpers.

mbloch1986 commented 4 years ago

Root cause was that on the author-primary the SegmentNodeStoreService config on the author-primary has the setting customBlobStore set to true, while on the author-standby this configuration is set to false. This results in data inconsistency between author-primary & author-standby, as assets are not getting transfered to the author-standby.

mbloch1986 commented 4 years ago

AEM OpenCloud 4.8.0 includes the fix for the Author-Standby promotion bug.