cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koushik Das (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-5205) System vm startup scripts calculate jvm memory wrong
Date Wed, 04 Jun 2014 09:28:01 GMT

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

Koushik Das updated CLOUDSTACK-5205:
------------------------------------

    Fix Version/s: 4.3.0

> System vm startup scripts calculate jvm memory wrong
> ----------------------------------------------------
>
>                 Key: CLOUDSTACK-5205
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5205
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: SystemVM
>    Affects Versions: 4.2.0
>            Reporter: John E Vincent
>            Assignee: Koushik Das
>             Fix For: 4.3.0, 4.4.0
>
>
> While attempting to provision beefier system vms, we discovered this bug.
> The `_run.sh` script in the system vm calculates jvm memory based on 80% of the total
memory on the system. This is great up until the point 80% of memory goes above ~1.9G. The
system vm templates are all 32-bit and so calculating the size too high will cause the agent
jvm to fail to start.
> The fix is pretty simple with a final sanity check:
> 	if [ $maxmem -gt 1900 ]
> 	then
> 	  maxmem=1900
> 	fi



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message