Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Attachments
Issue Links
- relates to
-
TEZ-2316 Log count of different events if eventQueue has lot of events
- Open
-
TEZ-2317 Event processing backlog can result in task failures for short tasks
- Closed
-
TEZ-2325 Route status update event directly to the attempt
- Closed
-
TEZ-1897 Create a concurrent version of AsyncDispatcher
- Closed
1.
|
Optionally send user payload as local resource if user payload if large | Open | Unassigned | |
2.
|
Investigate : skip user paylaod for same-vertex tasks when container re-use is used | Open | Unassigned | |
3.
|
Avoid creating multiple copies of the same Event payload | Closed | Siddharth Seth | |
4.
|
Re-use ID instances in the AM, intern vertex names etc where possible | Closed | Siddharth Seth | |
5.
|
Reduce AM mem usage caused by storing TezEvents | Closed | Bikas Saha | |
6.
|
Avoid re-sending TaskContext more than once to the same node | Open | Unassigned | |
7.
|
Dynamic heartbeat intervals between RM and AM | Resolved | Unassigned | |
8.
|
Dynamic heartbeat intervals between task and AM | Open | Unassigned | |
9.
|
The AM-RM heartbeat interval should not be static | Reopened | Unassigned | |
10.
|
Offload DataMovement event creation from the AM to the tasks | Open | Bikas Saha |