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

some messages in mpool disappeared #3789

Closed
NealLiu-Test2 opened this issue Sep 12, 2020 · 2 comments
Closed

some messages in mpool disappeared #3789

NealLiu-Test2 opened this issue Sep 12, 2020 · 2 comments

Comments

@NealLiu-Test2
Copy link

Describe the bug
in space race, my miner id is t02490,
worker address is t3qlp7se6vaw6yg3sjm2pme3xbfw7avhjng2ilmkejujbmxrsv7v5netdonvcrj5rez5epawkxpnzaei27esna.
messages in mpool is begin from 69011, but in filfox.io and other explorer, the biggest Nonce i can found is 68980. the messages with Nonce 68981-69010 were disappeared , neither on the chain nor in the mpool. messages in mpool cannot go to the chain now. because there is no messages with 68981.....................

To Reproduce
Steps to reproduce the behavior:

  1. I used lotus mpool replace to increase the gas of some message , so let them go to the chain.
  2. after running some lotus mpool replace commands, i found messages with Nonce 68981-69010 were disappeared.

Expected behavior
is this a bug ? how can i find the disappeared messages back?

Screenshots
https://filecoinproject.slack.com/files/U0197DEDKLN/F01AKC1H1T4/image.png

Version (run lotus version):
lotus version 0.7.0+git.232cc320

Additional context
Add any other context about the problem here.

@NealLiu-Test2 NealLiu-Test2 changed the title messages in mpool disappear some messages in mpool disappeared Sep 12, 2020
@NealLiu-Test2
Copy link
Author

after restarting the daemon, the lost messages finally go to the chain, but several hours have passed since them disappeared. if i dont restart the daemon, it will never go to the chain. this must be a bug!

@vyzo
Copy link
Contributor

vyzo commented Sep 12, 2020

it's a bug, and it has been fixed in #3772 (it's merged in master).

@vyzo vyzo closed this as completed Sep 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants