[X] This is not a security-related bug/issue. If it is, please follow please follow the security policy.
[X] This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
[X] This is not a new feature request. If it is, please file a feature request instead.
[X] This is not an enhancement request. If it is, please file a improvement suggestion instead.
[X] I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
[X] I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
[X] I did not make any code changes to lotus.
Lotus component
[ ] lotus daemon - chain sync
[ ] lotus miner - mining and block production
[ ] lotus miner/worker - sealing
[ ] lotus miner - proving(WindowPoSt)
[X] lotus miner/market - storage deal
[X] lotus miner/market - retrieval deal
[ ] lotus miner/market - data transfer
[ ] lotus client
[ ] lotus JSON-RPC API
[ ] lotus message management (mpool)
[ ] Other
Lotus Version
Daemon: 1.13.0-rc2+mainnet+git.a1a7ea66c+api1.4.0
Local: lotus version 1.13.0-rc3+mainnet+git.c23cff45f
Describe the Bug
If the storage provider receives retrievals that stops due to for example a stream reset, it seems to impact later incoming storage-deals to not start the transfer. I have experienced this behavior twice, so thought it was worthy a ticket.
So this was my view of lotus-miner data-transfers list:
Sending Channels
ID Status Sending To Root Cid Initiated? Transferred Voucher
1634579593870108898 Ongoing ...m5rYc8VD ...3zpbzada N 31.94MiB ...lIncrease":1048576,"UnsealPrice":"0"}
Message: stream reset
1634580045873407428 Ongoing ...m5rYc8VD ...3zpbzada N 362.5MiB ...lIncrease":1048576,"UnsealPrice":"0"}
Message: stream reset
1634580530481520217 Ongoing ...m5rYc8VD ...kpmoyiim N 2.658MiB ...lIncrease":1048576,"UnsealPrice":"0"}
Message: stream reset
1634597923690491082 Ongoing ...m5rYc8VD ...5ozef35m N 21.99GiB ...lIncrease":1048576,"UnsealPrice":"0"}
Message: stream reset
Receiving Channels
ID Status Receiving From Root Cid Initiated? Transferred Voucher
1631206380224510302 Ongoing ...iTLZXDjt ...6v3dmo6m N 0B ...m2pq2qxf25n3jmpo4bmu5wjudnsy5up7yy"}}
1634604531202059314 Ongoing ...bc8Hs8Nd ...ahxxky3a N 0B ...bujb74qtmegatn3cf77ptei46kgpalfnbi"}}
Message: graphsync request cancelled
1634622720975052977 Ongoing ...MTqHYBjw ...qnpM3JX1 N 0B ...nlufzhrvyrhbyudklwxtkrkpmtygmkkmni"}}
Message: graphsync request cancelled
All the receiving storage deals came after the retrievals had stalled. The first time I experienced this, a full clean-up off all the transfers (cancelling retrievals & receiving channels), and a restart of the markets-node made incoming storage-deals transfer again.
Not seen this issue on the upcoming release candidates for 1.13.2. Retrievals does not seem to stop new incoming storage deals on release-candidate 2 and up!
Checklist
Latest release
, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.Lotus component
Lotus Version
Describe the Bug
If the storage provider receives retrievals that stops due to for example a
stream reset
, it seems to impact later incoming storage-deals to not start the transfer. I have experienced this behavior twice, so thought it was worthy a ticket.So this was my view of
lotus-miner data-transfers list
:All the receiving storage deals came after the retrievals had stalled. The first time I experienced this, a full clean-up off all the transfers (cancelling retrievals & receiving channels), and a restart of the markets-node made incoming storage-deals transfer again.
Logging Information
Repo Steps