Applicable Products
QuTS MEGA 1.0.0 and later
Scenario
This scenario explains how software updates in a QuTS MEGA cluster, initiated through Settings > Update in the QuTS MEGA web interface, may affect service availability. These updates may include upgrades to the dashboard, system firmware, cluster services, and individual software components. Understanding how updates are applied helps administrators plan for system maintenance and minimize service disruption.
Details
QuTS MEGA applies software updates using a rolling update process, where nodes in the cluster are updated one at a time to help maintain service availability throughout the update.
In most cases, services continue running without interruption, but if a workload runs on a single pod replica and that replica is hosted on a node being updated, the service may become temporarily unavailable until the pod is redeployed. To avoid potential downtime, you can configure multiple pod replicas for critical workloads, ensuring redundancy and allowing services to fail over to other nodes during updates.
The system provides notifications before applying updates and may require confirmation, while in managed environments, QNAP works directly with administrators to schedule updates and assess their impact. By keeping your system up to date and configuring workloads for high availability, you can maintain consistent performance and service continuity during updates.
Note
In rare cases, SMB clients may display a temporary “network error” during a rolling update if a pod hosting the service is redeployed. This behavior is typically recoverable, and clicking Retry resumes the connection. Configuring multiple pod replicas can further reduce the likelihood of such interruptions.
适用产品
QuTS MEGA 1.0.0 及更高版本
场景
此场景解释了如何在 QuTS MEGA 群集中通过设置>更新在 QuTS MEGA 网页界面中进行的软件更新可能如何影响服务可用性。这些更新可能包括对仪表板、系统固件、群集服务和单个软件组件的升级。了解如何应用更新有助于管理员规划系统维护并最大限度地减少服务中断。
详细信息
QuTS MEGA 使用滚动更新过程应用软件更新，其中群集中的节点逐个更新，以帮助在整个更新过程中保持服务可用性。
在大多数情况下，服务会继续运行而不会中断，但如果工作负载运行在单个 pod 副本上，并且该副本托管在正在更新的节点上，则服务可能会暂时不可用，直到 pod 重新部署。为了避免潜在的停机时间，您可以为关键工作负载配置多个 pod 副本，确保冗余并允许服务在更新期间故障转移到其他节点。
系统在应用更新之前提供通知，并可能需要确认，而在托管环境中，QNAP 直接与管理员合作安排更新并评估其影响。通过保持系统更新并为高可用性配置工作负载，您可以在更新期间保持一致的性能和服务连续性。
注意
在极少数情况下，如果托管服务的 pod 被重新部署，SMB 客户端可能在滚动更新期间显示临时“网络错误”。这种行为通常是可恢复的，点击重试可以恢复连接。配置多个 pod 副本可以进一步减少此类中断的可能性。
