AgileApps Support Wiki Pre Release

Server Restart Sequence

From AgileApps Support Wiki
Revision as of 11:23, 17 October 2019 by imported>Aeric
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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

<syntaxhighlight lang="bash" enclose="div">
  1. STOP THE MESSAGING SERVER, if one is running:

/etc/init.d/messaging stop {hornetq-folder}/bin/stop.sh

  1. STOP ALL APPLICATION SERVERS
  2. On each server:

{install-dir}/profiles/IS_default/bin/shutdown.sh

  1. STOP ALL memcached SERVERS
  2. On each server:

/bin/memcached -d stop

  1. START ALL memcached SERVERS
  2. 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
  1. START ALL APPLICATION SERVERS
  2. On each server:

{install-dir}/profiles/IS_default/bin/startup.sh

  1. 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.