gocrane/crane-scheduler

crane-scheduler日志报错

jiangfeng051 opened this issue · 2 comments

jiangfeng051 commented

k8s: v1.21.5

E0625 08:39:09.924340 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed E0625 08:39:09.924391 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed" pod="dev-app/base-v1-web-5f9b4fb6fc-wqbcl" E0625 08:39:09.940324 1 scheduler.go:379] scheduler cache AssumePod failed: pod 50450750-6476-4e89-8232-f3f756483a11 is in the cache, so can't be assumed E0625 08:39:09.940364 1 factory.go:338] "Error scheduling pod; retrying" err="pod 50450750-6476-4e89-8232-f3f756483a11 is in the cache, so can't be assumed" pod="dev-app/jz-digital-attendance-mobile-web-5f69dd6645-hpgqm" W0625 08:39:23.173299 1 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget E0625 08:40:09.914104 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed E0625 08:40:09.914157 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed" pod="dev-app/xiaofang-auth-admin-web-64bbd7fd4-sct6d" E0625 08:40:39.915075 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed E0625 08:40:39.915127 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed" pod="dev-app/base-v1-web-5f9b4fb6fc-wqbcl" E0625 08:40:39.927121 1 scheduler.go:379] scheduler cache AssumePod failed: pod 50450750-6476-4e89-8232-f3f756483a11 is in the cache, so can't be assumed E0625 08:40:39.927172 1 factory.go:338] "Error scheduling pod; retrying" err="pod 50450750-6476-4e89-8232-f3f756483a11 is in the cache, so can't be assumed" pod="dev-app/jz-digital-attendance-mobile-web-5f69dd6645-hpgqm" E0625 08:41:09.915082 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed E0625 08:41:09.915123 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed" pod="dev-app/xiaofang-auth-admin-web-64bbd7fd4-sct6d" E0625 08:42:09.915837 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed E0625 08:42:09.915879 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed" pod="dev-app/base-v1-web-5f9b4fb6fc-wqbcl" E0625 08:42:09.925737 1 scheduler.go:379] scheduler cache AssumePod failed: pod 50450750-6476-4e89-8232-f3f756483a11 is in the cache, so can't be assumed E0625 08:42:09.925772 1 factory.go:338] "Error scheduling pod; retrying" err="pod 50450750-6476-4e89-8232-f3f756483a11 is in the cache, so can't be assumed" pod="dev-app/jz-digital-attendance-mobile-web-5f69dd6645-hpgqm" E0625 08:42:09.936894 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed E0625 08:42:09.936970 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed" pod="dev-app/xiaofang-auth-admin-web-64bbd7fd4-sct6d" E0625 08:43:09.917671 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed E0625 08:43:09.917714 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed" pod="dev-app/base-v1-web-5f9b4fb6fc-wqbcl" E0625 08:43:39.918409 1 scheduler.go:379] scheduler cache AssumePod failed: pod 50450750-6476-4e89-8232-f3f756483a11 is in the cache, so can't be assumed E0625 08:43:39.918449 1 factory.go:338] "Error scheduling pod; retrying" err="pod 50450750-6476-4e89-8232-f3f756483a11 is in the cache, so can't be assumed" pod="dev-app/jz-digital-attendance-mobile-web-5f69dd6645-hpgqm" E0625 08:43:39.930036 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed E0625 08:43:39.930072 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed" pod="dev-app/xiaofang-auth-admin-web-64bbd7fd4-sct6d" E0625 08:43:50.288516 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed E0625 08:43:50.302026 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed" pod="dev-app/xiaofang-auth-admin-web-64bbd7fd4-sct6d" E0625 08:44:09.919255 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed E0625 08:44:09.919303 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed" pod="dev-app/base-v1-web-5f9b4fb6fc-wqbcl" E0625 08:44:39.920148 1 scheduler.go:379] scheduler cache AssumePod failed: pod 50450750-6476-4e89-8232-f3f756483a11 is in the cache, so can't be assumed E0625 08:44:39.920193 1 factory.go:338] "Error scheduling pod; retrying" err="pod 50450750-6476-4e89-8232-f3f756483a11 is in the cache, so can't be assumed" pod="dev-app/jz-digital-attendance-mobile-web-5f69dd6645-hpgqm" E0625 08:45:09.920842 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed E0625 08:45:09.920881 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0a64a369-5b40-41f3-b354-d056f79b5a81 is in the cache, so can't be assumed" pod="dev-app/xiaofang-auth-admin-web-64bbd7fd4-sct6d" E0625 08:45:09.931887 1 scheduler.go:379] scheduler cache AssumePod failed: pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed E0625 08:45:09.931959 1 factory.go:338] "Error scheduling pod; retrying" err="pod 0ad913e1-30bb-48e7-b563-78ee26bee313 is in the cache, so can't be assumed" pod="dev-app/base-v1-web-5f9b4fb6fc-wqbcl"

qmhu commented

Please provide more informations like your scheduler's config, environment, pod events etc...

jiangfeng051 commented

k8s configmap:
`apiVersion: kubescheduler.config.k8s.io/v1beta1
kind: KubeSchedulerConfiguration
leaderElection:
leaderElect: false
profiles:

  • schedulerName: crane-scheduler
    plugins:
    filter:
    enabled:
    - name: Dynamic
    score:
    enabled:
    - name: Dynamic
    weight: 7
    pluginConfig:
    • name: Dynamic
      args:
      policyConfigPath: /etc/kubernetes/policy.yaml`

`apiVersion: scheduler.policy.crane.io/v1alpha1
kind: DynamicSchedulerPolicy
spec:
syncPolicy:
##cpu usage
- name: cpu_usage_avg_5m
period: 3m
- name: cpu_usage_max_avg_1h
period: 15m
- name: cpu_usage_max_avg_1d
period: 3h
##memory usage
- name: mem_usage_avg_5m
period: 3m
- name: mem_usage_max_avg_1h
period: 15m
- name: mem_usage_max_avg_1d
period: 3h

predicate:
##cpu usage
- name: cpu_usage_avg_5m
maxLimitPecent: 0.65
- name: cpu_usage_max_avg_1h
maxLimitPecent: 0.75
##memory usage
- name: mem_usage_avg_5m
maxLimitPecent: 0.75
- name: mem_usage_max_avg_1h
maxLimitPecent: 0.85

priority:
###score = sum(() * weight) / len, 0 <= score <= 10
##cpu usage
- name: cpu_usage_avg_5m
weight: 0.2
- name: cpu_usage_max_avg_1h
weight: 0.3
- name: cpu_usage_max_avg_1d
weight: 0.5
##memory usage
- name: mem_usage_avg_5m
weight: 0.2
- name: mem_usage_max_avg_1h
weight: 0.3
- name: mem_usage_max_avg_1d
weight: 0.5

hotValue:
- timeRange: 5m
count: 5
- timeRange: 1m
count: 2
`

pod event:
Warning FailedScheduling 59m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed Warning FailedScheduling 57m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed Warning FailedScheduling 56m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed Warning FailedScheduling 55m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed Warning FailedScheduling 54m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed Warning FailedScheduling 53m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed Warning FailedScheduling 52m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed Warning FailedScheduling 50m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed Warning FailedScheduling 50m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed Warning FailedScheduling 49m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed Warning FailedScheduling 48m crane-scheduler pod 9093ad6d-d0b6-435f-b4af-471e145ad179 is in the cache, so can't be assumed