Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

How to enable the clustering in AEM 6

ankitk22810784
Level 2
Level 2

Please let me know how to enable the clustering in AEM 6.0

I did by enable the CRX 2 by override the CRX 3 in AEM 6.0. Does it effect any of the functionality if we use the CRX 2 .... i means in sense of Mongo MK ???

Other one if enable the clustering with CRX 2 then how my publisher know this the author????? if do clustering at the author end

1 Accepted Solution
Lokesh_Shivalingaiah
Correct answer by
Community Advisor
Community Advisor

I would advice to migrate to CRX3 from CRX2 as CRX2 is not supported from AEM 6.1

Also if you are using CRX2, clustering should work as before and there will not be any Mongo MK for CRX2. If you upgrade to CRX 3 then you can use MongoMK for clustering using shard system

refer [1] for the same

[1] http://docs.adobe.com/docs/en/aem/6-0/deploy/recommended-deploys.html

View solution in original post

2 Replies
Opkar_Gill
Employee
Employee

Why do you want to enable clustering: Are you looking for scalability, reliability or high availability?

If you use CRX2, you will not have the advantages of the OAK based repository. MongoMK has no relation to CRX2 clustering, if you use CRX2 clustering and then want to move to MongoMK, you would have to migrate your repository to OAK and then to Mongo.

If you use CRX2 clustering, then replication requests goes via the master.

Lokesh_Shivalingaiah
Correct answer by
Community Advisor
Community Advisor

I would advice to migrate to CRX3 from CRX2 as CRX2 is not supported from AEM 6.1

Also if you are using CRX2, clustering should work as before and there will not be any Mongo MK for CRX2. If you upgrade to CRX 3 then you can use MongoMK for clustering using shard system

refer [1] for the same

[1] http://docs.adobe.com/docs/en/aem/6-0/deploy/recommended-deploys.html

View solution in original post