You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2014/09/10 03:26:29 UTC

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

    [ https://issues.apache.org/jira/browse/TEZ-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127884#comment-14127884 ] 

Bikas Saha commented on TEZ-993:
--------------------------------

[~hitesh] [~zjffdu] Any opinions on the priority of this jira wrt other advanced stuff/testing being done wrt recovery? Testing may not be affected if it considers only the external visible effects of recovery but adding more features to Tez may mean getting this cleaned up will be harder with time.

> 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)