Don't block on channel arbitator startup by ziggie1984 · Pull Request #9324 · lightningnetwork/lnd

ziggie1984 · 2024-11-29T23:43:29Z

Replaces #9262

Fixes: #9323

coderabbitai · 2024-11-29T23:43:36Z

Important

Review skipped

Auto reviews are limited to specific labels.

🏷️ Labels to auto review (1)

llm-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

guggero

Thanks a lot for looking into this. I think we can simplify the code somewhat and also reduce the number of goroutines a bit, see inline comment.

yyforyongyu

Left some comments here, I don't think the fix should happen in lnd. From the logs, what happened was the chan newInputs was blocked since we sent two inputs during the startup, and the first input was blocking on aux.ExtraBudgetForInputs,

2024-11-29 10:15:07.185 [INF] SWPR: Sweep request received: out_point=e4a01568a0cd879df94cd6c9ae8143e1304bf1731ddee7003c6f12df4f7baf13:0, witness_type=TaprootAnchorSweepSpend, relative_time_lock=0, absolute_time_lock=0, amount=0.00000330 BTC, parent=(<nil>), 
...
2024-11-29 10:15:07.192 [INF] CNCT: ChannelArbitrator(ce3ab677a419e40558d095faf7165ba143467c1dc5691632ad511224473eabc9:0): offering anchor from local commitment 7a4c66554f168a903202ed29e2a13e1061b8c0f484a4be7a2ef8d69ceac382c5:1 to sweeper with deadline=None, budget=0.00000330 BTC
2024-11-29 10:15:07.192 [INF] SWPR: Sweep request received: out_point=7a4c66554f168a903202ed29e2a13e1061b8c0f484a4be7a2ef8d69ceac382c5:1, witness_type=TaprootAnchorSweepSpend, relative_time_lock=0, absolute_time_lock=0, amount=0.00000330 BTC, parent=(fee=0.00001366 BTC, weight=958 wu), params=(startingFeeRate={false 0}, immediate=false, exclusive_group=948947804208955392, budget=0.00000330 BTC, deadline=none)

There are multiple ways we can fix this,

make newInputs a buffered chan, which will defeat blockbeat as we no longer guarantee the order channel arbitrator offers -> sweeper sweeps.
we could instead remove the advanceState in the ChannelArbitrator.Start since the channels will be handled in the main goroutine channelAttendant anyway.
fix it in the tapd side, which feels more appropriate as if the calls to methods of the AuxSweeper are blocking, we may have had some incorrect assumptions when using them in the sweeper.

yyforyongyu

I tested out the second idea here, turns out it's a small change, and all the itests passed!

ziggie1984

Have some questions in terms of this new introduced behaviour, we are altering the lnd daemon logic slightly, which I think is ok and actually a better way to go instead of shutting down LND in case the startup of one arbitrator fails.

ziggie1984 · 2024-12-03T14:53:05Z

+	if err != nil {
+		log.Errorf("Unable to progress state machine after "+
+			"restart: %v", err)
+		return
+	}


This is a code change behaviour:

Previously we would not startup if the broadcast of the channel commitment failed, now we are just logging an error but we still continue running the daemon.

If we want to restore the behavior, we can use Criticalf here.

I kinda like this new approach, so if everybody is ok with it, I would favour not shutting down if one arbitrator fails

Roasbeef · 2024-12-03T15:10:26Z

+	if err != nil {
+		log.Errorf("Unable to progress state machine after "+
+			"restart: %v", err)
+		return
+	}


If we want to restore the behavior, we can use Criticalf here.

ziggie1984 · 2024-12-03T16:18:48Z

CI passed in the previous run, so I think this is gtg as soon as we have consensus whether we shutdown LND if a channel arbitrator fails to start or we just log an error and continue the process nonetheless.

yyforyongyu

LGTM🦾 Thanks for the quick fix!

guggero

Nice, very clean solution, LGTM 🎉

We decouple the state machine of the channel arbitrator from the start-up process so that we can startup the whole daemon reliably.

Roasbeef

LGTM 🦂

ziggie1984 force-pushed the non-blocking-startup-chan-arbitrator branch 2 times, most recently from 2f28012 to c1dc62b Compare November 30, 2024 10:10

ziggie1984 marked this pull request as ready for review November 30, 2024 10:11

ziggie1984 requested review from guggero and yyforyongyu November 30, 2024 10:11

guggero added this to the v0.18.4 milestone Dec 1, 2024

guggero added bug fix init Issues related to LND startup custom chans labels Dec 1, 2024

guggero reviewed Dec 2, 2024

View reviewed changes

Comment thread docs/release-notes/release-notes-0.19.0.md Outdated

Comment thread contractcourt/chain_arbitrator.go Outdated

yyforyongyu requested changes Dec 2, 2024

View reviewed changes

Comment thread contractcourt/chain_arbitrator.go Outdated

yyforyongyu reviewed Dec 2, 2024

View reviewed changes

dstadulis assigned ffranr and ziggie1984 and unassigned ffranr Dec 3, 2024

ziggie1984 force-pushed the non-blocking-startup-chan-arbitrator branch from c1dc62b to 7efaffe Compare December 3, 2024 14:50

ziggie1984 commented Dec 3, 2024

View reviewed changes

ziggie1984 requested review from guggero and yyforyongyu December 3, 2024 14:54

Roasbeef reviewed Dec 3, 2024

View reviewed changes

ziggie1984 force-pushed the non-blocking-startup-chan-arbitrator branch 3 times, most recently from 514f29e to 2905de9 Compare December 3, 2024 16:16

yyforyongyu approved these changes Dec 3, 2024

View reviewed changes

Comment thread contractcourt/channel_arbitrator.go

ziggie1984 force-pushed the non-blocking-startup-chan-arbitrator branch from 2905de9 to 8235f83 Compare December 3, 2024 21:14

guggero approved these changes Dec 4, 2024

View reviewed changes

guggero requested a review from Roasbeef December 4, 2024 16:47

Roasbeef requested changes Dec 5, 2024

View reviewed changes

Comment thread contractcourt/channel_arbitrator.go

ziggie1984 added 2 commits December 5, 2024 15:11

contractcourt: refactor start up of arbitrators

17bc882

We decouple the state machine of the channel arbitrator from the start-up process so that we can startup the whole daemon reliably.

docs: add release-notes

0004e31

ziggie1984 force-pushed the non-blocking-startup-chan-arbitrator branch from 8235f83 to 0004e31 Compare December 5, 2024 14:11

ziggie1984 requested a review from Roasbeef December 5, 2024 14:11

Roasbeef approved these changes Dec 5, 2024

View reviewed changes

Roasbeef merged commit 8d7f085 into lightningnetwork:master Dec 5, 2024

guggero mentioned this pull request Dec 5, 2024

release: create branch for v0.18.4-beta.rc2 #9335

Merged

ziggie1984 mentioned this pull request Sep 17, 2025

[bug]: On restart LND attempts to broadcast different FC tx for already closing channel, shuts down #8850

Closed

Conversation

ziggie1984 commented Nov 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot commented Nov 29, 2024

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

Uh oh!

guggero left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

yyforyongyu left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

yyforyongyu left a comment

Choose a reason for hiding this comment

Uh oh!

ziggie1984 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

ziggie1984 Dec 3, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Roasbeef Dec 3, 2024

Choose a reason for hiding this comment

Uh oh!

ziggie1984 Dec 3, 2024

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Roasbeef Dec 3, 2024

Choose a reason for hiding this comment

Uh oh!

ziggie1984 commented Dec 3, 2024

Uh oh!

yyforyongyu left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

guggero left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Roasbeef left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

ziggie1984 commented Nov 29, 2024 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)

ziggie1984 Dec 3, 2024 •

edited

Loading