AEM Author Clustering - Master Slave configuration | Community
Skip to main content
A
aem_consultant
October 16, 2015
Solved

AEM Author Clustering - Master Slave configuration

  • October 16, 2015
  • 2 replies
  • 2799 views

Hi All,

I am facing a strange issue on CQ 5.6.0 Cluster for Author servers.

In a Master Slave cluster setup of Author instances, the sync between Master and Slave(s) causes the slave(s) CQ to become unresponsive.

The Node write operation (programatically) on Master is heavy as the requirement is to create around 50K new nodes. So synching of these new 50K nodes to the Slave CQ Author instance causes unresponsive behavior.

Has anyone encountered this before? Is there a way to optimize the sync between Master and Slave CQ Authors (Cluster) so that the Slave instances are responsive throughout the sync operation?

Thanks for any inputs.

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 joerghoh

Hi,

I don't think, that there's a way to workaround for the behaviour you observed. With AEM 6.0 and Mongo-MK (as the currently only available clustering solution) the problem shouldn't exist anymore.

kind regards,
Jörg

2 replies

WhoaShekhar
WhoaShekhar
Level 10
October 16, 2015

Hi There,

Thanks for reaching out to Adobe Community.

I'd suggest you to follow the below mentioned article for troubleshooting steps:

http://docs.adobe.com/docs/en/crx/current/administering/cluster.html#Troubleshooting

Hope this helps!

Thanks!

S
ShaileshPa
Level 2
June 7, 2024

can you give me link to documentation about how this is achieved in AEM 6.5 ( latest) and AEMaaCS ? I guess mongo-mk tech stack is not recomended anymore in AMS or AEMaaCS , is there an alternative available to this  ? 

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi,

I don't think, that there's a way to workaround for the behaviour you observed. With AEM 6.0 and Mongo-MK (as the currently only available clustering solution) the problem shouldn't exist anymore.

kind regards,
Jörg

Terms & ConditionsAccessibility statement

Loading footer...