[ https://issues.apache.org/jira/browse/TEZ-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513602#comment-14513602 ]
Jeff Zhang commented on TEZ-2226: --------------------------------- I saw the TEZ_DAG_HISTORY_LOGGING is set in the dag's configuration. So it should be able to restore this value when recovering. [~lichangleo] I think you need to update the following code in RecoveryParser.java when recovering from DAGSubmittedEvent. (Also update the skippedDAGs of ATSHistoryLoggingService in this place) {code} case DAG_SUBMITTED: { DAGSubmittedEvent submittedEvent = (DAGSubmittedEvent) event; LOG.info("Recovering from event" + ", eventType=" + eventType + ", event=" + event.toString()); recoveredDAGData.recoveredDAG = dagAppMaster.createDAG(submittedEvent.getDAGPlan(), lastInProgressDAG); recoveredDAGData.cumulativeAdditionalResources = submittedEvent .getCumulativeAdditionalLocalResources(); recoveredDAGData.recoveredDagID = recoveredDAGData.recoveredDAG.getID(); dagAppMaster.setCurrentDAG(recoveredDAGData.recoveredDAG); if (recoveredDAGData.nonRecoverable) { skipAllOtherEvents = true; } break; {code} BTW there's no apache header for HistoryACLPolicyException.java > Disable writing history to timeline if domain creation fails. > ------------------------------------------------------------- > > Key: TEZ-2226 > URL: https://issues.apache.org/jira/browse/TEZ-2226 > Project: Apache Tez > Issue Type: Sub-task > Reporter: Hitesh Shah > Assignee: Chang Li > Priority: Blocker > Attachments: TEZ-2226.10.patch, TEZ-2226.2.patch, TEZ-2226.3.patch, > TEZ-2226.4.patch, TEZ-2226.5.patch, TEZ-2226.6.patch, TEZ-2226.7.patch, > TEZ-2226.8.patch, TEZ-2226.9.patch, TEZ-2226.patch, TEZ-2226.wip.2.patch, > TEZ-2226.wip.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)