[ 
https://issues.apache.org/jira/browse/KYLIN-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ma Gang updated KYLIN-1827:
---------------------------
    Description: Currently mail notification is only sent in the 
onExecuteFinished() method, but no notification will be sent when 
RuntimeException throws, that may cause user miss some important job build 
failure, especially for some automation merge jobs.  Sometimes job state update 
fails(the hbase metastore is unavailable in a short time), it will make the job 
always look like in a running state, but actually it is failed, should send 
mail to notify user.  (was: Currently mail notification only is sent in the 
onExecuteFinished() method, but no notification will be sent when 
RuntimeException throws, that may cause user miss some important job build 
failure, especially for some automation merge jobs.  Sometimes job state update 
fails(the hbase metastore is unavailable in a short time), it will make the job 
always look like in a running state, but actually it is failed, should send 
mail to notify user.)

> Send mail notification when runtime exception throws during build/merge cube
> ----------------------------------------------------------------------------
>
>                 Key: KYLIN-1827
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1827
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Job Engine
>    Affects Versions: v1.5.1, v1.5.2
>            Reporter: Ma Gang
>            Assignee: Ma Gang
>
> Currently mail notification is only sent in the onExecuteFinished() method, 
> but no notification will be sent when RuntimeException throws, that may cause 
> user miss some important job build failure, especially for some automation 
> merge jobs.  Sometimes job state update fails(the hbase metastore is 
> unavailable in a short time), it will make the job always look like in a 
> running state, but actually it is failed, should send mail to notify user.



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

Reply via email to