-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pods restart because their log volume exceeds its limit #620
Comments
Observations with ZooKeeper 3.8.1 in a local kind cluster: The log file rollover works as desired:
The logs of the prepare container used 515 Bytes. A total of 10,488,112 Bytes were used which means, nearly 1 MiB (1,046,224 Bytes) were unused. If the size limit of the log volume is set to 2 MiB then the Pod is evicted with the shown error message when the log file exceeds 2,300,856 Bytes (~ 2.2 MiB). So the size limit is checked in a kind cluster. Possible explanations for the behavior in OpenShift:
|
The issue can be reproduced on our OpenShift cluster. The problem is that the disk usage per log file is not just |
Pods restart because their log volume exceeds its limit:
This was observed in an OpenShift cluster for ZooKeeper 3.8.0 and HBase.
The text was updated successfully, but these errors were encountered: