cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8866) restart.retry.interval is being used instead of migrate.retry.interval during host maintenance
Date Mon, 30 Nov 2015 06:47:11 GMT

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

ASF subversion and git services commented on CLOUDSTACK-8866:
-------------------------------------------------------------

Commit 07ee5e9bf0e167299faef81f41a8514200696b65 in cloudstack's branch refs/heads/master from
[~ManeeshaP]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=07ee5e9 ]

CLOUDSTACK-8866 : restart.retry.interval is being used instead of migrate.retry.interval during
host maintenance


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