[jira] [Commented] (CLOUDSTACK-2682) Redundant router: Router switch to MASTER then immediately switch back to BACKUP would failed to work

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666850#comment-13666850 ] 

ASF subversion and git services commented on CLOUDSTACK-2682:
-------------------------------------------------------------

Commit a21a4e5ac43af0f225b6e56e3e73ea7e570510d9 in branch refs/heads/master from Sheng Yang <sh...@citrix.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a21a4e5 ]

CLOUDSTACK-2682: Sleep 1 second before switch to BACKUP

To prevent backup.sh preempt master.sh when keepalived switch to MASTER then
back to BACKUP immediately.

Since it would take at least 3 seconds for BACKUP to switch to MASTER(vrrp
timeout), the fix won't cause chaos when keepalive try to switch to MASTER.

                
> Redundant router: Router switch to MASTER then immediately switch back to BACKUP would failed to work
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2682
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2682
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Sheng Yang
>            Assignee: Sheng Yang
>             Fix For: 4.2.0
>
>
> The scripts master.sh and backup.sh are called at the same time when the 
> "backup" RvR switch to MASTER then immediately back to BACKUP, because of the 
> file lock mechanism we're using, there is a chance that backup.sh may be called 
> before master.sh, then result in router seems in MASTER state(though keepalived 
> still reports BACKUP state). 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira