DRS invocation not completed

[deepak_ashwath]

hi

i have an error in the cluster as "DRS invocation not completed" due to which the ESX cluster is slow. Any body has any idea on this ?

Deepak

[jschlach]

Was there ever an answer for this? I've just come across this problem after rebooting a host in a resource pool. It's stuck as "not responding" even though the host is online and I can ssh into it.

Update: I restarted Virtual Center and this condition went away. 😕

[abii]

Hi, I am getting the same error "DRS invocation not completed" on cluster. Can you please guide how did you restart the virtual center? Do I need to do it on all the hosts inside the cluster? Your time is highly appreciated!!

[krismcewan]

In the DRS Tab of the Cluster click RUN DRS (top right)

This should do a recheck of all the DRS rules and settings and migrate things about if required.

Also check your rules to make sure that there are none that conflict or make an imbalance that DRS cant handle.

All else fails do a restart of the VCenter service and the Management agents on each host.

[curmudgeonsf]

I fixed this by disabling HA and removing, then re-adding each host to the cluster. Within a minute or two, the error went away and the hosts started displaying the correct memory and cpu usage instead of 0. No rebooting of VMs or vmotioning occured during this process. This occured on version 5.1

-Josh

[Swift0ZA]

Alternatively, Just try to "Disconnect" and "Re-Connect" the affected hosts first; before removing them from the cluster and even the vCenter all together and then adding them again, which is quite a tedious task if you have plenty of hosts that are affected.

I had this same problem today, AGAIN! I had it a couple of times in the past and I used to fix it by removing the host from vCenter, then adding it again. Lukily i found this post: DRS invocation not completed

All credit to "Rapidparts, Inc" who posted on that blog and mentioned to Disconnect and Re-Connect the affected hosts. I tried it and has worked for me on vCenter 5.1.

It seems like this is quite a common and recurring problem and seems to have started with vSphere 5.0... Does anyone know if VMWare is aware of this or may have addressed this problem already? There is not much on this problem to be found on the Internet and especially on VMWare's site.

P.S.

There is a similar issue in vCenter 5.x where DRS may still be working but the performance graphs show: "Performance data is currently not available for this entity" - This can also be temporarily fixed by Disconnect\Reconnect of the affected host. A permanent Fix for this issue would be nice :smileycool: (Removing hosts and adding them is not it - the issue keeps creeping in every so often).