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

Marcus Sorensen commented on CLOUDSTACK-1339:
---------------------------------------------

75% memory, sounds like it could be driving you to swap, depending on what else 
the server is doing. That would cause the unresponsiveness you mention, and 
would be easy to diagnose as such. Again, what sort of hardware is this being 
seen on? What does /proc/meminfo look like when the issue is seen? Fortunately 
this is also easy to test by changing your tomcat6.conf as mentioned.

It sounds like we will probably need to discuss what sort of memory 
requirements are necessary and should be set as a standard. They have increased 
with Javelin, but I'm not sure if anyone knows what the minimum acceptable is, 
the old settings were running people out of memory, and it sounds like the 
current settings may be overwhelming your test systems.

The recommendations per the Javelin e-mails was 2g heap and 512M perm, if we 
stick to that, then it means that we probably want to set the minimum 
requirements for management server as one with 4GB of RAM. Alternatively, we 
can find a lower setting that is acceptable and doesn't trigger out of memory 
errors after running awhile, or somehow reduce the actual memory footprint.
                
> ASF 4.1: Management server becomes unresponsive
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-1339
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1339
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>            Reporter: Srikanteswararao Talluri
>            Assignee: Prachi Damle
>            Priority: Blocker
>             Fix For: 4.1.0
>
>         Attachments: MS_log.txt
>
>
> management server becomes unresponsive after running for a while and after 
> some time the process shuts down.
> This is blocking the testing 
> logs can be found @ https://citrix.sharefile.com/d/sa684d7a73fb45ba8

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