cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9873) VR related periodic jobs are scheduled twice and run twice on management servers
Date Thu, 13 Apr 2017 06:28:41 GMT

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

ASF GitHub Bot commented on CLOUDSTACK-9873:
--------------------------------------------

Github user ustcweizhou commented on the issue:

    https://github.com/apache/cloudstack/pull/2041
  
    @Slair1 this is already fixed by commit ba9dcba in 4.10/master


> VR related periodic jobs are scheduled twice and run twice on management servers
> --------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9873
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9873
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Virtual Router
>    Affects Versions: 4.8.0, 4.9.0
>         Environment: Appears all environments
>            Reporter: Sean Lair
>            Priority: Minor
>             Fix For: 4.10.0.0
>
>
> The "start" method of VirtualNetworkApplianceManagerImpl schedules several period checks,
including stats updates, alert updates, and VR checks including S2S vpn checks.
> VpcVirtualNetworkApplianceManagerImpl also extends VirtualNetworkApplianceManagerImpl.
 Thus when VpcVirtualNetworkApplianceManagerImpl is used, it re-runs the "start" method and
once again schedules all the various jobs.  Thus all the jobs run twice at each scheduled
run.  This is easily seen in the mangement-server.log:
> cat /var/log/cloudstack/management/management-server.log | grep "routers to update status"
> 2017-04-10 21:48:12,879 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-5f7bc584)
(logid:4d5b1031) Found 10 routers to update status.
> 2017-04-10 21:48:12,932 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-d027ab6f)
(logid:1bc50629) Found 10 routers to update status.
> 2017-04-10 21:48:42,877 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-2c8f4d18)
(logid:e9111785) Found 10 routers to update status.
> 2017-04-10 21:48:42,927 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-1bfd5351)
(logid:ad0f95ef) Found 10 routers to update status.
> 2017-04-10 21:49:12,874 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-ede0d2bb)
(logid:6f244423) Found 10 routers to update status.
> 2017-04-10 21:49:12,928 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-d58842d5)
(logid:8442d73c) Found 10 routers to update status.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message