Details
-
Bug
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Distinct from TEZ-3815, since even with a hack that makes plugins aware of each other, they cannot store task-specific info without calling into each others' per-task structures.
In particular, I need a piece of info that is generated when the custom scheduler calls getContext().taskAllocated, to be propagated to communicator plugin registerRunningTaskAttempt, so that the custom communicator could include additional info in task submission (e.g. a scheduler-specific priority or other instructions). There doesn't seem to be any means to do it now.
