b64e5b2d15
The reason for the issue is that the metrics were bumped before the final job status update. In case the update failed the path was repeated by the next syncJob leading to double-counting of the metrics. The solution is to delay recording metrics and broadcasting events after the job status update succeeds. |
||
|---|---|---|
| .. | ||
| config | ||
| metrics | ||
| doc.go | ||
| indexed_job_utils_test.go | ||
| indexed_job_utils.go | ||
| job_controller_test.go | ||
| job_controller.go | ||
| OWNERS | ||
| pod_failure_policy_test.go | ||
| pod_failure_policy.go | ||
| tracking_utils_test.go | ||
| tracking_utils.go | ||
| utils_test.go | ||
| utils.go | ||