amazon web services - Scaling Up an Elasticache Instance? -


i'm running site uses redis through elasticache. want move larger instance more ram since we're getting around 70% full on our current instance type.

is there way scale elasticache instance in same way rds instance can scaled?

alternative, wanted create replica group , add bigger instance it. then, once it's replicated , running, promote new instance master. doesn't seem possible through aws console replicas created same instance type primary node.

am missing or use case can't achieved. understand can start bigger instance , manually deal replication move web servers on use new server require downtime due dns migration, etc.

thanks!, alan

elasticache feels more cache solution in memcached sense of word, meaning scale up, indeed fire new cluster , switch application on it. performance degrade moment because cache have rebuilt, nothing more.

for many people (i suspect included), however, redis more of nosql database solution in data loss unacceptable. amazon offers read replicas "solution" problem, it's still bit iffy. of course, offers replication reduce risk of data loss, it's still near production-safe (or mature) rds redis database (as opposed cache, it's quite perfect), offers backup , restore procedures, well-structured change management support scaling up. knowledge, elasticache not support changing instance type running cluster. suggests it's merely in-memory solution lose data on reboot.

i'd go far saying if data loss concerns you, should @ self-rolled redis solution instead of using elasticache. not marginally cheaper run, enable change instance type on other ec2 instance (after stopping it, of course). enable use rdb or aof persistence.


Comments

Popular posts from this blog

get url and add instance to a model with prefilled foreign key :django admin -

android - Keyboard hides my half of edit-text and button below it even in scroll view -

css - Make div keyboard-scrollable in jQuery Mobile? -