Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When retrieval data transfer fails, deal remains in Ongoing state #513

Open
dirkmc opened this issue Mar 24, 2021 · 1 comment
Open

When retrieval data transfer fails, deal remains in Ongoing state #513

dirkmc opened this issue Mar 24, 2021 · 1 comment
Labels
x/ignite Issues and PRs being tracked by Team Ignite at Protocol Labs

Comments

@dirkmc
Copy link
Contributor

dirkmc commented Mar 24, 2021

This bug was observed during manual testing.

When trying to make a retrieval deal for a CID with a miner, there was an error saying that there is an existing retrieval deal with the same miner for the same piece CID that is still active. The error message says the deal state is DealStatusOngoing:

lotus client  retrieve --miner f1234 bafykbzacecd3a2hrmxiw4g22ixtwmkfwq32o4cpyzvrogr3rxpna2yazmjbo1 output
> Recv: 0 B, Paid 0 FIL, ClientEventOpen (DealStatusNew)
ERROR: retrieval failed: Retrieve failed: there is an active retrieval deal with peer 12D3KooWQrZnhRaBecSZYKR815zH65xkg1TvfyPWUGYwehHvVFK3 for payload CID bafykbzacecd3a2hrmxiw4g22ixtwmkfwq32o4cpyzvrogr3rxpna2yazmjbo1 (retrieval deal ID 1, state DealStatusOngoing) - existing deal must be cancelled before starting a new retrieval deal

However list-transfers shows that the deal is in the Completed state:

$ lotus client list-transfers --completed
Sending Channels
ID                   Status     Sending To   Root Cid     Initiated?  Transferred  Voucher
1616506229013813701  Completed  ...ehHvVEKB  ...yazmjbo1  Y           583.7MiB     ...qrw5nr23pp5wwjgg2ybwqmot4rjuvgs6xm"}}

Note that in lotus there is currently no way to list retrieval deals or cancel a retrieval deal: filecoin-project/lotus#5870

@dirkmc dirkmc added the x/ignite Issues and PRs being tracked by Team Ignite at Protocol Labs label Mar 24, 2021
@kernelogic
Copy link

I also noticed, if I ctrl+C at client side while the transfer is executing, the miner will continue serve content to I don't know where. Have to manually cancel-transfer on the client side in order to stop the miner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
x/ignite Issues and PRs being tracked by Team Ignite at Protocol Labs
Projects
None yet
Development

No branches or pull requests

2 participants