[LU-10275] ptlrpc reply acknowledgement

• Type: New Feature
• Resolution: Unresolved
• Priority: Minor
• Labels: lnet performance
• Assignee: Amir Shehata (Inactive)
• Reporter: Liang Zhen (Inactive)

Description

Because most ptlrpc messages do not have ACK , RPC client cannot distinguish message loss from long service time. Also, in current implementation, message-resend can only be triggered by RPC client after service timeout, no matter which message is lost in lifecycle of RPC.

To improve Lustre RAS against message loss, we should allow message resend for any step of RPC lifecycle. However, current RPC client already has request message timeout/resend protocol and adaptive timeout, it may need fundamental changes if we want to have ACK for request message and use network timeout instead of service time to trigger request message resend. This may require a lot more efforts and resources, so it is not covered by this document.

Reply-resend is relatively simple and more practicable, RPC server can repeatedly resend reply at fix time interval (e.g. 20 seconds), which should be sufficient even for latency in environment with router. Reply-resend can be stopped when there is an ACK for reply message, or client is evicted/disconnected.

Issue Links

• is related to: LU-10274 LNet event add-on function

Comments

[Amir Shehata (Inactive)]

This looks like it's covered with the LNet Health work. I'll take a look at the docs in more detail to see what he had intended.

[Andreas Dilger]

Amir, how does this relate to our recent discussions about LNet Health and reply timeouts? Are these patches still useful?

[Liang Zhen (Inactive)]

I will work on CORAL soon, so have to reassign this ticket to bobijam. I will maintain patches for a while, but can't finish the landing process.

[Liang Zhen (Inactive)]

Andreas, yes I think I can do this, I will update the patch to make it optional.