[
https://issues.apache.org/jira/browse/TEZ-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505423#comment-14505423
]
Hitesh Shah commented on TEZ-2292:
----------------------------------
bq. Further, if users catch and swallow these exceptions then it may lead to
the state machines being left behind in an invalid state and weird errors down
the line. This is probably why originally the exceptions were all unchecked.
In some cases, this may be true but it all depends on whether the user plugin
can do anything to recover from its error. In any case, a plugin could be
catching all RuntimeExceptions too which leads us back to the same problem. The
issue holds whether there is a checked or an unchecked exception. I am not sure
we can do much if there is a "bad" vertex manager plugin.
> Add e2e test for error reporting when vertex manager invokes plugin APIs
> ------------------------------------------------------------------------
>
> Key: TEZ-2292
> URL: https://issues.apache.org/jira/browse/TEZ-2292
> Project: Apache Tez
> Issue Type: Task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: TEZ-2292.1.patch
>
>
> If the Vertex Manager has an error or cannot apply a required reconfiguration
> then it should be allowed to fail the vertex.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
