Skip to content

Commit 89c7a8d

Browse files
fixed grammar
1 parent adb6f44 commit 89c7a8d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,13 +20,13 @@ sections:
2020
answer: Share your feedback on the [Azure IoT Operations public feedback forum](https://feedback.azure.com/d365community/forum/20152d6e-6a76-ee11-8179-000d3a1abe9e).
2121
- question: |
2222
Does Azure IoT Operations offer high availability across multi-node setup?
23-
answer: Yes, Azure IoT Operations workloads on K3s and HCI/AKS-Arc multi-node clusters support distribution of Azure IoT Operations workloads across multi-nodes setups in the preview version. The MQTT Broker does automatically replicates states across multiple nodes governed by the Broker's 'cardinality' setting. Replicas are distributed across different nodes in a multi-node cluster and data is not lost if there is one set of replicas running and healthy.
23+
answer: Yes, Azure IoT Operations workloads on K3s and HCI/AKS-Arc multi-node clusters support distribution of workloads across multi-nodes setups in the preview version. The MQTT Broker does automatically replicates states across multiple nodes governed by the Broker's 'cardinality' setting. Replicas are distributed across different nodes in a multi-node cluster and data is not lost if there is one set of replicas running and healthy.
2424
- question: |
2525
How can we ensure zero or minimal data loss in an Azure IoT Operations setup?
2626
answer: To achieve zero message loss in 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, 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 strict message guarantees (Exactly Once) and requires complex state management and synchronization which can impact performance and scalability. QoS-0 (At most once) and QoS-1 (At least once) provide sufficient message delivery guarantees for Azure IoT Operations operations, where a balance between availability, throughput, latency, and reliable message delivery is desired.
3030
- question: |
3131
Is message persistence supported in Azure IoT Operations?
3232
answer: Full message persistence is on the roadmap, however, Azure IoT Operations supports in-memory message persistence with optional spillover to disk. This setup allows messages to remain available in memory, with overflow messages stored temporarily on disk to prevent data loss during high message volumes. However, if a pod restarts, any messages that were written to disk cannot be restored.

0 commit comments

Comments
 (0)