Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

[pure k8s] K8s's pod eviction may not trigger when job container uses too much disk space #3765

Closed
wangdian opened this issue Oct 23, 2019 · 1 comment
Assignees
Labels

Comments

@wangdian
Copy link
Member

K8s's pod eviction may not trigger when job container uses too much disk space.

According to k8s doc, there are two fs partitions that kubelet supports:

  1. The nodefs filesystem that kubelet uses for volumes, daemon logs, etc.
  2. The imagefs filesystem that container runtimes uses for storing images and container writable layers.

The imagefs limit is optional, so it may not configured by default. The result is if nodefs and imagefs are different, k8s may not evict pod that consumes large disk space.

Plus, if a pod is evicted by k8s, PAI treat it as system failure and retry without increase retry count. The job will always retry.

@fanyangCS
Copy link
Contributor

closed and tracked in #4694?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants