You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bc59a4b
Browse filesBrowse the repository at this point in the historyBrowse files
docs(api): a pinned write goes to the pinned node only (MAG-4382) (#82)
Product decision A on MAG-4382: a pin means "only this node" for reads
and writes alike, so a write carrying lava-select-provider or
lava-stickiness is sent to the pinned node only and gives up the
broadcast to every node. That is the router's behaviour today; the docs
never said it.
directives.md: a note under the pin section, a sentence in the sticky
section, and a lava-fast-tx-participants row in the response headers
(it was not documented), which is how a caller sees who got the write.
sticky-sessions.md: the read-your-own-write row says the write itself
then goes to one node, and how to keep the broadcast.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
To work across replicas, the header needs a cache backend and `--shared-state`. Without them, it only applies within a single replica. If the chosen node cannot serve a request, the request fails. No other node serves it. See [Sticky sessions](../configuration/sticky-sessions.md) for the full behaviour and limits.
107
+
To work across replicas, the header needs a cache backend and `--shared-state`. Without them, it only applies within a single replica. If the chosen node cannot serve a request, the request fails. No other node serves it. A write in the session goes to that node only, without the usual broadcast to every node (see [A pinned write](#pin-to-a-specific-node)). See [Sticky sessions](../configuration/sticky-sessions.md) for the full behaviour and limits.
100
108
101
109
## Force a cache refresh
102
110
@@ -236,6 +244,7 @@ Smart Router adds metadata to every response about how the relay was served. The
236
244
|`Lava-Provider-Address`| The node that finally served the response. The literal value **`Cached`** means the [cache](../deployment/cache/index.md) answered and the router contacted *no* node, even when the request named one with `lava-select-provider`. |
237
245
|`Lava-Retries`| Number of retry attempts made for this relay. |
238
246
|`Provider-Latest-Block`| Latest block the serving node reported. |
247
+
|`lava-fast-tx-participants`| On a write only: the nodes the router sent it to, in brackets and space-separated, e.g. `[node-a node-b]`. A single name means the write was not broadcast, for example because it was [pinned](#pin-to-a-specific-node). |
239
248
|`Lava-Guid`| Unique request id. Use it to find the request in logs and traces. |
240
249
|`Lava-Errored-Providers`| Nodes that errored on this request. |
241
250
|`Lava-Node-Errors-providers`| Nodes that returned a node-level error. |
Copy file name to clipboardExpand all lines: docs/configuration/sticky-sessions.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ A session's choice lasts about two router epochs (30 minutes at the default `--e
77
77
|---|---|
78
78
| Two or more calls that must agree: read the head, then fetch that block |**Yes**. This is what it is for |
79
79
| Node-side state tied to one node, such as an `eth_newFilter` id or a subscription handle |**Yes**|
80
-
| Read-your-own-write after `eth_sendRawTransaction`|**Yes**|
80
+
| Read-your-own-write after `eth_sendRawTransaction`|**Yes**. The write itself then goes to the session's node only, not to every node: a sticky write gives up the broadcast. Send the write without the header if you want the broadcast, and the follow-up reads with it|
81
81
| Independent single reads with no relationship to each other | No. Pinning gives up the optimizer's choice with no benefit |
82
82
| A specific node you already know by name | No. Use [`lava-select-provider`](../api/directives.md#pin-to-a-specific-node)|
0 commit comments