Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
It sets up its internal book-keeping upon onVertexStarted() but that book-keeping can be wrong if its parallelism changes after that. It needs to subscribe to Vertex configured event for its source vertices to make sure that all changes have been made before initializing its internal state.
Attachments
Attachments
Issue Links
- relates to
-
TEZ-2020 For 1-1 edge vertex configured event may be sent incorrectly
- Closed
The patch changes the InputReady manager to wait for CONFIGURED signal from all source vertices and its own vertex to start before taking any action. Thus any changes in parallelism in those vertices will take effect before its data structures are initialized and so the calculations will be correct. The logic is essentially the same as before but delayed till all configured signals are received.
Updated tests for different cases. rajesh.balamohan Please review. Currently this is not an issue since the AM is essentially locked on the central dispatcher. But after
TEZ-1914this may be an issue.