Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
By TEZ-4339, DagClient can expose the sum heap usage by AM and tasks, however, there were 2 separate API endpoints introduced in order to expose those. This can become very verbose in code sooner or later once we want to expose more advanced data. The point is that we don't want to extend the DagClient API every time when we add a single property that is related to the application's memory usage. Currently, protobuf doesn't support map, so a workaround is needed, e.g a prop,value,prop,value serialized list, like:
list: ["am_consumption",value,"tasks_consumption",value,"task_containers_usage",value1:value2:value3,"task_containers_usage_percentage",value1:value2:value3]
Attachments
Issue Links
- is related to
-
TEZ-4339 Expose real-time memory consumption of AM and task containers via DagClient
- Resolved