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

Add UUID to message sent to chain node #9171

Closed
5 of 14 tasks
shrenujbansal opened this issue Aug 15, 2022 · 0 comments · Fixed by #9174
Closed
5 of 14 tasks

Add UUID to message sent to chain node #9171

shrenujbansal opened this issue Aug 15, 2022 · 0 comments · Fixed by #9174
Labels
kind/feature Kind: Feature

Comments

@shrenujbansal
Copy link
Contributor

shrenujbansal commented Aug 15, 2022

Checklist

  • This is not a new feature or an enhancement to the Filecoin protocol. If it is, please open an FIP issue.
  • This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
  • I have a specific, actionable, and well motivated feature request to propose.

Lotus component

  • lotus daemon - chain sync
  • lotus miner - mining and block production
  • lotus miner/worker - sealing
  • lotus miner - proving(WindowPoSt)
  • lotus miner/market - storage deal
  • lotus miner/market - retrieval deal
  • lotus miner/market - data transfer
  • lotus client
  • lotus JSON-RPC API
  • lotus message management (mpool)
  • Other

What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

If a lotus daemon sends a message to the blockchain but fails to confirm it with the miner and the subsequent failure needs to be investigated.
We should add retries to let the system recover but don't want the miner to accidentally send the same message twice

Describe the solution you'd like

Add a UUID to each message sent by the miner to the daemon
The daemon can then check if the message being retried by the miner has already been processed and sent to the chain

Describe alternatives you've considered

No response

Additional context

This is a requirement for #9130

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Kind: Feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant