Uploaded image for project: 'CloudStack'
  1. CloudStack
  2. CLOUDSTACK-8426

Use a separate thread pool for VR reboot in case of out-of-band movement

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.5.0
    • Fix Version/s: 4.6.0
    • Component/s: Management Server
    • Security Level: Public (Anyone can view this level - this is the default.)
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              koushikd Koushik Das
              Reporter:
              koushikd Koushik Das
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: