Skip to main content

BYTE_LOG_REFUSED_REASON

Constant BYTE_LOG_REFUSED_REASON 

Source
pub const BYTE_LOG_REFUSED_REASON: &str = "this peer refused a one-event push of the byte-cut log, whose events are \
     sized from its declared `max_event_bytes`: it takes smaller events than \
     it declares (SY-18's subject, judged by its rule), and the count-cut log \
     showed no page; SY-37 is unverified for this peer";
Expand description

The reason SY-37’s rule reports when the peer refused its byte-cut log, and the count-cut log showed no page.

That log pushes one event to a push, its payload PeerLimits::max_event_bytes capped by max_batch_bytes: no larger than the boundary event peer_declares_its_own_limits pushes alone. So a refusal is the peer taking smaller events than it declares, SY-18’s subject, and a peer that refuses it on size fails that rule too. Because each push holds one event, a peer that overstates only max_batch_bytes takes the log and pages it, which no rule could otherwise judge.