Optimize ack messages for setups not collecting logs #4699
Optimize ack messages for setups not collecting logs #4699tysonnorris merged 5 commits intoapache:masterfrom
Conversation
|
Following test cases cover all the above 4 permutations |
| } | ||
|
|
||
| val logsToBeCollected = collectLogs.logsToBeCollected(job.action) | ||
| val sendCompletionAfterLogsCollection = logsToBeCollected == true |
There was a problem hiding this comment.
instead of defining these two values which are essentially the same (value), how about just defining one value with this name and using it accordingly splitAckMessagesPendingLogCollection?
There was a problem hiding this comment.
Naming is very hard so thanks for the suggestion :). Updated PR
|
Did this go out to the dev list - I haven't checked. |
|
Initiated a mail thread today for this |
Codecov Report
@@ Coverage Diff @@
## master #4699 +/- ##
==========================================
- Coverage 84.8% 78.35% -6.45%
==========================================
Files 196 198 +2
Lines 8803 8812 +9
Branches 603 598 -5
==========================================
- Hits 7465 6905 -560
- Misses 1338 1907 +569
Continue to review full report at Codecov.
|
|
Thanks @chetanmeh ! |
Optimizes the ack message flow of setups which collect logs out of band i.e. where logs are not collected as part of activation message processing itself.
Fixes #4635
Description
Changes the
ContainerProxyactive ack flow whenjob.action.limits.logs.asMegaBytes == 0.MBLogDriverLogStoreis being usedNow the behaviour is
CombinedCompletionAndResultMessagedirectlyCompletionMessagedirectlyResultMessageCompletionMessageCompletionMessageRelated issue and scope
My changes affect the following components
Types of changes
Checklist: