Like others mentioned below I had a hypervisor error, which isn't my issue. I got the error because I had uninstalled vbox on this machine, but I was hoping to get another shot at it on another machine that I can commit to long VM WUs on. So I prepared the other machine to get new work, aborted and updated on this machine. Went to update on another machine and it says "last request too recent 651 seconds" That's a long time to have to wait in my opinion, also in comparison to other projects which usually are around 3 minutes.
I'm eager to see how this project runs; it'd be much more convenient for us to help test and run this project if the server was a bit more flexible with host activity.
Update request time
-
ChristianB
- Admin

- Beiträge: 1920
- Registriert: 23.02.2010 22:12
Re: Update request time
This long update penalty was introduced to spread the low amount of workunits on more hosts. I've seen that shortly after I created a bunch of workunits they were all reserved by a handful of hosts so I limited the amount of workunits per request and increased the time between updates. This will change back once we have a more steady amount of new workunits. It's also not possible to "move" tasks between hosts that belong to the same useraccount.
