Skip to content

Add lazy persistence back to KVStore::delete #4188

Closed

Description

@TheBlueMatt

This is from discord:

  • Should all deletes be performed in a lazy fashion now? I noticed the lazy flag was removed in Remove lazy flag from {KVStore,KVStoreSync}::remove #4116. I was surprised it was described as having no utility, as we ran into issues where a large channel monitor update consolidation (e.g. with maximumpendingupdates = 1000) would block other tasks from continuing if the 1000 deletes were performed sequentially in a non-lazy fashion. This might apply most to the sync fn use-case though.

Activity

  1. added this to the 0.2 milestone on Oct 29, 2025
  2. added a commit that references this issue on Oct 30, 2025
    42152a9
  3. linked a pull request that will close this issueRestore `lazy` flag to `KVStore::remove` #4189on Oct 30, 2025
  4. added a commit that references this issue on Oct 30, 2025
    3b4c2ff
  5. added a commit that references this issue on Oct 30, 2025
    75b0b53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions