A gRPC deadline bounds waiting, not uncertainty about side effects

A deadline states when a caller is no longer willing to wait; a timeout is a duration used to represent a budget at a particular point. Set an appropriate deadline explicitly instead of relying on an unspecified default. Include local waiting and connection acquisition in the user operation's budget, even when a particular library's RPC timer begins later. Downstream calls should receive only the remaining budget, often with a reserve for returning or cleaning up. Giving every hop a fresh full timeout can make a short user operation continue consuming resources long after its intended limit.

Different machines do not necessarily share an exact wall clock. gRPC propagates time remaining as a timeout, avoiding an assumption that a remote endpoint interprets a copied absolute timestamp identically. Language runtimes differ in how propagation is configured or performed automatically, so verify the selected implementation. Locally, use a suitable monotonic clock for elapsed-time accounting. A budget calculation is still an upper bound on willingness to wait, not a guarantee of successful scheduling: a thread can be descheduled, cancellation can be observed later, and already transmitted work cannot be pulled back by arithmetic.

A gRPC exchange commonly carries HTTP status 200 while its final gRPC status reports an application or RPC failure. The grpc-status field is normally carried in final trailers, with a trailers-only form for certain immediate responses. Receiving headers or one streaming message is not equivalent to receiving successful final completion. Libraries may synthesize a status when transport failure prevents valid trailers. Record the RPC status and whether it came from an observed completion or local transport handling, alongside application request identifiers and user-visible outcomes. An HTTP access log alone is not a complete gRPC success metric.

DEADLINE_EXCEEDED means the operation did not complete within the caller's allowed deadline from that perspective; it can occur even when a state-changing operation completed successfully but the response arrived too late. CANCELLED likewise describes cancellation, not a durable rollback guarantee. UNAVAILABLE can identify a retryable situation under an appropriate policy, but the status code alone does not establish safe replay for every operation. Combine method semantics, idempotency, retry configuration, attempt budget, and knowledge about committed effects. Retrying a non-idempotent action merely because it lacked a success status can duplicate the action. In A6's retry model, receiving response headers or overflowing the client's replay buffer commits the RPC to an attempt and stops subsequent automatic retries. This library commitment is distinct from the application's durable transaction commit.

The server should observe cancellation and stop work that no longer has a useful consumer, including downstream calls where appropriate. The runtime cannot generally interrupt arbitrary application logic safely; handlers and resource owners need to cooperate. Cancellation can race with transaction commit, external side effects, response serialization, or a worker finishing. Preserve the result in durable application state when the operation's contract requires later reconciliation. A client that sees an ambiguous outcome can query by a stable operation identifier or retry through a deduplication protocol rather than treating a timeout as proof of failure.

The queue lab examines waiting pressure, not deadline enforcement. Reset, explicitly set BOTH λ=2.5 and μ=3, predict backlog four draining from t=0 to zero at eight seconds, then Play or Step. Reset and re-set BOTH λ=1 and μ=3 for a two-second drain comparison. Edits retain elapsed t and recompute from four; they are not live changes to a running RPC. Neither the fluid backlog nor the separate M/M/1 residence estimate predicts an individual request's deadline. Use an event timeline and cancellation evidence to determine whether useful work stopped or merely the caller stopped waiting.