Stuck nonces

Chain 13
KafkaHTTP/2Partner apps400 req/sKafka log2 vCPU · 2 GBWorker1 vCPU · 1 GB × 8
KafkaHTTP/2Partner apps400 req/sKafka log2 vCPU · 2 GBWorker1 vCPU · 1 GB × 8

Fix the board. Turn every goal green.

Traffic
400 req/s · writes only
Limit
Worker answers about 1,300 req/s
Bill
  • Kafka log8 USD/mo
  • Worker32 USD/mo
40 of 80 USD/mo

Goals

Not tested yet

Events that arrived in the wrong order.How long a message waits before a worker takes it.Saved data that was lost later.What the servers and services cost each month.

The exchange sends 400 payouts/s from 64 hot wallet addresses. Eight signers read one payout log, and each signature takes 6 ms of CPU. Transactions from one address must reach the chain in nonce order, but many arrive early and get stuck. You have 2 edits.

0:10. Payouts stall. Nodes hold 2,000 transactions that arrived before a lower nonce from the same address.

A lease with a fencing tokenTap to turn the fencing tokens on or off

Fencing tokens · lease 30 s · late write with token 33: rejected

Parts you can add: Kafka log, Worker. At most 8 parts. Budget: 80 USD/mo.

Tap a part to add it, or drag it onto a trace.Click a part to add it, or drag it onto a trace.