feat(f3): log when gaining/losing participation leases #12581
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Log whenever we start/stop participating for a storage miner in F3. Given that we use overlapping leases, we expect that we'll start participating for a miner on start then continue to participate over time.
This could get a bit noisy for setups that constantly switch between different lotus nodes but there's not much I can do about that and this will really help with debugging.
Checklist
Before you mark the PR ready for review, please make sure that: