[one-users] Sunstone redundant memcached setup

[Stefan Kooman]

Hi List,

If you have a setup consisting of more than one "front-end" server I
think it would make sense to be able to specify more than one memcached
server in sunstone. If for one reason or another a memcached server is
not available anymore it can automatically try the next one configured
(after $timeout value). Building this funtionality directly into
sunstone gives you the benefit of "redundant" memcached servers without
the need for cluster software taking care of this. If you let sunstone
server A point to memcached server A (primary) and memached server B
(secondary) and sunstone server B point to memcached server B (primary)
and memcached server A (secondary) you've doubled the available
memcached capacity during normal operations.

Are there any reasons _not_ to use two different (active) memcached
servers?

Cheers,

Stefan


-- 
| BIT BV  http://www.bit.nl/        Kamer van Koophandel 09090351
| GPG: 0xD14839C6                   +31 318 648 688 / info at bit.nl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 230 bytes
Desc: Digital signature
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20131113/68c20639/attachment.pgp>