ninsmiracle commented on issue #2102: URL: https://github.com/apache/incubator-pegasus/issues/2102#issuecomment-2373168473
Regarding the second discussion, I think update the config via http is not a good idea. Here is the method we use this feat: 1.Push new config file (config.ini) with your own method to target cluster. 2.Open pegasus-shell and type `remote_command -t all dup-config-reload`. 3.Begin duplication as normal. Just like: `dup add -c c3tst-cluster3 -p` In step1, we require the cluster maintenance personnel to push the config file to the nodes of the target cluster first. This step is to ensure that the latest config file can be read immediately when the cluster node is restarted after a downtime. In step2, we can see that we use `remote_command` to upload the latest config file paramaters (those about duplication) to memory. So that, in step 3, you can use dup command without restart target cluster's nodes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
