Shlomi Reiss reopened HHQ-5823:
-
The additional disk space didnt help, system crashed after a while.
Large scale setup should run with 200 GB Disk
vApp large scale : at max scale - DB is crashing after few days of running because disk becomes full.
-----------------------------------------------------------------------------------------------------
Key: HHQ-5823
URL: https://jira.hyperic.com/browse/HHQ-5823
Project: Hyperic HQ
Issue Type: Bug
Components: Core Monitoring
Affects Versions: 5.7
Reporter: Shlomi Reiss
Assignee: Shlomi Reiss
Priority: Critical
Fix For: 5.7
>
Scenario :
1. Scale setup installed on a vapp is running for few days (3-4) with 2K agents.
Result:
Server is not responsive. Looking at the logs i see that this is a DB issue.
DB is not responding and showing the following in its logs :
"could not write to log file: No space left on device"
localhost:/opt/vmware/vpostgres/current/logs # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 58G 55G 0 100% /
udev 5.9G 84K 5.9G 1% /dev
tmpfs 5.9G 0 5.9G 0% /dev/shm
/dev/sda1 1012M 46M 915M 5% /boot
Disk size for large scale should be increased. The current disk size of 55 GB looks too low.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.hyperic.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira