Difference between revisions of "Server Restart Sequence"

From AgileApps Support Wiki
imported>Aeric
 
imported>Aeric
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
=== Server Restart Sequence ===
<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> or the [[Platform Installation Guide (printable)#Messaging Server Installation|Messaging Server]], it is important to follow this sequence when restarting servers:
# Stop all application Servers
:<syntaxhighlight lang="bash" enclose="div">
# Stop all memcached servers
# STOP THE MESSAGING SERVER, if one is running:
# Start all memcached servers
/etc/init.d/messaging stop
# Start all application servers
{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:
;Considerations:
Line 10: Line 33:
:* 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 servers come up, they use the clean cache.
<noinclude>
 
[[Category:Installation]]
</noinclude>

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:

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