This repository was archived by the owner on Nov 24, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 189
This repository was archived by the owner on Nov 24, 2023. It is now read-only.
make start-relay easier to use #2241
Copy link
Copy link
Open
Description
Is your feature request related to a problem? Please describe
- I want to start relay to reduce the number of upstream binlog replication slaves, not care about which worker started relay so don't want to specify worker name. Currently I must specify worker name of the source is bound or free
I want to specify the position from which the relay is pulling. Currently this is specified in source configuration file, which is hard to modify
Describe the feature you'd like
start-relay -s <source-id>,stop-relay -s <source-id>to let current and future bound workers use relay to replicate.
and this feature is exclusive fromstart-relay -s <source-id> <worker-names>, which meansstart-relay -s source1 # now DM will start relay for current and future bound workers start-relay -s source1 worker2 # DM will raise error: "this source has automatically started relay for bound worker, can't specify worker using relay now" stop-relay -s source1 worker1 # DM will raise error: "this source has automatically started relay for bound worker, can't specify worker stopping relay now" stop-relay -s source1 # now DM will stop relay for current and future bound workers start-relay -s source1 worker2 # DM will let worker2 pull relay log of source1 start-relay -s source1 # DM will raise error: "this source has started relay for specified worker [worker1], can't automatically started relay for bound worker now" stop-relay -s source1 # DM will raise error: "this source has started relay for specified worker [worker1], can't automatically stop relay for bound worker now" stop-relay -s source1 worker2 # successstart-relay -s <source-id> <worker-name> --binlog-file <filename> --binlog-pos <position>orstart-relay -s <source-id> <worker-name> --binlog-gtid <gtid set>
Describe alternatives you've considered
No response
Teachability, Documentation, Adoption, Migration Strategy
No response
Ehco1996
Metadata
Metadata
Assignees
Labels
No labels