support fuse resend API for live upgrade and failover

[imeoer]

This issue aims to implement request resend for the fuse-backend-rs lib and the nydusd live upgrade and failover, ensuring the fuse requests are resent after nydusd(fuse daemon) recovery, thereby avoiding interruptions in fuse io request processing.

[X1aoZEOuO]

Hello, I would like to participate in this GLCC project. Could you please provide some detailed scenarios?

Currently, my understanding of the project is that it requires persisting requests received by the FUSE Daemon (e.g., logging them), and then, when reloading the FUSE Daemon, continuing the previous FUSE requests based on the logs. However, I feel this might reduce the throughput of FUSE requests. Is this approach correct? Additionally, where in the code for fuse-backend-rs and Nydus should I focus my reading? I would like to study this further.

[imeoer]

Hi @X1aoZEOuO Plz take a look the new FUSE notify API for request resend here.

[X1aoZEOuO]

Hi @X1aoZEOuO Plz take a look the new FUSE notify API for request resend here.

Thank you, I will take a deep look at it.

[github-actions]

This issue is stale because it has been open 60 days with no activity.