mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
841a40ff88
At every site where we've dug into backpressure disconnect findings, it has been the case that the default values were too small. 8192, so 4x the old default, suffices at every site to drown out premature disconnects. With metrics now available for the send buffers regardless of backpressure overflow policy, this also switches the default from "disconnect" to "drop_oldest" (for both peers and websockets), meaning that peerings remain untouched but the oldest queued message simply gets dropped when a new message is enqueued. With this policy, the number of backpressure overflows is then simply the count of discarded messages, something that users can tune to see drop to zero in everyday use. Another benefit is that marginal overflows cause less message loss than when an entire buffer's worth (plus potentially more in-flight messages) gets thrown out with a disconnect. |
||
|---|---|---|
| .. | ||
| __load__.zeek | ||
| backpressure.zeek | ||
| log.zeek | ||
| main.zeek | ||
| README | ||
| store.zeek | ||
The Broker communication framework facilitates connecting to remote Zeek instances to share state and transfer events.