Promoting author-standby -> author-primary fails with AEM 6.4 & 6.5
Closed this issue · 2 comments
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:
- Run the operational-task
promote-author
- Access the author instance
- AEM Login page appears
- 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):
- AEM 6.4 & AEM 6.5
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
A solution implementation should also fix the issue shinesolutions/puppet-aem-curator#200 reported by @henrykuijpers.
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.
AEM OpenCloud 4.8.0 includes the fix for the Author-Standby promotion bug.