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

CQ instance down still request going to the respective web server in clustered environment

Avatar

Level 4

Hi,

I have a clustered CQ environment. There are 2 CQ servers in my cluster hosted on different web servers.

I have shutdown one of the CQ instance but web server is still up and running which is hosting that CQ instance.

When I hit the page, it gives me an error - Bad gateway, that means though CQ instance is down request is still going to web server.

Shouldn't it be that if one CQ instance is down, request should go to another web server with second cluster node?

Regards,

Shallu Rohilla

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Then configure your loadbalancer not to check the healthstate of the webserver/dispatcher, but to check the health of your CQ instance sitting behind the webserver/dispatcher. The probably most easiest way is to append a "?" at the end of the healthcheck URL.

View solution in original post

6 Replies

Avatar

Former Community Member

Hi Shallu,

Have you Added both of your CQ instances in the "/renders" section of your Dispacther Configuration?. This could be due to Web server not being able to Connect to your Running CQ instance. Dispatcher Logs could also help you to fix it.

Avatar

Level 10

In front of web servers you should have load balancer to check the healthiness & redirect to available one.  Or at dispatcher you need to configure cross reference. 

Avatar

Level 4

Hi,

Both the web servers have different Apache configurations and have renders pointing to their individual servers for clustering.

Regards,

Shallu Rohilla

Avatar

Level 6

So Dispatcher1 is connected to Publish1 and Dispatcher2 is connected to Publish2 with no cross reference. A pure Left and Right setup.

And then you have a load balancer in front of the Dispatchers and turn of the Publish1 but Dispatcher 1 is still serving content. Did I get you right?

/Ove

Avatar

Correct answer by
Employee Advisor

Then configure your loadbalancer not to check the healthstate of the webserver/dispatcher, but to check the health of your CQ instance sitting behind the webserver/dispatcher. The probably most easiest way is to append a "?" at the end of the healthcheck URL.