[
https://issues.apache.org/jira/browse/APEXCORE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863171#comment-15863171
]
Sanjay M Pujare commented on APEXCORE-642:
------------------------------------------
I investigated this more and noticed a problem for the test case I tried. The
test case had conflicting hadoop libraries which caused "Class or method not
found" exception. This caused the DAG to be not constructed and an exception is
thrown directly from
this.dag = LogicalPlan.read(fis);
which is only caught in main(). A number of objects required for even recording
are not constructed (such as StreamingContainerManager, FSEventRecorder) so it
is difficult to record the event.
I can investigate an alternative solution of creating an FSEventRecorder object
where the exception is caught in main, get the DTFS root directory somehow and
then record the event synchronously before exiting the process. If this
approach is not feasible, I'll just close the JIRA.
> 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)
