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

Sheng Yang resolved CLOUDSTACK-799.
-----------------------------------

    Resolution: Fixed

Fixed with:

commit aa9701a10c2ed1aad6edf552e93d6fa792a135f9
Author: Sheng Yang <[email protected]>
Date:   Thu Nov 29 16:57:11 2012 -0800

    CLOUDSTACK-799: Redundant router: Speed up RvR status update
    
    The basic idea behind this is, deploy a fix sized threadpool for updating 
RvR
    status, then using producer/consumer model. There is a global configuration
    router.check.poolsize(10 by default) to control the pool size.
    
    Using pool size 100 for 1000 RvR is tested with simulator and works well.
    
    Also we can adjust the global configuration option router.check.interval to 
e.g.
    60s from default 30s to mitigate the issue.

                
> [Load Test] Check router statistics falls behind in gathering stats by more 
> than 2 times the set value
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-799
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-799
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.0.0
>            Reporter: Sheng Yang
>            Assignee: Sheng Yang
>             Fix For: 4.1.0
>
>
> Frequency of router statistics interval is set to default 5 mins. But 
> observing a delay of as high as 16 mins between successive router statistics 
> collection. 
> Setup: 
> Clustered set up with 2 MS 
> 1 zone, advanced with RVR 
> 112 Pods [Each Pod having 2 Clusters] 
> 224 Clusters [Each cluster having 8 hosts and one primary storage] 
> 1782 Hosts 
> 4000 User accounts [Each account having one network] 
> 12000 User instances 
> 8000 Virtual Routers [Since its RVR] 
> router.check.interval = 5 mins 
> The router check is falling behind by more than 11 mins in certain cases. The 
> least value for frequency is 8 mins and highest is as high as 16 mins, while 
> expected is 5 mins. 
> The analysis was done for a period of about 3 hours across both MS. 
> Monitoring was done based on the "CheckRouterCommand" for each router across 
> both MS. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to