Skip to main content

METADATA_SNAPSHOT_FETCH_HARD_MAX

Constant METADATA_SNAPSHOT_FETCH_HARD_MAX 

Source
pub const METADATA_SNAPSHOT_FETCH_HARD_MAX: Quantity<dyn Dimension<T = Z0, I = Z0, Th = Z0, L = Z0, N = Z0, M = Z0, J = Z0, Kind = dyn InformationKind>, dyn Units<f64, electric_current = ampere, amount_of_substance = mole, mass = kilogram, luminous_intensity = candela, time = second, thermodynamic_temperature = kelvin, length = meter>, f64>;
Expand description

Hard ceiling on the total bytes a follower will reassemble for one snapshot.

The size of the cluster metadata bounds the __cluster_metadata snapshot: topics, partitions, ACLs, configs, and broker registrations. That is tens of MiB even for very large clusters. 1 GiB is generous but finite. No legitimate cluster reaches it, and it caps the memory that a peer which the follower believes is the leader can force it to allocate (denial-of-service finding M-3). A peer that declares or streams more than this aborts the transfer.