You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pegasus.apache.org by "ninsmiracle (via GitHub)" <gi...@apache.org> on 2024/08/19 07:01:14 UTC
[I] Dynamic reload duplication config [incubator-pegasus]
ninsmiracle opened a new issue, #2102:
URL: https://github.com/apache/incubator-pegasus/issues/2102
## Feature Request
In PR #2000 , we can ignore cluster id with paramater `dup_ignore_other_cluster_ids`.
However, I think this function can be more flexible.
There is no doubt that, cluster id is very useful in multiple clusters duplication situation, backup-cluster can use it to judge data's priority.
So we may want to dynamic relod duplication config when we doing duplication.
**Describe the feature you'd like:**
Here is a case:
At beging, we have two clusters like cluster A dup data to cluster B. (A ----> B)
And now, demand changes:
C cluster also need to dup to cluster B. (A,C -----> B)
We don't need to restart the nodes on B, and can reload the config **ABOUT DUP**.
--
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: dev-unsubscribe@pegasus.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pegasus.apache.org
For additional commands, e-mail: dev-help@pegasus.apache.org
Re: [I] Dynamic reload duplication config [incubator-pegasus]
Posted by "ninsmiracle (via GitHub)" <gi...@apache.org>.
ninsmiracle commented on issue #2102:
URL: https://github.com/apache/incubator-pegasus/issues/2102#issuecomment-2373145551
There are 2 key-value paris needed to be reload:
--
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: dev-unsubscribe@pegasus.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pegasus.apache.org
For additional commands, e-mail: dev-help@pegasus.apache.org
Re: [I] Dynamic reload duplication config [incubator-pegasus]
Posted by "ninsmiracle (via GitHub)" <gi...@apache.org>.
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: dev-unsubscribe@pegasus.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pegasus.apache.org
For additional commands, e-mail: dev-help@pegasus.apache.org
Re: [I] Dynamic reload duplication config [incubator-pegasus]
Posted by "acelyc111 (via GitHub)" <gi...@apache.org>.
acelyc111 commented on issue #2102:
URL: https://github.com/apache/incubator-pegasus/issues/2102#issuecomment-2370782836
How many configuration key-value pairs are needed to be reload in this case?
There are several ways to update configs, http and remote_command, it's not a good idea to introduce another method.
--
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: dev-unsubscribe@pegasus.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pegasus.apache.org
For additional commands, e-mail: dev-help@pegasus.apache.org