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: | ||
{{:Common:Stop the Messaging Server}} | {{:Common:Stop the Messaging Server}} | ||
# Stop all application Servers | # Stop all application Servers | ||
Revision as of 02:32, 24 January 2014
When an installation employs memcached, it is important to follow this sequence when restarting servers: Common:Stop the Messaging Server
- Stop all application Servers
- Stop all memcached servers
- Start all memcached servers
- Start all application servers
Common:Start the Messaging Server
- 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.