-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Dedupe logging for PD SetUpAt and added a slow SetVolumeOwnership warning #83426
Conversation
51194ce
to
ddbff58
Compare
/retest |
@@ -412,35 +410,31 @@ func (b *gcePersistentDiskMounter) SetUpAt(dir string, mounterArgs volume.Mounte | |||
if err != nil { | |||
notMnt, mntErr := b.mounter.IsLikelyNotMountPoint(dir) | |||
if mntErr != nil { | |||
klog.Errorf("IsLikelyNotMountPoint check failed: %v", mntErr) | |||
return err | |||
return fmt.Errorf("failed to mount: %v. Cleanup IsLikelyNotMountPoint check failed: %v", err, mntErr) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not your change. but I am wondering whether it is necessary to check IsLikelyNotMountPoint multiple times. If mount failed, is it better we just try to unmount (maybe a few times) and then try to remove dir.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is outside of the scope of this PR and I won't change it. Feel free to create an issue :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I opened an issue here #83515
ddbff58
to
223ef76
Compare
@jingxu97 resolved comments |
/lgtm |
ping @msau42 for approval :) |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidz627, msau42 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
SetUpAt
errors actually bubble up to theoperation_generator
level and are logged in a much better way with more context. The one-off logs are duplicates and split context in different places.Also we have a known issue with volume ownership being slow and it would be nice to surface a warning when this feature is being used. This would make debugging the issue much easier.
/kind cleanup
/sig storage
/assign @msau42 @jingxu97
/priority backlog