cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8866) restart.retry.interval is being used instead of migrate.retry.interval during host maintenance
Date Wed, 16 Sep 2015 06:23:46 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746963#comment-14746963
] 

ASF GitHub Bot commented on CLOUDSTACK-8866:
--------------------------------------------

Github user sureshanaparti commented on the pull request:

    https://github.com/apache/cloudstack/pull/834#issuecomment-140641999
  
    Reschedule time is always based on the work type. Code changes are OK. LGTM.


> 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
>
> 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)

Mime
View raw message