Difference between revisions of "Server Restart Sequence"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
(3 intermediate revisions by the same user not shown) | |||
Line 8: | Line 8: | ||
# STOP ALL APPLICATION SERVERS | # STOP ALL APPLICATION SERVERS | ||
# On each server: | # On each server: | ||
{ | {install-dir}/profiles/IS_default/bin/shutdown.sh | ||
# STOP ALL memcached SERVERS | # STOP ALL memcached SERVERS | ||
# On each server: | # On each server: | ||
/bin/memcached -d stop | |||
# START ALL memcached SERVERS | # START ALL memcached SERVERS | ||
# On each server: | # On each server: | ||
/bin/memcached -d start -p {port} -u {user} -m {MB_of_memory} | |||
# Typical values: | |||
# Port: 11211, User: root, MB of memory: 25 | |||
# START ALL APPLICATION SERVERS | # START ALL APPLICATION SERVERS | ||
# On each server: | # On each server: | ||
{ | {install-dir}/profiles/IS_default/bin/startup.sh | ||
# START THE MESSAGING SERVER, if you're running one: | # START THE MESSAGING SERVER, if you're running one: |
Latest revision as of 11:23, 17 October 2019
When an installation employs memcached or the Messaging Server, it is important to follow this sequence when restarting servers:
- <syntaxhighlight lang="bash" enclose="div">
- STOP THE MESSAGING SERVER, if one is running:
/etc/init.d/messaging stop {hornetq-folder}/bin/stop.sh
- STOP ALL APPLICATION SERVERS
- On each server:
{install-dir}/profiles/IS_default/bin/shutdown.sh
- STOP ALL memcached SERVERS
- On each server:
/bin/memcached -d stop
- START ALL memcached SERVERS
- On each server:
/bin/memcached -d start -p {port} -u {user} -m {MB_of_memory}
# Typical values: # Port: 11211, User: root, MB of memory: 25
- START ALL APPLICATION SERVERS
- On each server:
{install-dir}/profiles/IS_default/bin/startup.sh
- START THE MESSAGING SERVER, if you're running one:
{hornetq-folder}/bin/start.sh /etc/init.d/messaging start </syntaxhighlight>
- Considerations
-
- Stopping application servers ensures that they aren't adding entries to the cache.
- Stopping memcached makes sure that the cache is flushed.
- Those two steps can occur in either order. It is the next two for which order is critical:
- Restarting memcached first makes sure that a clean copy of the cache is available.
- When the application servers come up, they use the clean cache.