-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Process bundle batch in parallel #2905
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2905 +/- ##
============================================
- Coverage 82.58% 82.57% -0.02%
+ Complexity 19723 19720 -3
============================================
Files 1327 1327
Lines 70182 70228 +46
Branches 10736 10740 +4
============================================
+ Hits 57959 57989 +30
- Misses 8102 8115 +13
- Partials 4121 4124 +3
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
//myExecutor.setMaxPoolSize(1); | ||
myExecutor.setCorePoolSize(myDaoConfig.getBundleBatchPoolSize()); | ||
myExecutor.setMaxPoolSize(myDaoConfig.getBundleBatchMaxPoolSize()); | ||
myExecutor.setQueueCapacity(myDaoConfig.getBundleBatchQueueCapacity()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need the complexity of a queue? The main thread will wait for these to complete, so I wonder if we could delete this config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will delete this config
|
||
myVersionAdapter.setResponseStatus(nextEntry, toStatusString(caughtEx.getException().getStatusCode())); | ||
// waiting for all tasks to be completed | ||
AsyncUtil.awaitLatchAndIgnoreInterrupt(completionLatch, 120L, TimeUnit.SECONDS); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we already have a request timeout configured somewhere? This feels too short for some customers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a connection timeout for 10000 milliseconds (10s). I can't find any other timeout value. The value here is 120s (2m). I can change it to 5m (300s).
No description provided.