Skip to content

Commit ae3f55d

Browse files
removed additional storage overhead
1 parent 5d1ca91 commit ae3f55d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/iot-operations/troubleshoot/iot-operations-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ sections:
2626
answer: To achieve zero message loss in AIO GA1, a minimum 3-node cluster is required. This configuration allows for one node to reboot or go offline without data loss. However, if the entire cluster goes down or enough nodes are lost to disrupt quorum, message loss may occur.
2727
- question: |
2828
Is MQTT with QoS 2 supported in Azure IoT Operations?
29-
answer: Currently, MQTT with QOS 2 is not supported. QoS 2 provides "exactly once" message delivery, but it requires additional processing and storage overhead, which can impact performance and scalability, particularly in high-throughput IoT environments. Azure IoT Operations prioritizes QoS levels 0 and 1 for efficient message handling, balancing reliability and resource management.
29+
answer: Currently, MQTT with QOS 2 is not supported. QoS 2 provides "exactly once" message delivery, but it requires additional processing, which can impact performance and scalability, particularly in high-throughput IoT environments. Azure IoT Operations prioritizes QoS levels 0 and 1 for efficient message handling, balancing reliability and resource management.
3030
- question: |
3131
Is message persistence supported in Azure IoT Operations?
3232
answer: At AIO GA1, full message persistence is not going to be supported - the capability will be added post-GA. Currently, messages are held in memory with optional spill over to disk. However, if there is pod restart for any reason, messages that were written to disk cannot be restored.

0 commit comments

Comments
 (0)