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
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
The idea is to have a command to delay replication on a specific replica keeping the current replication status (stopped or started).
In some maintenance scenarios it is interesting to have an option to delay the replication, keeping the current state of the replication threads, and if that can be accomplished using the Orchestrator API we can use the same toolset and associate scripts which is very desirable.
I added a PR that was tested in my test environment as a suggested implementation and I'm open to work it out with the Orchestrator project as you see fit.
I appreciate your feedback and I'm open to contribute as you see fit.
Thank you!
The text was updated successfully, but these errors were encountered:
The idea is to have a command to delay replication on a specific replica keeping the current replication status (stopped or started).
In some maintenance scenarios it is interesting to have an option to delay the replication, keeping the current state of the replication threads, and if that can be accomplished using the Orchestrator API we can use the same toolset and associate scripts which is very desirable.
I added a PR that was tested in my test environment as a suggested implementation and I'm open to work it out with the Orchestrator project as you see fit.
I appreciate your feedback and I'm open to contribute as you see fit.
Thank you!
The text was updated successfully, but these errors were encountered: