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

M1: miner with 2k deals but 0 migrated to dagstore #7017

Closed
4 tasks done
raulk opened this issue Aug 10, 2021 · 2 comments
Closed
4 tasks done

M1: miner with 2k deals but 0 migrated to dagstore #7017

raulk opened this issue Aug 10, 2021 · 2 comments
Labels
kind/bug Kind: Bug P1 P1: Must be resolved team/ignite Issues and PRs being tracked by Team Ignite at Protocol Labs
Milestone

Comments

@raulk
Copy link
Member

raulk commented Aug 10, 2021

Checklist

  • This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
  • I am reporting a bug w.r.t one of the M1 tags. If not, choose another issue option here.
  • I am not reporting a bug around deal making. If yes, create a M1 Bug Report For Deal Making.
  • I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.

Lotus component

Other

Lotus Tag and Version

m1.3.4

Describe the Bug

Miner has 2697 deals:

2021-08-11T00:46:06.057+0900	INFO	dagstore.migrator	dagstore/wrapper.go:286	registering shards for all active deals in sealing subsystem	\{"count": 2697\}\

However, the migrator reports a nil PieceCID for all deals:

2021-08-11T00:46:06.057+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 2202633\}\
2021-08-11T00:46:06.058+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 0\}\
2021-08-11T00:46:06.058+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 0\}\
2021-08-11T00:46:06.058+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 0\}\
2021-08-11T00:46:06.058+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 0\}\
2021-08-11T00:46:06.058+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 2252899\}\
2021-08-11T00:46:06.058+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 0\}\
2021-08-11T00:46:06.058+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 0\}\
2021-08-11T00:46:06.058+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 0\}\
2021-08-11T00:46:06.058+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 0\}\
2021-08-11T00:46:06.058+0900	WARN	dagstore.migrator	dagstore/wrapper.go:335	deal has nil piece CID; skipping	\{"deal_id": 0\}\

Leading to all deals being skipped on migration:

2021-08-11T00:46:06.095+0900	INFO	dagstore.migrator	dagstore/wrapper.go:361	finished registering all shards	\{"total": 0\}\

And a total of 0 deals migrated to the dagstore.

Logging Information

See above.

Repo Steps

No response

@raulk
Copy link
Member Author

raulk commented Aug 10, 2021

Found the bug on a debugging session with @hannahhoward.

This check is incorrect:

if deal.Ref.PieceCid == nil {

We should be using deal.Proposal.PieceCID, which is guaranteed to be non-nil.

It is not clear to me why this hadn't been reported up until now.

@jennijuju jennijuju added epic/sharded-dag-store P1 P1: Must be resolved team/ignite Issues and PRs being tracked by Team Ignite at Protocol Labs and removed need/triage labels Aug 10, 2021
@jennijuju jennijuju added this to the v1.11.2 milestone Aug 10, 2021
raulk added a commit that referenced this issue Aug 10, 2021
@raulk
Copy link
Member Author

raulk commented Aug 10, 2021

Fixed in d3cf5b0.

@raulk raulk closed this as completed Aug 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Kind: Bug P1 P1: Must be resolved team/ignite Issues and PRs being tracked by Team Ignite at Protocol Labs
Projects
None yet
Development

No branches or pull requests

2 participants