You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Pierre-Luc Dion (JIRA)" <ji...@apache.org> on 2015/12/13 22:07:46 UTC

[jira] [Resolved] (CLOUDSTACK-8866) restart.retry.interval is being used instead of migrate.retry.interval during host maintenance

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

Pierre-Luc Dion resolved CLOUDSTACK-8866.
-----------------------------------------
    Resolution: Fixed

PR merged.

> restart.retry.interval is being used instead of migrate.retry.interval during host maintenance
> ----------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8866
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8866
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Maneesha
>            Assignee: Maneesha
>             Fix For: 4.7.0
>
>
> The frequency at which Cloudstack tries to migrate the VMs is currently controlled by the global parameter "restart.retry.interval" which has a default value of 600 seconds or 10 minutes.This has to be changed to use "migrate.retry.interval" which by default is 120 seconds or 2 minutes . Cloudstack uses restart.retry.interval for all operations-migrate,restart,stop,destroy.



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