Get-ClusterperformanceHistory Powershell command hangs at 'Querying The Database' on an Azure Stack HCI I cluster

Breedy, Andrew 41

When running the Get-Clusterperformance history command on an ASHCI cluster it hangs at '1/3 Querying the Database’ whenever I run it. The cmdlet seemed to stop working for no reason, it had worked fine for me then stopped a few minutes later.
I tried running 'Stop-ClusterPerformanceHistory -DeleteHistory' then 'Start-ClusterPerformanceHistory' but no change.
When I set up the cluster initially I did have a problem with the cluster performance charts IOPS and Latency were blank but running the above two command fixed that problem.

Trent Helms - MSFT 2,541 Reputation points Microsoft Employee

2022-02-18T14:47:20.973+00:00
Hi @Breedy, Andrew ,

I'm checking with our team to determine what we could try here. While I try to research on this, could you confirm a few things as well?

Are you running Azure Stack HCI version 20H2 (build 17784) or 21H2 (build 20348)?

Is the cluster functional level updated? For 20H2, the functional level should be 10, and for 21H2, the functional level should be 11. You can find this by running the PS cmdlet Get-Cluster | Select ClusterFunctionalLevel

Are you running the cmdlet directly on the cluster node itself?

Do you get any change if you attempt to query something other than the cluster? For example, you could query a node by running Get-ClusterNode -Name node_name | Get-ClusterPerformanceHistory.

Thanks,
Trent

Accepted answer

Trent Helms - MSFT 2,541 Reputation points Microsoft Employee

2022-02-18T15:49:35.993+00:00
Hi @Breedy, Andrew ,

After discussing with the team, we have an action plan you can try. Please try the steps below and let us know if this helps to resolve your issue.

Run Stop-ClusterPerformanceHistory -DeleteHistory -Verbose. Look for any errors in the output.

Once this has stopped, run Get-VirtualDisk -FriendlyName ClusterPerformanceHistory and ensure the virtual disk has been removed.

Stop and start the Health resource using Stop-ClusterResource Health followed by Start-ClusterResource Health.

Run Start-ClusterPerformanceHistory to restart the perf history again. (Note that you may need to wait 15-20 minutes for history to be repopulated.)

Please try these steps and let me know the result.

Hope this helps!
Trent
Please sign in to rate this answer.
Breedy, Andrew 41 Reputation points

2022-02-18T16:25:36.007+00:00

Hi Trent. I think your earlier reply may have helped. I ran the cmdlet directly form the ASHCI host and it worked ok . I had been running it from a remote session using -cimsession to connect to the cluster.

To answer your queries OS version is 21H2, OS Build is 20348.524, Functional Level is 11. The Get-ClusterNode -Name node_name | Get-ClusterPerformanceHistory. command returned an error (running remotely) saying the cluster service was stopped though it obviously is not

When I get some time I will try the procedure you have listed above to see if it starts working remotely again.

Thanks,
Andrew
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Get-ClusterperformanceHistory Powershell command hangs at 'Querying The Database' on an Azure Stack HCI I cluster

0 additional answers

Your answer