cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayapal Reddy (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6997) conntrack set to a very low value on router
Date Fri, 31 Oct 2014 05:03:35 GMT


Jayapal Reddy commented on CLOUDSTACK-6997:

The default conntrack max set on the router VM is quite low. Due this there are a lot of packet
When where are more number of connections made VR is not able to handle the connections. So
connections got dropped.

Root Cause Analysis:
Setting the ip_conntrack_max value in  sysctl.conf  is failed.
Conntrack_max is limited to 32'000 but the system would be capable of handling many more connections.

Proposed solution:
Setting ip_conntrack_max from the rc.local. On VR start rc.local run and execute the commands
in the file.

Verification steps:
1. Bring up the router.
2. Verify the below files in VR for the value 1000000.

3. It can also verified by making more number of tcp connections and see VR is
is handling around 65,000+ connections.

> conntrack set to a very low value on router
> -------------------------------------------
>                 Key: CLOUDSTACK-6997
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>            Reporter: Jayapal Reddy
>            Assignee: Jayapal Reddy
>             Fix For: 4.4.0
> Set ip_conntrack_max to 1 million
> ip conntrack value which is in sysctl.conf is not applied on VR.
> Debian wheezy sysctl.conf is not got loaded on boot time.
> There is bug in debian

This message was sent by Atlassian JIRA

View raw message