跳转到主内容

由于与 AIQUM 中的 EMS 事件处理并发冲突，集群轮询停滞不前

  1. 最后更新
  2. 另存为PDF
Views:
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

适用于

  • Active IQ Unified Manager (AIQUM) 9.x
  • ONTAP Cluster-Mode

问题描述

  • Active IQ Unified Manager (AIQUM) 中的集群轮询会间歇性地卡住，导致错过集群运行状况更新并丢失关键警报。
  • 轮询在 UI 中显示为停滞状态，后续轮询将被跳过或丢弃。
观察到的日志输出：
ERROR [oncommand][reconciliation-0][c.n.dfm.collector.OcieJmsListener] Previous foundation poll at <timestamp> ongoing for ds=<id>(<cluster>), adding to the dropped JmsDataSources list
...
org.springframework.orm.hibernate5.HibernateOptimisticLockingFailureException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; statement executed: update Cluster set healthStatus=? where id=? and healthStatus=?; nested exception is org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1; statement executed: update Cluster set healthStatus=? where id=? and healthStatus=?
...
INFO [oncommand][SyslogServer:udp][c.n.dfm.impl.ems.SysLogEventHandler] Received EMS from: [[<cluster>:cpeer.unavailable:ALERT]:]

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.