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

Offloading Instance Nodestore

deepaksuresh94
Level 2
Level 2

In my design, I have the AEM author instance with its nodestore in MongoDB and its Datastore in NFS. The Publish instance has shares the NFS Datastore and has its own TarMK nodestore. There will be an offloading instance setup to offload some of the works of the Primary Author(like renditions generation etc). As I read from the Adobe docs, for this offloading instance, its Datastore can be the same as the one shared by the Primary Author and Publish instances.

However, what about the nodestore? Should this offloading instance connect to the same MongoDB database as the Primary Author or should it have its own TarMK nodestore? If it were to have its own TarMK nodestore will there be any compatibility issues when it is working with Primary Author which has its nodestore in MongoDB?

1 Accepted Solution
berliant
Correct answer by
Employee
Employee

You should not add an AEM worker to your existing MongoMK cluster. The best approach for an offloading configuration is if you set TarMK instance for the worker and use share DataStore with your existing Author. It will also make sense to set a binary less replication to gain the best performance

View solution in original post

2 Replies
berliant
Correct answer by
Employee
Employee

You should not add an AEM worker to your existing MongoMK cluster. The best approach for an offloading configuration is if you set TarMK instance for the worker and use share DataStore with your existing Author. It will also make sense to set a binary less replication to gain the best performance

View solution in original post