Difference between revisions of "Server Restart Sequence"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
<includeonly>=== Server Restart Sequence ===</includeonly> | <includeonly>=== Server Restart Sequence ===</includeonly> | ||
When an installation employs <tt>memcached</tt>, it is important to follow this sequence when restarting servers: | When an installation employs <tt>memcached</tt>, it is important to follow this sequence when restarting servers: | ||
# Stop the messaging server: | |||
# | #: <tt>/etc/init.d/messaging stop</tt> | ||
# | #: <tt>{hornetq-folder}/bin/stop.sh</tt> | ||
# | :<syntaxhighlight lang="bash" enclose="div"> | ||
# | # STOP ALL APPLICATION SERVERS | ||
# On each server: | |||
# STOP ALL memcached SERVERS | |||
# On each server: | |||
# START ALL memcached SERVERS | |||
# On each server: | |||
# START THE MESSAGING SERVER, if you're running one: | |||
</syntaxhighlight> | |||
: <tt>{hornetq-folder}/bin/start.sh</tt> | |||
: <tt>/etc/init.d/messaging start</tt> | |||
;Considerations: | ;Considerations: | ||
Revision as of 02:39, 24 January 2014
When an installation employs memcached, it is important to follow this sequence when restarting servers:
- Stop the messaging server:
- /etc/init.d/messaging stop
- {hornetq-folder}/bin/stop.sh
# STOP ALL APPLICATION SERVERS # On each server: # STOP ALL memcached SERVERS # On each server: # START ALL memcached SERVERS # On each server: # START THE MESSAGING SERVER, if you're running one:
- {hornetq-folder}/bin/start.sh
- /etc/init.d/messaging start
- 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.