Redis部署配置-主从复制 [英] Redis deployment configuration - master slave replication
问题描述
目前，我有两台服务器，它们已部署了基于node.js / Express.JS的Web服务API。我正在使用Redis缓存JSON字符串。
将这种设置部署到生产环境中的最佳选择是什么？我在在专用服务器上与非专用服务器上的：
在运行的Redis上服务器键入：
redis-benchmark -q -n 100000
如果应用服务器受到重击并经常使用所有内核，则您应该会看到基准测试存在重大差异。
我的建议是，继续进行操作。首先设置并添加对redis响应时间的监视，并且仅在必要时执行操作，如果基准测试结果非常差，则可能现在就执行。
作为补充说明，考虑不共享与Internet应用程序一起执行应用程序内部功能的主机的选项。
Currently I have two servers which I have deployed node.js/Express.JS based web services API. I am using Redis for caching the JSON strings.
What will be the best option deploying this setup in to production? I see here it advices to go with a dedicated server redis. OK. I take it and use a dedicated server for running redis master. Can I use existing app servers as slave nodes? Note : these app servers are running an Node/Express application.
What other other options do I have?
You can.
It all depends on the load that those other servers have, it's a problem of resource sharing. To be honest my main issue with your architecture is not the dedicated vs the non-dedicated servers, it's the fact that you are placing a Redis server (master or not) on a host that most likely will be facing the internet (expressJS app), meaning, it's quite exposed.
If you can simulate HTTP load into your Node/Express JS servers, see the difference between running some benchmark tests on your dedicated server vs the non dedicated ones:
On a running redis server type in:
redis-benchmark -q -n 100000
If the app servers are being hammered and using all cores frequently you should see a substantial difference in the benchmarks.
My suggestion is, go ahead with your first setup and add monitoring for the redis response times, and only act when you have to, which might be now if the benchmarks show very poor results.
As a side note, consider the option of not sharing hosts for services that you expose to the internet with services that perform internal functions to your application.
这篇关于Redis部署配置-主从复制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
