[
https://issues.apache.org/jira/browse/CLOUDSTACK-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519487#comment-14519487
]
ASF subversion and git services commented on CLOUDSTACK-8426:
-------------------------------------------------------------
Commit 795f3814f69f341df107678ab45fc29297932aa1 in cloudstack's branch
refs/heads/4.5 from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=795f381 ]
CLOUDSTACK-8426: Use a separate thread pool for VR reboot in case of
out-of-band movement
Using a cached thread pool for VR reboot task
(cherry picked from commit 1a719afb516164915b973f548c37814b448f0349)
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
> 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)
