Opened at 2015-10-15T11:01:29Z
Last modified at 2016-03-21T17:24:35Z
#2537 closed defect
magic-folder: implement download retry — at Version 4
Reported by: | dawuud | Owned by: | daira |
---|---|---|---|
Priority: | normal | Milestone: | undecided |
Component: | code-frontend-magic-folder | Version: | 1.10.1 |
Keywords: | magic-folder download downloader retry reliability blocks-merge | Cc: | |
Launchpad Bug: |
Description (last modified by dawuud)
The downloader should retry if the operation fails... this can happen because of lossy networks such as wifi causing the tcp connections to storage servers to drop. Foolscap handles reconnection with exponential backoff... however the application layer still needs to retry... otherwise the user will experience our software as brittle.
Change History (4)
comment:1 Changed at 2015-10-15T11:51:41Z by dawuud
comment:2 Changed at 2015-10-15T13:10:15Z by daira
Note that this is not part of the OTF grant (milestones 1-6).
comment:3 Changed at 2015-10-27T20:21:02Z by daira
See also #2420.
comment:4 Changed at 2016-01-18T21:10:18Z by dawuud
- Description modified (diff)
- Summary changed from magic-folder: implement download/upload retry to magic-folder: implement download retry
Note: See
TracTickets for help on using
tickets.
i started to write an experimental test for the upload retry here in this dev branch: https://github.com/david415/tahoe-lafs/tree/2537.upload-download-retry.0
hmm but maybe the nonetwork grid isn't appropriate for testing connectivity retry?