AgileApps Support Wiki Pre Release

Difference between revisions of "Server Restart Sequence"

From AgileApps Support Wiki
imported>Aeric
 
imported>Aeric
Line 10: Line 10:
:* Stopping memcached makes sure that the cache is flushed.
:* 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:
:* Those two steps can occur in either order. It is the next two for which order is critical:
::* Restarting memcached before LongJump makes sure that a clean copy of the cache is available for the application server, when it comes up.
::* Restarting memcached first makes sure that a clean copy of the cache is available when the application server comes up.

Revision as of 22:20, 22 June 2011

Server Restart Sequence

When an installation employs memcached, it is important to follow this sequence when restarting servers:

  1. Stop all application Servers
  2. Stop all memcached servers
  3. Start all memcached servers
  4. Start all application servers
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 server comes up.