You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are sharing one set of sentinel nodes to serve for multiple services. But the problem is once we need to deploy a new service, we need to add it to the sentinel monitoring, the old way was just add the master name into the ansible playbook, and rerun the tasks. But we found every time this task will restart our ansible. I wonder if this could improve if you detect the redis is already running, and only add the new masters using the command without restarting it.
The text was updated successfully, but these errors were encountered:
We are sharing one set of sentinel nodes to serve for multiple services. But the problem is once we need to deploy a new service, we need to add it to the sentinel monitoring, the old way was just add the master name into the ansible playbook, and rerun the tasks. But we found every time this task will restart our ansible. I wonder if this could improve if you detect the redis is already running, and only add the new masters using the command without restarting it.
The text was updated successfully, but these errors were encountered: