VMware Cloud Community
peetz
Leadership
Leadership

VirtualCenter: No new logins when jobs are queued ?!

Hi all,

We recently noticed that - if there are queued jobs in VirtualCenter - it is not possible to log in to VirtualCenter via the VI client. Existing sessions are kept and run without problems, but no new sessions can be started (The log on just times out). We can reproduce this problem by starting an "Enter maintenance" task for a host that has lots of VMs (50 to 60) running on it. VirtualCenter will immediately start VMotion jobs for all of the VMs. The first 20 (or so) tasks will have the status "In progress", but the rest will have the status "Queued", and as soon as there is one or more queued jobs you won't be able to start a new session.

Can you confirm or disclaim this? Is this "by design" or is it a problem of our installation (VC 2.5 U3 with remote Oracle 10 database, 2 datacenters, 16 hosts, about 380 VMs)?

If this is by design is there a way to increase the max. possible number of jobs "in progress", so that queueing will start later?

Thank you for any comments!

Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Reply
0 Kudos
3 Replies
pooserj
Contributor
Contributor

I've had a case open on this for a few months now. Just got this response today:

"We're still waiting for engineering to respond to this case. I am pressing our engineering team to give us a response to this and will keep you informed."

peetz
Leadership
Leadership

Thanks, that sounds familiar to me. Smiley Wink

So I will open a SR for this, too.

Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Reply
0 Kudos
pooserj
Contributor
Contributor

Got this response last week:

>It has come to my understanding that there will not be a fix for this issue in the current VI3 generation of the product due to the architectural changes required to implement a permanent solution to this problem.

>This aside, I can confirm that engineering will be addressing the issue in the next product generation (or vSphere 4).

Reply
0 Kudos