-
Notifications
You must be signed in to change notification settings - Fork 554
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
Revert code added to maintain cephfs mount cache on nodes #824
Comments
if the #282 PR reverted ,the ceph csi driver daemonset plugin existed,caused the pod mount path transport endpoint is not connected error problem can resolved? @ShyamsundarR |
it won't resolve any issue. this code is not working as expected am working on removing the code |
@Madhu-1 really thanks, i want to know that the transport endpoint is not connected error ,the problem is cephfs-fuse client reason? not csi driver reason is right? |
@jianglingxia see #703 (comment) for the more detailed explanation |
closing this one as #825 is merged |
@ShyamsundarR @jianglingxia @Madhu-1 I feel sorry for patch not help, but as PR #282 describe, mount cache patch only work if Pod can restart when csi container exit, it may trigger by health probe check or other similar technology. If Pod not check mount path, mount cache can not help in thhe scenarios. NoGoal Pod should exit and restart when csi plugin pod exit and mount point lost. if pod not exit will get error of transport endpoint is not connected. |
As functionality added by PR #282 for CephFS fuse mounts does not work as intended, from a code maintainability standpoint we should revert this commit or remove the added code.
The text was updated successfully, but these errors were encountered: