[
https://issues.apache.org/jira/browse/TEZ-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135120#comment-14135120
]
Jeff Zhang commented on TEZ-993:
--------------------------------
Start working on this.
After some investigation, get some rough ideas.
* Create a new Abstract class RecoveryStore which wrap 2 interface :
RecoveryReader & RecoveryWrite. This component will be responsible for the the
reader & write of recovery log.
* Move the recovery read/write operation from RecoveryService & RecoveryParser
into RecoveryStore. And keep the application logic in RecoveryService &
RecoveryParser.
> Remove application logic from RecoveryService
> ---------------------------------------------
>
> Key: TEZ-993
> URL: https://issues.apache.org/jira/browse/TEZ-993
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
>
> Currently RecoveryService storage logic knows a lot about the DAG like which
> dag is pre-warm and does not need to be stored, which events needs special
> treatment etc. This kind of logic couples the DAG and the storage more than
> is probably necessary and can be a source of complications down the road. The
> storage should ideally be simply storing a sequence of arbitrary records
> delimited by a marker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
