Remote procedure call (RPC)
A remote procedure call (RPC) invokes a procedure in another process by exchanging request and reply messages.
Interface: RPC can use synchronous or asynchronous APIs. ONC RPC identifies a procedure by program, program version and procedure number; these fields are specific to that protocol. Its XID matches replies to calls or detects retransmissions, but is not an execution-order sequence number. [1]
Failure: A missing reply alone leaves execution uncertain. In gRPC, client and server can disagree about completion, and cancellation does not undo earlier changes. A call result therefore needs the application-specific persistence contract. [1] [2]
Retry scope: eRPC suppresses repeated handler execution during protocol retransmission and reports errors for pending client calls after suspected node failure. This does not establish durable deduplication for a newly submitted application request. [3]
Concurrency: Idempotent effects alone do not ensure linearizable retries: repeating a fixed-value write after an intervening update can overwrite that update. [4]
Relations
- related
- eRPC, RIFL, I/O timeout, Retry deduplication
Citations
- RFC 5531: ONC RPC Version 2, sections 4, 5, 8.1 and 9
- gRPC: Core concepts, RPC termination and cancellation
- Kalia, Kaminsky and Andersen: Datacenter RPCs can be General and Fast, NSDI 2019, sections 3.1, 5.3 and Appendix B
- Lee et al.: Implementing Linearizability at Large Scale and Low Latency, SOSP 2015, section 2 and Figure 2
Sources & caveats
- Primary-source synthesis of a general interface concept. ONC RPC, gRPC and eRPC are distinct protocols or implementations; their fields and failure semantics are not interchangeable.
- No network, retry or crash-recovery experiment was performed for this entry.