Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.0.0, trunk
-
None
Description
Background
As part of entity creation, Atlas sends notifications of different types. Current implementation, to listeners. Listeners in turn perform specific tasks.
At a more concrete level, the EntityAuditListenerV2 will write audits and the NotificationEntityChangeListener will send Kafka notifications.
Each of the listeners create notification objects. The notification objects are large in number and are short lived.
The transient nature of the notification objects causes memory pressure in scale environment.
Solution
Create object pool for notification objects. This way objects can be reused.and existing design can be kept in tact. This will also offer benefit of using existing test setup for verification.
Tests Used
Setup
Create a test rig that will spawn multiple works that will invoke Atlas' bulk APIs for entity creation.
Node: 40 workers, 8 GB allocated memory and 40 cores.
Observation
About 40 mins into the exercise, memory pressure builds up causing GC collects to take longer. This causes ZK timeout and finally Atlas process crashes.
Attachments
Attachments
Issue Links
- links to
