Add option to choose the scan_tree()
implementation in the NetApp backend
#1975
Labels
area:upstream
Issues with root cause from upstream 3rd parties
comp:storage-proxy
Related to Storage proxy component
effort:easy
Need to understand only a specific region of codes (good first issue, easy).
type:enhance
Enhance component, behavior, internals without user-facing features
urgency:3
Must be finished within a certain time frame.
Milestone
In some customer setups, running the NetApp's XCP executable is too slow, incurring 2-3 seconds of delays whenever storage-proxy tries to scan the directory contents (list of files) regardless of how many files are there.
Since directory listing is a frequently invoked operation in the storage folder management UI, it should be fast.
Unfortunately it seems not easy to reduce the XCP invocation latency. Let's add an opt-out flag (e.g.,
netapp_xcp_exclude_scan_tree
) to the NetApp storage plugin's configuration about whether to use XCP-basedscan_tree()
implementation forXCPFSOpModel
or the vanillascan_tree()
implementation from the super-class,BaseFSOpModel
.The text was updated successfully, but these errors were encountered: