[ https://issues.apache.org/jira/browse/KYLIN-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374047#comment-16374047 ]
Dong Li edited comment on KYLIN-2913 at 2/23/18 7:55 AM: --------------------------------------------------------- Found a critical bug on this patch, if user set job retry number as 1, and kylin.job.retry-exception-classes as empty as default, then all job steps will run 2 times even if the step succeeded, and all Merge job will fail. [~gwang3] please have a look. thanks! was (Author: lidong_sjtu): Found a critical bug on this patch, if user set job retry number as 1, and kylin.job.retry-exception-classes as empty as default, then all job steps will run 2 times, and Merge job will fail. [~gwang3] please have a look. thanks! > Enable job retry for configurable exceptions > -------------------------------------------- > > Key: KYLIN-2913 > URL: https://issues.apache.org/jira/browse/KYLIN-2913 > Project: Kylin > Issue Type: Improvement > Components: Job Engine > Affects Versions: v2.1.0 > Reporter: Wang, Gang > Assignee: Wang, Gang > Priority: Minor > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-2913-Enable-job-retry-for-configurable-excepti.patch > > > In our production environment, we always get some certain exceptions from > Hadoop or HBase, like > "org.apache.kylin.job.exception.NoEnoughReplicationException", > "java.util.ConcurrentModificationException", which results in job failure. > While, these exceptions can be handled by retry actually. So, it will be much > more convenient if we are able to make job retry on some configurable > exceptions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)