-
Notifications
You must be signed in to change notification settings - Fork 357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QUESTION] #617
Comments
If the old master is replaced by a new one, redis-plus-plus will get the new master's address from sentinels automatically. You don't need to worry about that. You only need to deploy the sentinel and master, slaves as the official site mentioned, and use the following code to create a Redis instance:
Regards |
Hi, |
In your case, I don't think 127.0.0.1 can be used. If you specify a domain instead of IP, and your operation system can resolve it, AsyncSentinel can work. redis-plus-plus does not do any special service discovery job but rely on the operation system. You'd better ask help from your network system admin or Redis admin for how to deploy Redis in sentinel mode. Regards |
Hi |
Replace the IP address with URI. However, as I mentioned, you need to ensure your operation system (not an external name service, e.g. zookeeper, etcd) can resolve the URI to IP. Regards |
Hi, sentinel.conf #include <sw/redis++/redis++.h> |
NO. AsyncSentinel's constructor does not take URI as parameter, instead, you can try to specify the hostname with Regards |
Hi, #include <sw/redis++/async_redis++.h> ConnectionPoolOptions pool_opts; |
You should specify all sentinel nodes' host and port to Regards |
Hi, #include <sw/redis++/async_redis++.h> ConnectionPoolOptions pool_opts; |
YES, you can try this code. Regards |
Thank you very much! Good luck! |
As sentinel mode,master restart,IP change , which change to slave, and origianl slave change to master.
How to set sentinel deploy blueprint and labels?
The text was updated successfully, but these errors were encountered: