mds: blocklist clients with "bloated" session metadata#52944
mds: blocklist clients with "bloated" session metadata#52944
Conversation
batrick
left a comment
There was a problem hiding this comment.
I think a PendingReleaseNote would be appropriate.
It'd also be good if we had some kind of cluster warning about this. Maybe add a message parameter to evict_client so it can issue the cluster warning (I'm not sure SessionMap.cc can do it easily).
|
@vshankar the comments are yet to be addressed right? |
Pushing an update (I mark it resolved before an update just for my sanity). |
|
Added note in PendingReleaseNotes. |
robbat2
left a comment
There was a problem hiding this comment.
approving as some of the original users affected by this. Minor ask, not-critical: having a perf metric about how many sessions exceeded the threshold would be valuable.
Good idea. I'll include this and push an update. |
Buggy clients (or maybe a MDS bug) causes a huge buildup of `completed_requests` metadata in its session information. This could cause the MDS to go read-only when its flushing session metadata to the journal since the bloated metadata causes the ODSOp payload to exceed the maximum write size. Blocklist such clients so as to allow the MDS to continue servicing requests. Fixes: http://tracker.ceph.com/issues/61947 Signed-off-by: Venky Shankar <vshankar@redhat.com>
…data threshold being exceeded Signed-off-by: Venky Shankar <vshankar@redhat.com>
... when its session metadata is bloated due to buildup of `completed_requests`. Signed-off-by: Venky Shankar <vshankar@redhat.com>
…mds config Signed-off-by: Venky Shankar <vshankar@redhat.com>
|
fixed and updated. |
|
fs suite test results - https://pulpito.ceph.com/vshankar-2023-08-22_10:18:46-fs-wip-vshankar-testing-20230822.064807-testing-default-smithi/ will go through the run list tomorrow and do the needful. |
Test run looks fine - no failures related to this change. I'll merge this shortly. |
|
jenkins test api |
|
@vshankar Hi~ |
Fixes: http://tracker.ceph.com/issues/61947
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows