Skip to main content
Active IQ Unified Manager 9.9
9.9
A newer release of this product is available.

Responding to a dynamic performance event caused by HA takeover

Contributors
PDFs

You can use Unified Manager to investigate a performance event caused by high data processing on a cluster node that is in a high-availability (HA) pair. You can also use Unified Manager to check the health of the nodes to see whether any recent health events detected on the nodes contributed to the performance event.

Before you begin

  • You must have the Operator, Application Administrator, or Storage Administrator role.

  • There must be new, acknowledged, or obsolete performance events.

Steps

  1. Display the Event details page to view information about the event.

  2. Read the Description, which describes the workloads involved in the event and the cluster component in contention.

    There is one victim volume whose latency was impacted by the cluster component in contention. The data processing node, which took over all workloads from its partner node, is the cluster component in contention. Under Component in Contention, the Data Processing icon is highlighted red and the name of the node that was handling data processing at the time of the event is displayed in parentheses.

  3. In the Description, click the name of the volume.

    The Volume Performance Explorer page is displayed. At the top of the page, in the Events time line, a change event icon (Change event icon) indicates the time that Unified Manager detected the start of the HA takeover.

  4. Point your cursor to the change event icon for the HA takeover and details about the HA takeover are displayed in hover text.

    In the Latency chart, an event indicates that the selected volume crossed the performance threshold due to high latency around the same time as the HA takeover.

  5. Click Zoom View to display the Latency chart on a new page.

  6. In the View menu, select Cluster Components to view the total latency by cluster component.

  7. Point your mouse cursor to the change event icon for the start of the HA takeover and compare the latency for data processing to the total latency.

    At the time of the HA takeover, there was a spike in data processing from the increased workload demand on the data processing node. The increased CPU utilization drove up the latency and triggered the event.

  8. After fixing the failed node, use ONTAP System Manager to perform an HA giveback, which moves the workloads from the partner node to the fixed node.

  9. After the HA giveback is complete, after the next configuration discovery in Unified Manager (approximately 15 minutes), find the event and workload that triggered by the HA takeover in the Event Management inventory page.

    The event triggered by the HA takeover now has a state of obsolete, which indicates that the event is resolved. The latency at the data processing component has decreased, which has decreased the total latency. The node that the selected volume is now using for data processing has resolved the event.