Ticket #932 (closed Defect: fixed)

Opened 5 months ago

Last modified 5 months ago

Change result upload retry policy from per task to per project

Reported by: Raistmer Assigned to: davea
Priority: Major Milestone: Undetermined
Component: Client - Work Fetch Policy Version: 6.6.31
Keywords: Cc:

Description

Per task upload retry policy leads to kind of DoS attack from fast hosts in periods when project's server can't handle all incoming connections. When many results trying to resend themselves on it' own time schedule host _continually_ tries to connect to server, w/o any delays. With mny hundreds (and this number easely achievable now fro CUDA enabled hosts) of results in transfer queue there are always some that try to reach server at any given moment.

All that need to be done is to change retry policy from per task to per project basis (as it is for result reporting already). This inefficiency in BOINC leads to increase conncetion problems with overloaded project servers.

(I setted component as Work fetch policy as closest to this component. Actually it's work upload, not fetch, policy)

For more descriptions of this issue look this thread and links in it: http://boinc.berkeley.edu/dev/forum_thread.php?id=4080

Change History

(in reply to: ↑ description ) 07/10/09 06:48:51 changed by Raistmer

More clear description of proposed change in retry logic:

if last result sending for particular project was OK - do next result upload just when it will be available. else delay _ALL_ result uploads for this particular project for some time. repeat cycle.

07/10/09 10:06:08 changed by davea

  • status changed from new to closed.
  • resolution set to fixed.

(In [18593]) - client: restored code for project-wide backoff on file

uploads and downloads. I originally added this on 30 Sept 2005 and disabled it 2 weeks later because there were reports of problems. However, we need this functionality (e.g. on GPU hosts with hundreds of files to upload, we need to back off after a few failures, not try all of them). I added messages (<file_xfer_debug>) so you can see what's going on. Fixes #932.

If this page is incomplete or incorrect, please edit it or add it to the wiki to-do list. To do this, you must be logged in; click Login or Register above.