zchuango commented on PR #3708:
URL: https://github.com/apache/brpc/pull/3708#issuecomment-6737076373

   > On the RDMA question: URMA-only is fine for this PR. RDMA has no 
equivalent runtime recovery today -- it only falls back to TCP while the 
handshake/queue-pair bring-up is failing (`rdma_endpoint.cpp`), and an 
established QP error is treated as unrecoverable. So there is no parity gap 
this PR has to close. If the mechanism proves useful, the generalization worth 
doing afterwards is a transport-agnostic "a transport failure cools this peer 
for the next N seconds / new connections degrade to TCP" hook shared by RDMA 
and URMA, rather than a second process-global copy of the policy inside RDMA. 
That is also an argument for keeping the policy interface small and 
transport-neutral where it is cheap to do so.
   
   fully agree with this viewpoint. First, we plan to first establish and 
improve the fallback capability through the URMA memory semantics, and then use 
this as a foundation to extend it to the upper layers of the entire 
architecture. We will attempt to expand the functionality of RDMA, UBShm, and 
other transport layers, such as the design of a common fallback hook function. 
We will first internally align and provide the relevant plan. @wwbmmm 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to