-
Notifications
You must be signed in to change notification settings - Fork 553
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
Syslog / kubelet logs cluttered with gRPC messages #2410
Comments
The Could you update your containers:
- name: driver-registrar
image: k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.2.0
args:
- "--v=5"
- "--csi-address=/csi/csi.sock"
- "--kubelet-registration-path=/var/lib/kubelet/plugins/rbd.csi.ceph.com/csi.sock" to containers:
- name: driver-registrar
image: k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.2.0
args:
- "--v=5"
- "--csi-address=/csi/csi.sock"
- "--kubelet-registration-path=unix:///var/lib/kubelet/plugins/rbd.csi.ceph.com/csi.sock" So, prefixing the |
@nixpanic are you working on this one? |
@nixpanic Thanks for getting back on this! I could only briefly test without checking out any details yet.
|
Looking at https://github.com/grpc/grpc-go/blob/master/clientconn.go#L251-L268 it might work to reduce |
Thanks for testing @pehlert! I think the Is that something you can try out easily? |
@pehlert can you also try |
the open issue already exists at kubernetes-csi/node-driver-registrar#88 |
I tried this and while the pod came up just fine and seemingly worked as expected, it didn't have any effect on the warnings. |
@pehlert does decreasing the log level helps? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation. |
Describe the bug
On all our nodes that run ceph-csi, we observe a high number of log messages (every few seconds), seemingly from gRPC that attempts to collect to the Ceph CSI socket.
Example:
Environment details
fuse
orkernel
. for rbd itskrbd
orrbd-nbd
) : defaultsExpected behavior
These seemingly harmless warnings make the identification of actual errors in the logs much harder and result in unnecessary disk io. They shouldn't be logged when they don't indicate an actual issue.
The text was updated successfully, but these errors were encountered: