AEM 6.1 + mongo DB 3.5 clustering

Hi,

Mongo 3.5 is not supported [1]

Regards,

Opkar

[1] https://docs.adobe.com/docs/en/aem/6-1/deploy/technical-requirements.html

Hi Mahesh,

when you say shared cluster, do you mean sharing the MongoDB cluster between author and publish instances? Why do you need a Mongo cluster for your publish instances? I can't think of a use case for it, even for User Generated Content, a common store is the recommended approach.[1]

Regards,

Opkar

[1] http://docs.adobe.com/docs/en/aem/6-1/administer/communities/srp/asrp.html

Hi Opkar,

i am going through that link u provided, in the mean while i am posting my requirement below.

In our environemnt we have two  AEM6.1 author and two  mongo DB, we wanted a shared cluster between two Mongo DB. by this both the authors will be in sync with each other. 

quick question: -

1. if we create shared cluster between two mondo DB and integrate with two authors, will that shared cluster will take care of both the authors also??

Thanks,

Mahesh

Hi Opkar,

Thanks for sharing those links those helped to understand , our site require MONGO DB, 

After reading the above link, i got to know sharding and MongoDB 3.5 is not supported with AEM where as replica set is supported, we wnated to go with replica set.

Now i wanted to integrate  two  AEM 6.1 Authors with mongo DB replica set  

i have followed the below link [1] to setup, but it shows only one author configuration, can i follow the same steps for two authors.

[1] http://blogs.adobe.com/contentmanagement/2014/07/22/aem6-mongo-minimal-setup/

Thanks, Mahesh

Hi Mahesh,

In AEM6 clustering, the clustering is done at the MongoDB level.

What this means for you, is that once you initialise an AEM author instance to connect to a MongoDB instance, the MongoDB instance is set up for AEM therefore you can add more author instances by configuring them to connect to the existing MongoDB instance. Once connected, the new AEM instance will synchronise with the DB. At this point both author instances are pointing to the same DB and any changes will be synched via Mongo. So in essence, they are synchronised. Hope that makes sense.

In the article you mentioned, the last sections explains the same process can be used to add more AEM instances. 

Regards,

Opkar

Hi Mahesh,

You are right, 3 members are the minimum required for MongoDB cluster. The third can be an arbiter. Three machines sounds sensible. Once you get to production and you have multiple data centres, you may want to put each box in a different data centre to ensure maximum resilience.

The error you are seeing is the symptom of your repository not starting. The actual exception which stopped your repository from starting is likely to be much earlier in the error log. If it is not obvious, please start another thread otherwise this will become a monster thread :) 

Regards,

Opkar

Hi Opkar,

Thanks for your quick reply :)

My bad i missed it and asked about how to connect extra auhtor, i was about to post reply to that, in the mean while you replied.

Can you please suggest me how many boxes i need to setup replica set,  i wanted to go for below configuration :-

2 Authors - two machines, and for node0 node1 and arb0 on three diff boxes ??

when i am trying to start author with the parameters given in the link i am getting below error, any idea:-

16.08.2015 23:49:24.646 *ERROR* [qtp664876097-60] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.
16.08.2015 23:49:24.646 *ERROR* [qtp664876097-60] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.

Thanks,Mahesh

Hi Mahesh,

when you installed AEM and connected to Mongo, did you give adequate time for the initialisation process? It can take up to 30 minutes.

When you first set up your system, was AEM up and all the interfaces available?

Regards,

Opkar

Hi Opkar,

That was the only error, i am facing same error with your command also.

Thanks, Mahesh