This is documentation for NATS Documentation 2.11, which is no longer actively maintained.
For up-to-date documentation, see the latest version (2.14 (latest)).
Version: 2.11
memory_max_stream_bytes
Aliases: mem_max_stream_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.
Maximum bytes any given memory-based stream is allowed to be allocated.