What is the effect of Apache2ctl graceful

KinnowGrower · 08-04-2012, 05:04 PM

Network setup is

Code:

                                  |--Apache web server1
Internet---->|Apache Load Balancer|--Apache web server 2
                                  |--Apache web server 3

Problem:
Apache Load balancer is reasonably busy and running in production environment. Some time, we have to take one of the Web server out of loop for some reason.

Question: What is best way to take one of the Apache web server out of loop.?. Is it correct way by commenting out the webserver related lines on Apache Load Balancer cluster configuration and run the command

Code:

#apache2ctl graceful

How it Will effect the existing connection to the Webservers behind the Load balancer? What will happen to the customers at other buying/searching items and doing credit card transactions?

KinnowGrower · 08-06-2012, 12:39 PM

I was hoping some help with above mentioned issue, please let me know if I am not clear enough at any point.

KinnowGrower · 08-07-2012, 09:58 PM

Any help Please?

KinnowGrower · 08-09-2012, 08:11 PM

Any idea? Any help/hint on this ? Is it in wrong forum?. if it is please move it to correct one

jsaravana87 · 08-13-2012, 01:34 AM

#man apache2ctl graceful clearly states the difference between normal stop and graceful stop

graceful : Gracefully restarts the Apache daemon by sending it a
SIGUSR1. If the daemon is not running, it is started.
This differs from a normal restart in that currently open
connections are not aborted. A side effect is that old
log files will not be closed immediately. This means
that if used in a log rotation script, a substantial
delay may be necessary to ensure that the old log files
are closed before processing them. This command automat‐
ically checks the configuration files via apache2ctl con‐
figtest before initiating the restart to to catch the
most obvious errors. However, it is still possible for
the daemon to die because of problems with the configura‐
tion.

graceful-stop Gracefully stops the Apache httpd daemon. This differs
from a normal stop in that currently open connections are
not aborted. A side effect is that old log files will
not be closed immediately.

stop Stops the Apache daemon.