Skip to content

Commit 8e59d35

Browse files
Update articles/iot-operations/manage-mqtt-broker/howto-disk-backed-message-buffer.md
Co-authored-by: Pat Altimore <[email protected]>
1 parent 0f9d898 commit 8e59d35

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/iot-operations/manage-mqtt-broker/howto-disk-backed-message-buffer.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,9 @@ The **disk-backed message buffer** feature is used for efficient management of m
2828
By default, the disk-backed message buffer feature is disabled. In this case, messages remain in memory, and back pressure is applied to clients as the reader pool or scratch pool reaches the limit as defined by the [subscriber queue limit](./howto-broker-mqtt-client-options.md#subscriber-queue-limit).
2929

3030
Configuring the disk-backed message buffer is essential for maintaining a robust and reliable message queuing system, especially in scenarios where message processing speed and connectivity are critical.
31-
**Note**: The MQTT broker writes data to disk exactly as received from clients, without additional encryption. Securing the disk is essential to protect the data stored by the broker.
31+
32+
> [!NOTE]
33+
> The MQTT broker writes data to disk exactly as received from clients, without additional encryption. Securing the disk is essential to protect the data stored by the broker.
3234
3335
## Configuration options
3436

0 commit comments

Comments
 (0)