caching - Couchbase warmup strategies -


we have memcached cluster running in production. replacing memcached couchbase cluster persistent cache layer. question how implement cut-over , how warm couchbase bucket. can't switch on cold couchbase since starting old cache bring whole site down.

one option thinking warm couchbase memcached node first. means couchbase using (non-persistent) memcached bucket, , getting cache set/get traffic other memcached node. thing there minimum code changes (what's needed configure moxi proxy take memcached traffic, , register node memcached node). later convert memcached buckets couchbase. not sure couchbase supports conversions between these 2 types of buckets.

the 2nd option set persistent couchbase bucket (as opposed non-persistent memcached bucket) @ beginning. change production cache client replicate traffic both memcached , coucbase clusters. monitor couchbase bucket , once cache items reach size, complete cut-over. small drawback complexity change cache client.

thoughts?

edit on aug 9, 2016

as later found out, converting memcached bucket couchbase bucket not supported in couchbase. first option not feasible.

finally decide set client-side (standalone) proxy in each application host. incrementally host host ramp cache traffic. way changes in site small enough.

if want easy, less work, , proven work well, following:

  1. set moxi client on each application server.
  2. point moxi couchbase bucket on couchbase cluster.
  3. change web application servers point @ local moxi install.
  4. for next code revision start converting code using couchbase sdk instead of memcached.

yes, there time things not hot in cache, not take long couchbase populated. method used of time switch over. easy, fool proof. 1 thing have seen people try , copy things existing memcached servers on couchbase before cutting over, not sure of how new key of each value in memcached.

also note moxi interim step off of regular memcached , great, long run, better switch sdk. sdk has many more features pure memcached.

do not use memcached buckets have none of ha, persistence or whatever features of couchbase.


Comments

Popular posts from this blog

Spring Boot + JPA + Hibernate: Unable to locate persister -

go - Golang: panic: runtime error: invalid memory address or nil pointer dereference using bufio.Scanner -

c - double free or corruption (fasttop) -