Difference between revisions of "Proxyd"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
* Applies [[rate limiting]] (<code>[[SenderRateLimitConfig]]</code>) on a per-sender basis to avoid being bombarded with signed transactions causing a DOS (Denial of Service) of the sequencer ([[Optimism Censorship Bug Disclosure]]) | * Applies [[rate limiting]] (<code>[[SenderRateLimitConfig]]</code>) on a per-sender basis to avoid being bombarded with signed transactions causing a DOS (Denial of Service) of the sequencer ([[Optimism Censorship Bug Disclosure]]) | ||
| + | |||
| + | == Backend healthy == | ||
| + | In [[proxyd]] a backend is considered healthy if it meets the following criteria | ||
| + | * Not [[banned]] | ||
| + | * Avg 1-min moving window [[error rate]] ≤ [[configurable threshold]] | ||
| + | * Avg 1-min moving window latency ≤ configurable threshold | ||
| + | * [[Peer count]] ≥ configurable threshold | ||
| + | * [[Latest block]] lag ≤ [[configurable threshold]] | ||
| + | * [[:ast state update]] ≤ configurable threshold | ||
| + | * Not currently [[syncing]] | ||
== Logs == | == Logs == | ||
Revision as of 15:05, 14 October 2024
proxyd /etc/proxyd/proxyd.toml ws_method_whitelist
- Changelog: https://github.com/ethereum-optimism/infra/blob/main/proxyd/CHANGELOG.md
- Config: https://github.com/ethereum-optimism/infra/blob/main/proxyd/config.go
- Releases: https://github.com/ethereum-optimism/infra/tags
Features:
- Whitelists RPC methods (ws_method_whitelist)
- Routes RPC methods to groups of backend services
- Round-robin Load balance requests across backend services
- Automatically retries failed backend requests
- Cache immutable responses from backends
- Provides metrics to measure request latency, error rates
Consensus related:
- Track backend consensus (latest, safe, finalized blocks), peer count and sync state
- Re-write requests and responses to enforce consensus
- Applies rate limiting (
SenderRateLimitConfig) on a per-sender basis to avoid being bombarded with signed transactions causing a DOS (Denial of Service) of the sequencer (Optimism Censorship Bug Disclosure)
Backend healthy
In proxyd a backend is considered healthy if it meets the following criteria
- Not banned
- Avg 1-min moving window error rate ≤ configurable threshold
- Avg 1-min moving window latency ≤ configurable threshold
- Peer count ≥ configurable threshold
- Latest block lag ≤ configurable threshold
- ast state update ≤ configurable threshold
- Not currently syncing
Logs
ERROR
error forwarding request to backendError forwarding RPC batcherror serving requestserror proxying websocketerror writing clientConn message
WARN
backend request failed, trying againbackend banned - not healthybackend banned - unexpected block tagsproxied requests' XFF header will not contain the proxyd ip addresspeer count responded with 200 and 0 peersfailed requesterror updating backendbackend broke consensus
INFO
Activities
Related
- Consensus
- Emerald Dshackle load balancer
- dRPC
- Total number of primary candidates
- RedisConfig
- Fallback
See also
proxyd, config, routing_strategy, consensus_aware (deprecated), SenderRateLimitConfig, Consensus awareness,ws_method_whitelist, backend healthy- OP Stack:
op-, op-geth, op-node, op-proposer, op-batcher, op-contracts, op-challenger, op-heartbeat, op-ufm, op-service, Snap Sync, op-conductor, op-dispute-mon
Advertising:
