Bug #23394
closed
nfs-ganesha: check cache configuration when exporting FSAL_CEPH
Added by Patrick Donnelly about 6 years ago.
Updated almost 6 years ago.
Category:
Administration/Usability
Component(FS):
Ganesha FSAL
Description
NFS Ganesha should check that caching is disabled when exporting FSAL_CEPH. If misconfigured, it should raise an error and quit.
I don't think we should do this. We have settings that we recommend, but not using those doesn't mean that anything is broken.
For instance, someone may want to use an attribute cache to get better (perceived) performance, if their applications can tolerate less cache coherency. This would prevent anyone from even experimenting with those settings.
If we have something that is really a problem, we should just autoadjust it when starting (and maybe throw a LOG_NOTICE level message or something).
The default should be the safe/efficient configuration and we should make an attempt to either fix it automatically or quit with an error. If we want to allow for testing Ganesha cache settings, then let's add another configuration variable for "CephFS_Allow_Unsafe_Caching" or something?
- Status changed from New to Rejected
Also available in: Atom
PDF