Difference between revisions of "Adding Additional memcached Servers"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
<includeonly>===Adding Additional memcached Servers===</includeonly> | |||
Adding an additional memcached servers helps to distribute the cache and balance the load across the memcached servers. | Adding an additional memcached servers helps to distribute the cache and balance the load across the memcached servers. | ||
| Line 22: | Line 23: | ||
</pre> | </pre> | ||
|} | |} | ||
<noinclude> | |||
[[Category:Installation]] | |||
</noinclude> | |||
After following the [[Server Restart Sequence]], all instances are using the new, distributed cache. | After following the [[Server Restart Sequence]], all instances are using the new, distributed cache. | ||
Latest revision as of 21:41, 2 October 2013
Adding an additional memcached servers helps to distribute the cache and balance the load across the memcached servers.
- To add an additional memcached server
- Edit networking.properties on all instances.
- Update the MemCachedServers entry
- Restart all servers, following the Server Restart Sequence
Note: The sequence is important!
- Example
There is one memcached server running on serverA (192.168.0.1) on port 11211. On each instance, the networking.properties has this:
MemCachedServers=192.168.0.1:11211
A second memcached server is brought up on serverB (192.168.0.2) on port 11211. The networking.properties file is edited on all instances so it looks like this:
MemCachedServers=192.168.0.1:11211 192.168.0.2:11211
After following the Server Restart Sequence, all instances are using the new, distributed cache.
If a 3rd memcached server is added (192.168.0.3), the networking.properties file will look like this:
MemCachedServers=192.168.0.1:11211 192.168.0.2:11211 192.168.0.3:11211
Again, the Server Restart Sequence is followed to enable the new configuration.