-
Change Request
-
Resolution: Fixed
-
Low
-
6.0.33rc1, 6.4.18rc1, 7.0.4rc1, 7.2.0alpha1
-
None
-
vmware events
-
S24-W38/39, S24-W40/41, S24-W42/43, S24-W44/45
-
2
The huge amount of vmware event can lead server to crash due to out of memory (not shared memory).
Proposal:
- check the available size of shared memory
- load from vc number of events not more than available shared memory
- set eventlog.last_key to the last event of current "page". It will be used in next iteration.
Cons:
This is lead to permanent reading all vc events from "new" to actual "page"
- caused by
-
ZBXNEXT-9145 VMware: increase speed of eventlog retrieval (problem detection)
- Closed
- causes
-
ZBX-25584 VMWare collector processes at 100% utilization since upgrade to 7.0.6
- Ready for QA
- duplicates
-
ZBX-25213 Postponed VMware events requires up to xx bytes of free VMwareCache memory. Reading events skipped
- Reopened