Closed 1037husterljx closed 2 years ago
When the depth of candidateParent or peer is defaultDepthLimit (4), scheduling will fail no matter how and triggering RetryLimit returns 5006 error
Regardless of the depth, it should be possible to schedule successfully.
Use 60 clients and three seed peers to start downloading 1G tasks at the same time, dyconfig loadlimit = 15
uname -a
Quick Solution: Deletes the current peer depth calculation for the depth limit.
Future Solution: Task uses a DAG(Directed Acyclic Graph) for abstraction.
Bug report:
When the depth of candidateParent or peer is defaultDepthLimit (4), scheduling will fail no matter how and triggering RetryLimit returns 5006 error
Expected behavior:
Regardless of the depth, it should be possible to schedule successfully.
How to reproduce it:
Use 60 clients and three seed peers to start downloading 1G tasks at the same time, dyconfig loadlimit = 15
Environment:
uname -a
):