Work around for Scheduler issues.

Questions and Answers : Wish list : Work around for Scheduler issues.

To post messages, you must log in.

AuthorMessage
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 7486
Credit: 91,086,990
RAC: 46,347
Australia
Message 1301152 - Posted: 2 Nov 2012, 4:43:10 UTC


Lately the Scheduler appears to be having major problems whenever there is heavier than usual network traffic. The usual response to reporting or requesting work is "Scheduler request failed: Timeout was reached".

Routing the Scheduler traffic to the campus network (the one used by the web site & forums) may help with this issue.
At it's heaviest, inbound traffic is around 20Mb/s. During the outages when the Scheduler is down, but uploads are still possible the inbound traffic is generally around 8Mb/s.
So that would shift roughly 12MB/s of traffic from the present saturated link, it wouldn't overwhelm the campus network, & it would allow people to report & at least get new work allocated without difficulty.


Grant
Darwin NT

ID: 1301152 · Report as offensive
John McLeod VII
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 15 Jul 99
Posts: 24806
Credit: 754,585
RAC: 65
United States
Message 1301495 - Posted: 3 Nov 2012, 0:19:06 UTC - in response to Message 1301152.  


Lately the Scheduler appears to be having major problems whenever there is heavier than usual network traffic. The usual response to reporting or requesting work is "Scheduler request failed: Timeout was reached".

Routing the Scheduler traffic to the campus network (the one used by the web site & forums) may help with this issue.
At it's heaviest, inbound traffic is around 20Mb/s. During the outages when the Scheduler is down, but uploads are still possible the inbound traffic is generally around 8Mb/s.
So that would shift roughly 12MB/s of traffic from the present saturated link, it wouldn't overwhelm the campus network, & it would allow people to report & at least get new work allocated without difficulty.

Not allowed by the campus.


BOINC WIKI

ID: 1301495 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 7486
Credit: 91,086,990
RAC: 46,347
Australia
Message 1301856 - Posted: 3 Nov 2012, 23:13:04 UTC - in response to Message 1301495.  


That's a shame.
I don't think the issue is bandwidth related- there have been many times in the past where it has been impossible to download work due to network congestion, but you were still able to report & be allocated new work regardless of how bad the downloads were.
But moving the scheduler traffic to a different network from the download traffic would have shown one way or the other if it was network load related or sever load related.


Grant
Darwin NT

ID: 1301856 · Report as offensive

Questions and Answers : Wish list : Work around for Scheduler issues.


 
©2016 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.