You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2015/01/30 08:22:35 UTC

[jira] [Updated] (TEZ-993) Remove application logic from RecoveryService

     [ https://issues.apache.org/jira/browse/TEZ-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Zhang updated TEZ-993:
---------------------------
    Attachment: TEZ-993-4.patch

Rebase the patch.

> 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
>            Assignee: Jeff Zhang
>         Attachments: TEZ-993-3.patch, TEZ-993-4.patch, Tez-993-2.patch, Tez-993.patch
>
>
> 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)