From e1c23e962885a2b4ae0d8ed9198a702435e797ab Mon Sep 17 00:00:00 2001 From: ddongchen Date: Wed, 5 Apr 2017 02:48:48 -0400 Subject: [PATCH] fix scheduling metrics error for E2eSchedulingLatency If we get the scheduling metrics, which is "SchedulingAlgorithmLatency, E2eSchedulingLatency, BindingLatency". The E2eSchedulingLatency should be the sum of SchedulingAlgorithmLatency and BindingLatency, while we found E2eSchedulingLatency is almost the same as E2eSchedulingLatency for some optimization. --- plugin/pkg/scheduler/scheduler.go | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/plugin/pkg/scheduler/scheduler.go b/plugin/pkg/scheduler/scheduler.go index 84bc88f1587..d53f35baf29 100644 --- a/plugin/pkg/scheduler/scheduler.go +++ b/plugin/pkg/scheduler/scheduler.go @@ -205,7 +205,9 @@ func (sched *Scheduler) scheduleOne() { } go func() { - defer metrics.E2eSchedulingLatency.Observe(metrics.SinceInMicroseconds(start)) + defer func() { + metrics.E2eSchedulingLatency.Observe(metrics.SinceInMicroseconds(start)) + }() b := &v1.Binding{ ObjectMeta: metav1.ObjectMeta{Namespace: pod.Namespace, Name: pod.Name},