This message was deleted.

Sounds like the failure is between the coordinator and the metadata database connection. The overlord also interacts with the metadata database directly. AFAIK, no other services connect to the metadata DB.

HI @Sergio Ferragut looks issue with host it has very less memory . Increased to higher memory box and not seeing error any more

I'm glad you figured it out. Thanks for the update! Was the problem with coordinator memory ? or was your metadata DB getting overwhelmed?

i think its due to coordinator memory . after increasing the instance type we didn't faced any issue