filecoin-project/dealbot

Repeated storage/retrieval deal scheduling

Open

#336 opened on Nov 9, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (8 forks)github user discovery
P1good first issueworkstream/general

Repository metrics

Stars
 (34 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Expected behavior When a storage + retrieval deal is schedule in the following way:

  • SP fXXXXXX will receive 1 storage deal at 1405 UTC every day for the next 30 days (720h)
  • for each of these storage deals, 3 retrieval deals will be attempted (every 24h for 72h)
  • the first retrieval will fail since the timestamps are the same -> expectations are therefore that:
    • total attempted storage deals: 30
    • total attempted retrievals: 90
    • total guaranteed failed retrievals: 30
    • realistic retrieval attempts: 60
    • daily deals at peak: 1 storage deal + 4 retrievals (T-0, T-24, T-48, T-72)

Is this right? If not we should:

  • adjust expectations accordingly
  • OR adjust behavior for the controller

Contributor guide

Research direction
Examine the deal scheduling logic in the dealbot codebase to verify if the expected numbers of storage and retrieval deals match the behavior. Trace the scheduling algorithm, focusing on the interaction between storage deal scheduling and retrieval deal attempts.
Tech stack
go
Domain
backendblockchain
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65