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

lnd: ensure that LND won't start in native SQL mode if it has any KV invoices #8568

Merged

Conversation

bhandras
Copy link
Collaborator

This PR is a temporary measure for 0.18 as we don't plan to add invoice migration yet for native SQL invoice DB.

Copy link

coderabbitai bot commented Mar 19, 2024

Important

Auto Review Skipped

Auto reviews are limited to the following labels: llm-review. Please add one of these labels to enable auto reviews.

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.

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>.
    • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@bhandras bhandras added the database Related to the database/storage of LND label Mar 19, 2024
@bhandras bhandras self-assigned this Mar 19, 2024
@bhandras bhandras added this to the v0.18.0 milestone Mar 19, 2024
@bhandras bhandras force-pushed the native-sql-ensure-empty-invoicedb branch from a6e6a00 to 55b3b85 Compare March 19, 2024 14:30
@saubyk saubyk requested review from a team, bitromortac, ziggie1984 and ellemouton and removed request for a team and ziggie1984 March 19, 2024 14:38
@bhandras bhandras force-pushed the native-sql-ensure-empty-invoicedb branch from 55b3b85 to 751caa1 Compare March 20, 2024 07:33
Copy link
Collaborator

@ellemouton ellemouton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! tACK 🚀

One comment about re-using the passed in context instead.

Then as mentioned offline: realised that we dont do this check the other way around (ie it is possible to add native sql invoice & then remove the flag and it will go back to adding kvdb invoices). But Andras pointed out that this is already the case with any backend change we have today. So potentially not needed to be that defensive especially cause in future when we add migration scripts, then we do want to allow this 👍

// start lnd with native SQL enabled, as we don't currently
// migrate the invoices to the new database schema.
invoiceSlice, err := dbs.GraphDB.QueryInvoices(
context.Background(), invoices.InvoiceQuery{
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think you can instead use the context that is already available

Copy link
Collaborator Author

@bhandras bhandras Mar 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed, thanks :)

Comment on lines +127 to +128
return fmt.Errorf("cannot use native SQL with bolt " +
"backend")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙏

This commit adds a check to ensure that we don't start LND with native
SQL invoice DB if we already have any invoices in our KV channeldb. This
is needed as native SQL invoices is an experimental feature and we do
not yet support migration.
@bhandras bhandras force-pushed the native-sql-ensure-empty-invoicedb branch from 751caa1 to 483f5f3 Compare March 20, 2024 07:46
Copy link
Collaborator

@bitromortac bitromortac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🎉. Only to clarify, it doesn't matter if the database contained any invoices that were deleted, we just require that it is empty?

@bhandras
Copy link
Collaborator Author

LGTM 🎉. Only to clarify, it doesn't matter if the database contained any invoices that were deleted, we just require that it is empty?

Good question! As deleted invoices are completely removed from the KV invoice DB, it'd be fine. We could be more strict by not even caring about the invoice DB, but only about whether this is a first ever start of the node. I believe the current approach is quite liberal in that it allows "old" nodes to also use the native schema (given no invoices).

@bhandras
Copy link
Collaborator Author

bhandras commented Mar 20, 2024

LGTM! tACK 🚀

One comment about re-using the passed in context instead.

Then as mentioned offline: realised that we dont do this check the other way around (ie it is possible to add native sql invoice & then remove the flag and it will go back to adding kvdb invoices). But Andras pointed out that this is already the case with any backend change we have today. So potentially not needed to be that defensive especially cause in future when we add migration scripts, then we do want to allow this 👍

Thanks for the testing and discussion! :) I agree that we could be more strict about preconditions, see also my other comment above. I'm also open to changing things up if you both think more strict checking is better.

@bitromortac
Copy link
Collaborator

Good question! As deleted invoices are completely removed from the KV invoice DB, it'd be fine. We could be more strict by not even caring about the invoice DB, but only about whether this is a first ever start of the node. I believe the current approach is quite liberal in that it allows "old" nodes to also use the native schema (given no invoices).

The only thing that would get out of sync would be the add index (if I understand that correctly). I think keeping that liberal approach is ok, while being somewhat defensive against accidentally mixing native with the preexisting kv db 👍.

@guggero guggero merged commit 23f5f3c into lightningnetwork:master Mar 20, 2024
25 of 27 checks passed
@bhandras bhandras deleted the native-sql-ensure-empty-invoicedb branch March 20, 2024 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database Related to the database/storage of LND
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

4 participants