cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3458) Network GC thread - fails to stop the router in multiple Management server cluster environment
Date Thu, 11 Jul 2013 16:39:48 GMT

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

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

Commit 398428743484bbacc1d99bf60ae253d36c4c153b in branch refs/heads/master from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3984287 ]

CLOUDSTACK-3458: network GC thread - acquire global lock to prevent multiple MS from running
the GC thread on the network at the same time

                
> Network GC thread - fails to stop the router in multiple Management server cluster environment
> ----------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3458
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3458
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Alena Prokharchyk
>            Assignee: Alena Prokharchyk
>             Fix For: 4.2.0
>
>
> Steps to reproduce:
> 1) Setup 2 management servers
> 2) Have network GC thread run every min (the minimum interval)
> 3) As there is no locking done on the thread, 2 management servers can run network GC
thread on the same network, and it results in VR being stuck in Stopping state forever.
> Solution: introduce the global lock on the GC thread.

--
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

Mime
View raw message