cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-9864) cleanup stale worker VMs after job expiry time
Date Thu, 06 Apr 2017 08:27:41 GMT
Daan Hoogland created CLOUDSTACK-9864:
-----------------------------------------

             Summary: cleanup stale worker VMs after job expiry time
                 Key: CLOUDSTACK-9864
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9864
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: VMware
            Reporter: Daan Hoogland
            Assignee: Daan Hoogland


In the present code cleaning worker vms after a timeout is disabled, with the documented reason
that there is no API to query for related tasks in vcenter. ACS has an expiry time for jobs
and a cancel time for jobs.
- Jobs that take longer then the expiry time will have their results be be neglected.
- Jobs that are cancelled are forcibly removed after the cancellation expity time.
Any worker remaining after expiry+cancellation will surely be stale and can be removed.

As some administrators may not want this behaviour there will be a setting which by default
is false that will guard against cleaning stale worker VMs.
Stale worker VMs will be cleaned after 2 * (expiry-time + cancellation-time) as a safe margin.

related settings:
job.expire.minutes: 1440
job.cancel.threshold.minutes: 60
vmware.clean.old.worker.vms: false (new)



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

Mime
View raw message