#819 closed Defect (wontfix)
exponential backoff broken when uploading files
Reported by: | Christian Beer | Owned by: | davea |
---|---|---|---|
Priority: | Major | Milestone: | Undetermined |
Component: | Client - Daemon | Version: | 6.4.5 |
Keywords: | backoff upload | Cc: |
Description
A working CC 6.4.5 on Windows Vista Home Premium. 2 CPU's, GPU deactivated. One Project with work. WiFi network deactivated to see what the client does with the ready to upload files. Here is a short excerpt of the logfile:
03.01.2009 10:48:00|Einstein@Home|Scheduler request failed: Couldn't resolve host name 03.01.2009 10:48:02|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__112_S5R4a_1_0 03.01.2009 10:48:30|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__113_S5R4a_0_0 03.01.2009 10:49:01|Einstein@Home|Sending scheduler request: To fetch work. Requesting 55053 seconds of work, reporting 0 completed tasks 03.01.2009 10:49:04|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__112_S5R4a_1_0 03.01.2009 10:49:06|Einstein@Home|Scheduler request failed: Couldn't resolve host name 03.01.2009 10:49:32|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__113_S5R4a_0_0 03.01.2009 10:50:06|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__112_S5R4a_1_0 03.01.2009 10:50:07|Einstein@Home|Sending scheduler request: To fetch work. Requesting 55459 seconds of work, reporting 0 completed tasks 03.01.2009 10:50:12|Einstein@Home|Scheduler request failed: Couldn't resolve host name 03.01.2009 10:50:34|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__113_S5R4a_0_0 03.01.2009 10:51:08|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__112_S5R4a_1_0 03.01.2009 10:51:13|Einstein@Home|Sending scheduler request: To fetch work. Requesting 55764 seconds of work, reporting 0 completed tasks 03.01.2009 10:51:18|Einstein@Home|Scheduler request failed: Couldn't resolve host name 03.01.2009 10:51:35|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__113_S5R4a_0_0 03.01.2009 10:52:10|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__112_S5R4a_1_0 03.01.2009 10:52:19|Einstein@Home|Sending scheduler request: To fetch work. Requesting 55965 seconds of work, reporting 0 completed tasks 03.01.2009 10:52:24|Einstein@Home|Scheduler request failed: Couldn't resolve host name 03.01.2009 10:52:37|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__113_S5R4a_0_0 03.01.2009 10:53:12|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__112_S5R4a_1_0 03.01.2009 10:53:25|Einstein@Home|Sending scheduler request: To fetch work. Requesting 56370 seconds of work, reporting 0 completed tasks 03.01.2009 10:53:30|Einstein@Home|Scheduler request failed: Couldn't resolve host name 03.01.2009 10:53:39|Einstein@Home|Backing off 1 min 0 sec on upload of h1_0654.45_S5R4__113_S5R4a_0_0
According to PersFileXfer there should be an exponential backoff with this transient error. These two files are representet in client_state.xml as follows:
<file_info> <name>h1_0654.45_S5R4__113_S5R4a_0_0</name> <nbytes>236109.000000</nbytes> <max_nbytes>6000000.000000</max_nbytes> <md5_cksum>618a6c4c8886620c5d5fdf583996061b</md5_cksum> <generated_locally/> <status>1</status> <upload_when_present/> <url>http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/file_upload_handler</url> <persistent_file_xfer> <num_retries>1</num_retries> <first_request_time>1230945486.657211</first_request_time> <next_request_time>1230976541.593010</next_request_time> <time_so_far>510.182392</time_so_far> <last_bytes_xferred>0.000000</last_bytes_xferred> </persistent_file_xfer> <signed_xml> <name>h1_0654.45_S5R4__113_S5R4a_0_0</name> <generated_locally/> <upload_when_present/> <max_nbytes>6000000</max_nbytes> <url>http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/file_upload_handler</url> </signed_xml> <xml_signature> 8f17f585673341537637fe5ce8f98aefd33e1503b89295be1609c0d5cf6adab3 a754c4b7e12a578b8232f867bc986524cad3ffdffb2f541a2b4e85f0229c455a 5e41539f6d87dedad53d7c2a0469cc94a739354fc88dfea1528ea5c31105eea7 ab9674240295b7c341c6c823852ffac0057ae502d644757a3c07333e7b7b873b . </xml_signature> </file_info> <file_info> <name>h1_0654.45_S5R4__112_S5R4a_1_0</name> <nbytes>236119.000000</nbytes> <max_nbytes>6000000.000000</max_nbytes> <md5_cksum>692e7fd85c8c47a10d41d48af5d85f3d</md5_cksum> <generated_locally/> <status>1</status> <upload_when_present/> <url>http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/file_upload_handler</url> <persistent_file_xfer> <num_retries>0</num_retries> <first_request_time>1230956469.291210</first_request_time> <next_request_time>1230976514.199411</next_request_time> <time_so_far>329.128809</time_so_far> <last_bytes_xferred>0.000000</last_bytes_xferred> </persistent_file_xfer> <signed_xml> <name>h1_0654.45_S5R4__112_S5R4a_1_0</name> <generated_locally/> <upload_when_present/> <max_nbytes>6000000</max_nbytes> <url>http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/file_upload_handler</url> </signed_xml> <xml_signature> 5718dde72b830e579bad81dc94d93278af0790c367da002a91261f9781278892 7a42adac3c83eb09339fa60fd0f641971bd7feeb1430613bc249a452c301d331 a176399314b3489a8ad95dec6ba70277e8aa398f189303de580628c76b536859 bddd996174f82411c38babd04e5b9b9aab7d44010edea619f75d1d8ebbea2952 . </xml_signature> </file_info>
I can provide more logs if needed as this happens as soon as I deactivate my network (hardware switch).
Exponential backoff is used when the server is down, not when the network is down.