Currently, private data is only communicated to the requesting node upon successfully accepting the connection. However, there are circumstances that make it helpful to know something about why a connection was rejected (e.g., that the remote process is shutting down vs. that there is already a connection in place between the two processes).
Implementation notes:
- Change the return type of
RdmaReceiver::OnConnectRequest to be absl::Status and include a reference to an rdma_conn_param pointer that can be set to allow the private data and its length to be sent back to the requesting node, regardless of the outcome of the request.
Currently, private data is only communicated to the requesting node upon successfully accepting the connection. However, there are circumstances that make it helpful to know something about why a connection was rejected (e.g., that the remote process is shutting down vs. that there is already a connection in place between the two processes).
Implementation notes:
RdmaReceiver::OnConnectRequestto beabsl::Statusand include a reference to anrdma_conn_parampointer that can be set to allow the private data and its length to be sent back to the requesting node, regardless of the outcome of the request.