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 技术进行实时数据同步，确保节点之间的数据一致性。
建议
在创建群集时设置心跳连接，请注意以下要求和注意事项：
- 使用直接连接
- 心跳连接需要两个节点之间的专用点对点网络连接。
- 不要在中间使用交换机、中心或其他网络设备，因为它们可能会引入延迟或连接不稳定。
- 在两个 NAS 设备上使用相同的网络接口
- 您必须在两个 NAS 设备上使用相同的网络接口。
例如，如果您在活动节点设备上使用适配器 2 进行心跳连接，则在被动节点设备上也必须使用适配器 2 进行心跳连接。 - 心跳连接的网络接口不能绑定 VLAN 或 vSwitch 适配器。
- 为两个网络接口配置 DHCP IP 地址。
- 确保高性能和低延迟连接
- 选择 10GbE 或更高的高速网络接口。
- 心跳连接必须具有高速度和低延迟，因为它直接影响故障转移检测和数据同步。
- 心跳连接速度必须大于或等于群集连接速度。
- 考虑端口中继
- 如果可能，使用端口中继（链路聚合）来增加带宽并提高容错能力。
- 您可以根据硬件和网络环境的能力，将端口中继模式配置为“Active-Backup”。
- 心跳连接不允许使用端口中继模式“Balance-alb”和“Balance-tlb”。
进一步阅读
