[ https://issues.apache.org/jira/browse/TEZ-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995117#comment-14995117 ]
Jeff Zhang commented on TEZ-2581: --------------------------------- bq. Alternatively, we could put the faking logic into NoOpVertexManager and based on -1 tasks it could self trigger internally and call setParallelism/reconfigureVertex with real data. This is option 3). [~bikassaha], thanks for the patient explanation. I'm afraid setParallelism/reconfigureVertex can only be called when vertex it in initializing/running. Seems VM has not way to query the state of vertex to trigger the call of setParallelism/reconfigureVertex . So I will try to implement the option 4 to get vertex state change notification from Vertex > Umbrella for Tez Recovery Redesign > ---------------------------------- > > Key: TEZ-2581 > URL: https://issues.apache.org/jira/browse/TEZ-2581 > Project: Apache Tez > Issue Type: Improvement > Reporter: Jeff Zhang > Assignee: Jeff Zhang > Attachments: TEZ-2581-WIP-1.patch, TEZ-2581-WIP-10.patch, > TEZ-2581-WIP-2.patch, TEZ-2581-WIP-3.patch, TEZ-2581-WIP-4.patch, > TEZ-2581-WIP-5.patch, TEZ-2581-WIP-6.patch, TEZ-2581-WIP-7.patch, > TEZ-2581-WIP-8.patch, TEZ-2581-WIP-9.patch, TezRecoveryRedesignProposal.pdf, > TezRecoveryRedesignV1.1.pdf > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)