You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any file transfer over 8GB, assuming a 1MB chunking strategy, will fail to complete data transfer on miner's side, even if data transfer completes.
If you are importing from an IPFS blockstore and using default 256KB chunking strategy, anything over 2GB will fail
To Reproduce
Steps to reproduce the behavior:
Create a deal for a file over 8GB
On miner side, even after data transfer completes, miner will stay stuck at StorageDealTransferring
Expected behavior
The data transfer completes
Version (run lotus version):
All lotus versions >= 1.0.0
Additional context
If you look in the miner logs, you find an error level message that reads contains Executing event planner failed: Slice value in field t.ReceivedCids was too long
What's happening here is as follows:
We are recording CIDs received on the miner in order to be able to resume a data transfer by passing the list of CIDs already traversed to go-graphsync in the case of a restart
We are recording them in the ChannelState, which is a CBOR encoded data structure in the data store where the CIDs received is an array data field, and the cbor encoding is done by cbor-gen
Cbor-gen has a hard limit of 8192 on arrays
The text was updated successfully, but these errors were encountered:
Describe the bug
Any file transfer over 8GB, assuming a 1MB chunking strategy, will fail to complete data transfer on miner's side, even if data transfer completes.
If you are importing from an IPFS blockstore and using default 256KB chunking strategy, anything over 2GB will fail
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The data transfer completes
Version (run
lotus version
):All lotus versions >= 1.0.0
Additional context
If you look in the miner logs, you find an error level message that reads contains
Executing event planner failed: Slice value in field t.ReceivedCids was too long
What's happening here is as follows:
The text was updated successfully, but these errors were encountered: