Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

AEM Author Clustering - Master Slave configuration

Avatar

Level 1

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.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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

View solution in original post

3 Replies

Avatar

Level 10

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!

Avatar

Level 2

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  ? 

Avatar

Correct answer by
Employee Advisor

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