Skip to content

Commit 7eb2525

Browse files
Merge pull request #290231 from huguesBouvier/patch-1
Update howto-disk-backed-message-buffer.md
2 parents 8d83e0b + 8e59d35 commit 7eb2525

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,10 @@ The **disk-backed message buffer** feature is used for efficient management of m
2727
<!-- TODO: accuracy check -->
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

30-
Understanding and configuring the disk-backed message buffer feature maintains a robust and reliable message queuing system. Proper configuration is important in scenarios where message processing speed and connectivity are critical factors.
30+
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+
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.
3134
3235
## Configuration options
3336

0 commit comments

Comments
 (0)