You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 9, 2020. It is now read-only.
You can't read logs out of deleted pods but you can read logs out of completed pods. Completed pods are also reaped when their count exceeds a threshold so it's ok to have large numbers of completed pods -- we don't need to worry about deleting them to clear up disk space from logs (untested but believed to be standard k8s behavior).
This issue is to change the way to clean up executor pods from deleting them to instead having them complete (the JVM process exits cleanly) to preserve the logs.
Logs are accessible with: kubectl logs <pod-name>
The text was updated successfully, but these errors were encountered:
You can't read logs out of deleted pods but you can read logs out of completed pods. Completed pods are also reaped when their count exceeds a threshold so it's ok to have large numbers of completed pods -- we don't need to worry about deleting them to clear up disk space from logs (untested but believed to be standard k8s behavior).
This issue is to change the way to clean up executor pods from deleting them to instead having them complete (the JVM process exits cleanly) to preserve the logs.
Logs are accessible with:
kubectl logs <pod-name>
The text was updated successfully, but these errors were encountered: