VDSM consumes a lot of cpu and memory / engine loses vdsm responses

Solution Unverified - Updated -


VDSM consumes a lot of cpu and memory.
Engine loses vdsm responses.
In engine.log, the following error message would appear:

[org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker) Exception thrown during message processing

If debug is enabled, it will have additional info:

"Heartbeat exeeded. Closing channel"


Red Hat Enterprise Virtualization (RHEV) 3.5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In