[
https://issues.apache.org/jira/browse/CLOUDSTACK-9114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054683#comment-15054683
]
ASF GitHub Bot commented on CLOUDSTACK-9114:
--------------------------------------------
Github user ustcweizhou commented on the pull request:
https://github.com/apache/cloudstack/pull/1198#issuecomment-164199095
@DaanHoogland @wilderrodrigues
assume there are two routers now routerA (master) and routerB (backup).
if we destroy routerA (master) at first, then routerB will become master
without downtime. and another routerC will create as BACKUP. However, we need
to destroy routerB as well, then routerC will become MASTER and another new
routerD will become BACKUP.
in this processing, we also need to wait some seconds for
keepalived/conntrackd on routerC to be up , because we should make sure that
the services on BACKUP are running before destroying MASTER.
hence, I think the solution in PR is good (there is only one BACKUP->MASTER
state change).
for the sleep or not, we need to test it. I added it because the test
failedout in my testing (without sleep).
> restartnetwork with cleanup should not update/restart both routers at once
> --------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9114
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9114
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Wei Zhou
> Assignee: Wei Zhou
>
> for now, restartnetwork with cleanup will stop both RVRs at first, then start
> two new RVRs.
> to reduce the downtime of network, we'd better restart the RVRs one by one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
