[jira] [Commented] (TEZ-992) Recovery data should not be written on AsyncDispatcher thread

["Bikas Saha (JIRA)" <ji...@apache.org>]

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

Bikas Saha commented on TEZ-992:
--------------------------------

[~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. Also this can have functional implications because of a slow dispatcher thread.

> Recovery data should not be written on AsyncDispatcher thread
> -------------------------------------------------------------
>
>                 Key: TEZ-992
>                 URL: https://issues.apache.org/jira/browse/TEZ-992
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>
> This may block the DAG operations in case the recovery data needs to be synchronously stored. The operations requiring this blocking operation should change their state machines to wait for the store operation before moving ahead. They will move ahead after they receive notification from the RecoveryService that their operation has completed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)