cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9319) Timeout is not passed to virtual router operations consistently
Date Fri, 23 Sep 2016 20:20:20 GMT


ASF GitHub Bot commented on CLOUDSTACK-9319:

Github user ustcweizhou commented on the issue:
    many people thought that changing router.aggregation.command.each.timeout in global setting
will increase the timeout. Actually it is not, at least for KVM.
    for KVM hypervisors, we need to put router.aggregation.command.each.timeout=??? in
and restart cloudstack-agent.
    This PR increases the minimal timeout to 120 seconds which is helpful but does not really
fix the issue.
    I think it is better to add host-level setting for each host in the future, like we did
for domain/account, zone/cluster.

> Timeout is not passed to virtual router operations consistently
> ---------------------------------------------------------------
>                 Key: CLOUDSTACK-9319
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>    Affects Versions: 4.8.0
>         Environment: KVM + Ceph cloud, Ubuntu hosts.
>            Reporter: Aaron Brady
>            Priority: Trivial
> The timeout parameter is not passed down to `applyConfigToVR` inside `VirtualRoutingResource`
in all cases.
> This timeout is worked out as 3 seconds per command or 120 seconds (whichever is larger),
but because it's not passed to the first invocation, the default (120 seconds, DEFAULT_EXECUTEINVR_TIMEOUT)
is used.
> In a recent upgrade of our Virtual Routers, the timeout was being hit and increasing
`router.aggregation.command.each.timeout` had no effect. I built a custom 4.8 agent with the
timeout increased to allow the upgrade to continue.

This message was sent by Atlassian JIRA

View raw message