[
https://issues.apache.org/jira/browse/YUNIKORN-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167188#comment-17167188
]
Adam Antal commented on YUNIKORN-331:
-------------------------------------
Oh I found the following entry flooding the scheduler logs:
{noformat}
2020-07-29T14:22:53.859+0200 DEBUG scheduler/scheduling_application.go:641
skipping node for allocation: basic condition not satisfied {"node":
"docker-desktop", "allocationKey": "ad8c8ff7-84a3-49f5-9116-9e5e64aaf811",
"error": "pre alloc check: requested resource map[memory:2000 vcore:2000] is
larger than currently available map[ephemeral-storage:75850798569
hugepages-1Gi:0 hugepages-2Mi:0 memory:6423 pods:110 vcore:1250] resource on
docker-desktop"}
2020-07-29T14:22:53.860+0200 DEBUG scheduler/scheduling_node.go:271
requested resource is larger than currently available node resources
{"nodeID": "docker-desktop", "requested": "map[memory:2000 vcore:2000]",
"available": "map[ephemeral-storage:75850798569 hugepages-1Gi:0 hugepages-2Mi:0
memory:6423 pods:110 vcore:1250]"}
2020-07-29T14:22:53.860+0200 DEBUG scheduler/scheduling_application.go:641
skipping node for allocation: basic condition not satisfied {"node":
"docker-desktop", "allocationKey": "ad8c8ff7-84a3-49f5-9116-9e5e64aaf811",
"error": "pre alloc check: requested resource map[memory:2000 vcore:2000] is
larger than currently available map[ephemeral-storage:75850798569
hugepages-1Gi:0 hugepages-2Mi:0 memory:6423 pods:110 vcore:1250] resource on
docker-desktop"}
2020-07-29T14:22:53.860+0200 DEBUG scheduler/scheduling_node.go:271
requested resource is larger than currently available node resources
{"nodeID": "docker-desktop", "requested": "map[memory:2000 vcore:2000]",
"available": "map[ephemeral-storage:75850798569 hugepages-1Gi:0 hugepages-2Mi:0
memory:6423 pods:110 vcore:1250]"}
2020-07-29T14:22:53.860+0200 DEBUG scheduler/scheduling_application.go:641
skipping node for allocation: basic condition not satisfied {"node":
"docker-desktop", "allocationKey": "ad8c8ff7-84a3-49f5-9116-9e5e64aaf811",
"error": "pre alloc check: requested resource map[memory:2000 vcore:2000] is
larger than currently available map[ephemeral-storage:75850798569
hugepages-1Gi:0 hugepages-2Mi:0 memory:6423 pods:110 vcore:1250] resource on
docker-desktop"}
2020-07-29T14:22:53.860+0200 DEBUG scheduler/scheduling_node.go:271
requested resource is larger than currently available node resources
{"nodeID": "docker-desktop", "requested": "map[memory:2000 vcore:2000]",
"available": "map[ephemeral-storage:75850798569 hugepages-1Gi:0 hugepages-2Mi:0
memory:6423 pods:110 vcore:1250]"}
...
{noformat}
I think we should get rid of this log piece.
> Reduce the number of log records related to the event mechanism
> ---------------------------------------------------------------
>
> Key: YUNIKORN-331
> URL: https://issues.apache.org/jira/browse/YUNIKORN-331
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Major
>
> Currently the shim publishes pod events whenever there is a predicate
> evaluation failure. This is not efficient, we usually can see huge number of
> times that events got logged. We need to reduce the overhead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
