Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
The dispatcher should be able to federate events across multiple event specific dispatchers for AM control plane scalability. Add dispatcher specific thread names for easier debugging.
Attachments
Attachments
Issue Links
- is related to
-
TEZ-1789 Move speculator processing off the central dispatcher
- Closed
-
TEZ-1714 Locking issue with StateChangeNotifier
- Resolved
-
TEZ-93 Use central AsyncDispatcher to relay events. Process events on different events based threads.
- Resolved
- relates to
-
TEZ-4501 Fix TestLocalMode timeouts - handle drained in case of InterruptedException
- Resolved
-
TEZ-1195 Remove manual Thread creation from DAGAppMaster and all supporting classes in favor of shared and managed Thread pool (e.g., ExecutorService)
- Open
-
TEZ-1897 Create a concurrent version of AsyncDispatcher
- Closed
-
TEZ-1914 VertexManager logic should not run on the central dispatcher
- Closed