jetstream

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.

Types

Type	Description	Choices
boolean	-	true, false
string	Indicates the capability is enabled or disabled.	enabled, enable, disabled, disable
object	An object with a set of explicit properties that can be set.	-

Properties

Name	Description	Type	Default	Reloadable
max_memory	The maximum storage allowed across all memory-based assets.	integer	-	Yes*
max_file	The maximum storage allowed across all file-based assets.	integer	-	Yes*
max_streams	The maximum number of streams allowed.	integer	-	Yes*
max_consumers	The maximum number of consumers allowed.	integer	-	Yes*
max_bytes_required	If true, requires all streams to have an explicit max bytes defined for both file and memory-based streams.	boolean	-	Yes*
memory_max_stream_bytes	Maximum bytes any given memory-based stream is allowed to be allocated.	integer	-	Yes*
disk_max_stream_bytes	Maximum bytes any given file-based stream is allowed to be allocated.	integer	-	Yes*
max_ack_pending	The maximum ack pending count allowed to be set on any given consumer.	integer	-	Yes*

* See the property page for reload caveats.