Quote Originally Posted by seebs View Post
No, it's not that simple. I got into queue, I was #12 in queue, then I got bounced out with 1017.

There is something seriously broken here. The entire point of a queue is that it lets you, get this, "queue" people up so that they can be assigned available slots as and when those slots open up. The basic idea of accumulating the list of people (or things) waiting for processing, and taking them out of the queue as capacity becomes available (say, other tasks complete, other players log out) is literally the entire point of a queue. I would really, really, like to see an official post from SE explaining in actual technical detail how you could possibly implement a system such that you have a queue, but when you need to limit population, you can't have people wait in the queue. I program, many of my friends program, and so far I've not found anyone who can come up with an explanation for how you could build a queue that would need to error out like this.
This is how this works... Server holds 5000 people each. they are limiting how many people can be logged in on the server to promote stability of the duty finder and other similar systems. Second the queue system holds only x amount of players in it. When that queue system is full or overloaded you get the 1017. For the times you get in a queue but then get booted out after several min its because they have now adjusted the artificial cap on the server. So say they where letting 3000 people and 300 in queue. But duty finder system is under strain. To prevent the servers from crashing they throttle back to 2800 people. which then pushes those 300 people in queue to 1017. Obviously these numbers are just used as an example not real data.