[KNI] main: configure coalescing PFP recorder #864
Conversation
The recorder by default pushes every new status as long as some capacity constraints are met but it doesn't check whether this status is already reported last. We added option to configure the coalesing on the recorder and by default it is false so we don't limit any client from pushing the same PFPs again. Here we only set this param to true at the begining of the program without need to set it through env var because this is what we expect when the scheduler is recording the statuses. Signed-off-by: Shereen Haj <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: shajmakh The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
|
@shajmakh: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
1 participant
The recorder by default pushes every new status as long as some capacity constraints are met but it doesn't check whether this status is already reported last. We added option to configure the coalesing on the recorder and by default it is false so we don't limit any client from pushing the same PFPs again. Here we only set this param to true at the begining of the program without need to set it through env var because this is what we expect when the scheduler is recording the statuses.