[jira] [Resolved] (CLOUDSTACK-8426) Use a separate thread pool for VR reboot in case of out-of-band movement

["Koushik Das (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Koushik Das resolved CLOUDSTACK-8426.
-------------------------------------
    Resolution: Fixed

> Use a separate thread pool for VR reboot in case of out-of-band movement
> ------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8426
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8426
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.5.0
>            Reporter: Koushik Das
>            Assignee: Koushik Das
>             Fix For: 4.6.0
>
>
> When there is out-of-band movement of VRs (due to native HA in a VMWare cluster), they need to be rebooted for reconfiguring all the network rules. Currently all these VR reboot happens using the thread pool used for collecting VR statistics.
> Refer VirtualNetworkApplianceManagerImpl.java
> _executor = Executors.newScheduledThreadPool(1, new NamedThreadFactory("RouterMonitor"));
> Also as can be seen, the size of the pool is 1. So if there are multiple VRs getting moved out-of-band, the reboot for each will be queued up.
> The idea is to use a separate thread pool for handling VR reboot.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)