Real Device Single File Task Download Crash

Problem Description

After a real device single-file download task is configured and runs for a period of time, the report shows no data. The following analysis explains the cause.

Analysis

When a report has no data, first check whether the task configuration is abnormal.

Check the report data. There are no special configuration items.

Check whether task scheduling, delivery, and data storage are normal. The storage rate is 0%.

Test the URL locally with Postman.

Multiple local tests show that downloading 50 MB of data takes more than 300 seconds, which indicates a task timeout.

Because the file is too large, download only part of it to test the behavior. Add a Range header and request the first 10 MB. The range request does not take effect, and the full 50 MB file is still downloaded.

Confirm the mechanism with the backend team.

Mechanism: for cost control, real device monitoring supports a maximum single-file download size of 20 MB.

Root Cause

The customer URL points to a 50 MB file, while Tingyun supports a maximum single-file download size of 20 MB for real device monitoring. The download times out, so data cannot be returned and the task fails.

Adding the Range header does not work because the customer URL includes a size field that forces the corresponding number of bytes to be downloaded.

Solution

Adjust the test file size to less than 20 MB.

Real Device Single File Task Download Crash

Problem Description#

Analysis#

Root Cause#

Solution#

Problem Description

Analysis

Root Cause

Solution