"Additional instances cannot be launched..."

Post by M3rc3nary0

Why does this happen so frequently, and if anything can be done about it, why haven't Blizzard done anything yet? It seems almost every time i go to run a low level instance i get this message.... anyone else having the same problems?

Post by 173035

This post was from a user who has deleted their account.

Post by 334003

This post was from a user who has deleted their account.

Post by Sakkura

It prevents the instance server (the server that runs all the instances for a given server) from becoming overburdened. If additional groups are allowed to "open" their version of an instance, then it adds a burden to the instance server; at some point, the burden becomes too much for the instance server, resulting in poor performance and/or crashes.

They introduced or severely tightened this restriction not long before the 3.0 patch, after an extended period with server problems affecting raids and dungeons in prime time.

Post by 283705

This post was from a user who has deleted their account.

Post by 295513

This post was from a user who has deleted their account.

Post by airtonix

so i decided to look it up on here, and thought maybe this might be the reason, so i checked with /who the oculus, it c came up with 0 players total, so this cannot be the reason!

The 'spots' are probably shared.

It is known that for a given realm, both factions are serviced by the same instance server.

What seems a little unclear to me is for how long will a groups instanceID take up a spot?

Does it have a timeout like php/asp sessionIDs do? so even though the group finished 10minutes ago, it will still be taking up a slot for the next 10min.

I also know that peoples use of leaving group inside a fresh dungeon to be ported to their herthstone spot takes a slot in this idea.

"Additional instances cannot be launched..."

Post Reply