12/15/2006 Assignment Server (AS) code update
We've been seing some serious misassigns with the AS code, so we have made some major changes. The upside is that it should not be possible (as far as we can tell) to get assigned to a server that the client can't run WU's from. This is important especially these days, as there are a large variety of types of clients, cores, ports, and each have certain limitations and restrictions.
In the past, when the AS got stuck, it would simply assign to the "default server," assuming that there would always be a server which could handle anything. In the old days of FAH, that was easy. Now, that's almost impossible. So, instead of just going with the default (and hoping for the best), the AS goes through a logical set of conditions and if it can't find a match, it assigns to 0.0.0.0, which means the client will just try again later.
So far, this is looking good, with one major drawback. Right now, we are very low on jobs that work with the v4 client. Due to some modifications in v5, certain calcualtions can only run in v5. V5 has been out for quite a while, so most of our science is based on v5-enabled functionality. Right now, v4 clients will likely get assigned to 0.0.0.0 as there is a dearth of v4 available WU's. We are working to see how we can fix this (and whether a few WUs can be made v4 compatible). But, in the mean time, if you are running v4 and are getting assigned to 0.0.0.0, the best and simplest thing to do is to upgrade your client ASAP.
All of this is going on late PST Friday night, so it may be a rough weekend, but we're keeping an eye on all of this and will do so until it looks like this is working well. So far, so good.