[
https://issues.apache.org/jira/browse/KYLIN-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wang, Gang updated KYLIN-2913:
------------------------------
Attachment: 0001-KYLIN-2913-Enable-job-retry-for-configurable-excepti.patch
make sense. Resubmit a patch.
Retry will happen in below cases:
1) if property "kylin.job.retry-exception-classes" is not set or is null, all
jobs with exceptions will retry according to the retry times.
2) if property "kylin.job.retry-exception-classes" is set and is not null, only
jobs with the specified exceptions will retry according to the retry times.
> 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
(v6.4.14#64029)
