[
https://issues.apache.org/jira/browse/GOBBLIN-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hung Tran resolved GOBBLIN-1101.
--------------------------------
Fix Version/s: 0.15.0
Resolution: Fixed
Issue resolved by pull request #2942
[https://github.com/apache/incubator-gobblin/pull/2942]
> Enhance bulk api retry for ExceedQuota
> --------------------------------------
>
> Key: GOBBLIN-1101
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1101
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: Alex Li
> Priority: Major
> Fix For: 0.15.0
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> 1. ExceedQuota exception
> Below is SFDC doc about ExceedQuota
> {code:java}
> One of the limits customers frequently reach is the concurrent request limit.
> Once a synchronous Apex request runs longer than 5 seconds, it begins
> counting against this limit. Each organization is allowed 10 concurrent
> long-running requests. If the limit is reached, any new synchronous Apex
> request results in a runtime exception. This behavior occurs until the
> organization’s requests are below the limit.
> {code}
> If the ExceedQuota exception happens, we should let the thread sleep 5
> minutes and try again. There should not be a retryLimit for this exception.
> 2. Except stack in log file
> For example we set up retryLimit to 10, we retried 10 times, and failed; we
> need to print out exception stack in log file, there are 10 of them in the
> exception stack.
> SSL Exception(root cause) ----retry and get ----> ExceedQuota ----retry and
> get ----> ExceedQuota ----....a lot........ ---->
> We'd better skip all the retry exception, only keep the root cause exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
