New problem with Gravitational Wave S6 Directed Search (CasA) ?
27 Jul 2013 20:19:04 UTC
Topic 197091
(moderation:
My W7 machine has 2 which I received on the 25th and 26th which I have processed. I looked at them and they have not been assigned to a wingman. OBTW it has validated the 3rd one.
The W8 machine has 19, none of which have been processed but only 6 of them have wingmen assigned. It then requested more CSA and got the message that no work was available. That is not true because the W7 has 2 which need a wingman, so it seems there is a problem.
New problem with Gravitational Wave S6 Directed Search (CasA) ?
)
This has to do with how locality scheduling works. The short answer is to have patience, the tasks will get assigned to a wingman in due time.
The longer answer is that the scheduler will wait for a host with the right set of data files to ask for work before sending it to minimize the amount of data to download. In the beginning of a analysis it might take a bit longer for a suitable host to ask for work as there is fewer hosts with the right set of data files or for the scheduler to reach a timeout and assign the task to the next host asking for that type of work. And to add to this Bernd has posted elsewhere that only a small amount of task for the new Gravity Wave search is available at any given time to prevent server overload if too many hosts try to download to much data at the same time.
For the second part there is a server side setting that defaults to not send the same task to the same user twice even if it's to different hosts, it's there to prevent cheating. So you should never be your own wingman.
That makes sense, thanks.
)
That makes sense, thanks.