Skip to main content

Module client

Module client 

Source
Expand description

The client side of a contract run: the paced producers, the live consumer groups, and the read-back after the load.

Unlike the judge, this half does IO. It is shared by the two executors that run a contract: the soak_contract suite of krabka-broker, which runs a soak or a self-check against its own three-broker cluster, and krabka-soak-drill, which runs a disaster-recovery contract against the secured cluster of the qualification drill. Both send the same records, keep the same ledgers and read back the same way, so the reconciler judges both by the same rules.

  • load: one paced producer per path, one live consumer group per path and isolation level.
  • readback: the read-back from the earliest offset, and the committed-offset checks.
  • windows: steady and disturbed time, and the latency split across it.

Modules§

load
The load: one paced producer per path and one live consumer group per path and isolation level.
readback
After the load: the committed offsets, and the read-back that the reconciler compares with the producers’ ledgers.
windows
Steady and disturbed time, and the latency and throughput split across it.

Structs§

Endpoint
Where every client of a run connects, and how it authenticates.
ScramLogin
A SCRAM-SHA-512 login over TLS.

Functions§

now_ms
The wall clock in Unix milliseconds, the coordinate every timestamp of the evidence is in.