We perform regular monthly server updates, occasionally more as needed. If
we had ticket replication (which Memcached itself doesn't support) we could
do these updates during regular working hours and users wouldn't notice.
Doing maintenance off hours is an option, and how we do it for
That looks very promising! We've been using memcached for some time as a
cache but this is the first time I've ever looked for a replicated model.
Thank you!
On Tuesday, April 10, 2018 at 12:05:26 PM UTC-4, Julien Gribonvald wrote:
>
> Hi,
>
> You can use repcached for the replicated side
Hi,
You can use repcached for the replicated side with memcached, we are
using it since several years in our context and we are totally satisfied !
Thanks
Le 10/04/2018 à 17:51, Ray Bon a écrit :
Teddy,
I have not used memcached. To accomplish your goal you would need a
replicated cache.
Teddy,
I have not used memcached. To accomplish your goal you would need a replicated
cache.
How often do you plan to restart your servers? Will your users to notice?
Ray
On Tue, 2018-04-10 at 08:07 -0700, Teddy Brown wrote:
Is it possible to get High Availability with the memcache ticket
Is it possible to get High Availability with the memcache ticket registry?
I only have these attributes configured currently and it works.
However it seems if the Memcached instance on either host is restarted (or
the host is restarted) that CAS continues to function as expected, any
