[
https://issues.apache.org/jira/browse/APEXCORE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881653#comment-15881653
]
Sanjay M Pujare commented on APEXCORE-642:
------------------------------------------
Instead of closing this I'll look into passing the failure reason thru the
amRmClient.unregisterApplicationMaster() call that is made from
StreamingAppMasterService.finishApplication(). When an exception is thrown from
serviceInit() we never call unregisterApplicationMaster() so there is no
opportunity to record diagnostics about the failure reason. I'll prototype this
idea and if it works, we'll implement it.
> Catch all exceptions in StreamingAppMasterService.serviceInit() and create a
> StramEvent
> ---------------------------------------------------------------------------------------
>
> Key: APEXCORE-642
> URL: https://issues.apache.org/jira/browse/APEXCORE-642
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Sanjay M Pujare
> Assignee: Sanjay M Pujare
> Priority: Minor
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> When the AM (Stram) starts, it executes
> StreamingAppMasterService.serviceInit() to perform service initialization as
> per the Hadoop service contract. In this, the Stram deserializes the DAG
> which can fail (e.g. bad jar versions or other deserialization issues) and
> any exception is thrown is not logged in Apex log files or events. It is
> proposed to catch these exceptions and log them to the dt log file as well as
> Stram events so the Apex user knows about these exceptions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
