Applicable Products
- QuTS hero h5.3.0 or later
- High Availability Manager 1.0 or later
Concept
In a high-availability (HA) cluster, a heartbeat connection allows direct periodic exchanges between the two nodes in the cluster. This allows them to monitor each other’s status and ensure that they remain connected and synchronized.
In addition to status detection, the heartbeat connection is also responsible for data synchronization. We use SnapSync technology to perform real-time data synchronization, ensuring data consistency between the nodes.
Recommendation
When setting up the heartbeat connection during cluster creation, please note the following requirements and considerations:
- Use a direct connection
- The heartbeat connection requires a dedicated, point-to-point network connection between the two nodes.
- Do not use switches, hubs, or other networking equipment in between, as they may introduce latency or connection instability.
- Use the same network interface on both NAS devices
- You must use the same network interface on both NAS devices.
For example, if you are using Adapter 2 on the active node device for the heartbeat connection, you must also use Adapter 2 on the passive node device for the heartbeat connection. - The network interface for the heartbeat connection cannot have VLAN or vSwitch adapter bindings.
- Configure DHCP IP addresses to both network interfaces.
- Ensure high-performance and low-latency connectivity
- Select high-speed network interfaces such as 10GbE or higher.
- The heartbeat connection must have the highest speed and lowest latency, as it directly impacts both failover detection and data synchronization.
- The heartbeat connection speed must be greater than or equal to the cluster connection speed.
- Consider port trunking
- If possible, use port trunking (link aggregation) to increase bandwidth and improve fault tolerance.
- You can configure the port trunking mode to "Active-Backup", depending on the capabilities of your hardware and network environment.
- Port trunking modes "Balance-alb" and "Balance-tlb" are not allowed for the heartbeat connection.
Further Reading
適用產品
- QuTS hero h5.3.0 or later
- High Availability Manager 1.0 or later
概念
在高可用性 (HA) 叢集中，心跳連線允許在叢集中的兩個節點之間進行直接的定期交換。這使得它們能夠監控彼此的狀態，確保它們保持連接和同步。
除了狀態檢測外，心跳連線還負責資料同步。我們使用 SnapSync 技術進行即時資料同步，確保節點之間的資料一致性。
建議
在建立叢集時設置心跳連線，請注意以下要求和考量：
- 使用直接連線
- 心跳連線需要在兩個節點之間有專用的點對點網路連線。
- 不要在中間使用交換器、Hub 或其他網路設備，因為它們可能會引入延遲或連線不穩定。
- 在兩臺 NAS 裝置上使用相同的網路介面
- 您必須在兩台 NAS 設備上使用相同的網路介面。
例如，如果您在主動節點設備上使用 Adapter 2 進行心跳連線，則在被動節點設備上也必須使用 Adapter 2 進行心跳連線。 - 心跳連線的網路介面不能有 VLAN 或 vSwitch 介面繫結。
- 為兩個網路介面配置 DHCP IP 位址。
- 確保高效能和低延遲的連線
- 選擇高速網路介面，例如 10GbE 或更高。
- 心跳連線必須具有最高的速度和最低的延遲，因為它直接影響容錯移轉檢測和資料同步。
- 心跳連線速度必須大於或等於叢集連線速度。
- 考慮 Port Trunking
- 如果可能，使用 Port Trunking (連結聚合) 來增加頻寬並提高容錯能力。
- 您可以根據硬體和網路環境的能力，將 Port Trunking 模式配置為 "Active-Backup"。
- 心跳連線不允許使用 Port Trunking 模式 "Balance-alb" 和 "Balance-tlb"。
進一步閱讀
