17 May
2021
17 May
'21
8:58 a.m.
Hello All, We want to serve read in case of a slow backend and would like the client to retry the read op. mdc_read_super_cb() calls mdcache_kill_entry() if FSAL returns eDelay. This ends up cleaning the state for the file including any byte range locks. Does this mean eDealy is not a valid error for FSAL read? How do I return ERR_FSAL_DELAY from FSAL without losing the state? Thanks in advance for your help! Thanks & Regards, Suhrud