[TEZ-2020] For 1-1 edge vertex configured event may be sent incorrectly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.5.4
• Hadoop Flags: Reviewed
• Assignee: Bikas Saha
• Reporter: Bikas Saha
• Created: 31/Jan/15 22:12
• Updated: 30/Jun/15 04:53
• Resolved: 05/Feb/15 03:58

Description

For a fully configured 1-1 vertex configured event will be sent after init because the vertex manager does not signal intent to reconfigure. However a change in parallelism upstream on the 1-1 edge can cause this vertex's parallelism to be updated accordingly. This breaks the guarantee that configured should be sent after vertex is fully configured. This is because update of parallelism on 1-1 edge has until now been hard-coded in the Vertex code. This can be removed now with the InputReadyVertexManager handling the 1-1 edge and the addition of vertex state updates. Not only will this fix the issue but also remove the special handling for 1-1 edges in the AM which should not be there for cleanliness.

Issue Links

• is related to: TEZ-1059 Generalize change in connected vertices when the parallelism of a vertex changes
• is related to: TEZ-2011 InputReadyVertexManager not resilient to updates in parallelism