max_bytes_required

Aliases: max_stream_bytes, max_bytes

Hot Reloadable

Applied by replacing the account's whole limits map, so it is all-or-nothing: on a standalone server the update is rejected if it would put max_memory/max_file below already-reserved stream bytes, and the reload still reports success (the error is only logged). Worse, the account walk returns on the first such error, so accounts later in iteration order get no limit update at all. Enforced when assets are created or updated; existing streams/consumers above the new value are left running.

If true, requires all streams to have an explicit max bytes defined for both file and memory-based streams.

Types

Type	Description	Choices
boolean	-	true, false