Skip to content

Conversation

liquid-helium
Copy link
Contributor

This is a WIP checkpoint commit for the async blob upload feature that allows clients to receive blob certificates immediately after achieving quorum while continuing background uploads to remaining storage nodes.

Key changes:

  • Add AsyncUploadConfig for configuring async upload behavior
  • Implement AsyncUploader for background task management
  • Add AsyncUploadWrapper for channel-based certificate communication
  • Update ClientConfig with async upload configuration options
  • Add comprehensive test coverage and examples
  • Update configuration files with async upload settings

The feature enables improved user experience by reducing perceived upload latency while maintaining data durability through continued replication in the background.

🤖 Generated with Claude Code

Description

Describe the changes or additions included in this PR.

Test plan

How did you test the new or updated feature?


Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that
a user might notice and any actions they must take to implement updates. (Add release notes after the colon for each item)

  • Storage node:
  • Aggregator:
  • Publisher:
  • CLI:

Copy link
Contributor

Warning: This PR modifies one of the example config files. Please consider the
following:

  • Make sure the changes are backwards compatible with the current configuration.
  • Make sure any added parameters follow the conventions of the existing parameters; in
    particular, durations should take seconds or milliseconds using the naming convention
    _secs or _millis, respectively.
  • If there are added optional parameter sections, it should be possible to specify them
    partially. A useful pattern there is to implement Default for the struct and derive
    #[serde(default)] on it, see BlobRecoveryConfig as an example.
  • You may need to update the documentation to reflect the changes.

This is a WIP checkpoint commit for the async blob upload feature that allows
clients to receive blob certificates immediately after achieving quorum while
continuing background uploads to remaining storage nodes.

Key changes:
- Add AsyncUploadConfig for configuring async upload behavior
- Implement AsyncUploader for background task management
- Add AsyncUploadWrapper for channel-based certificate communication
- Update ClientConfig with async upload configuration options
- Add comprehensive test coverage and examples
- Update configuration files with async upload settings

The feature enables improved user experience by reducing perceived upload
latency while maintaining data durability through continued replication
in the background.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@liquid-helium liquid-helium force-pushed the heliu/async-upload-blob-data branch from ab36a0d to cb113ce Compare September 11, 2025 17:44
Copy link
Contributor

PR Preview Action v1.6.2

🚀 View preview at
https://MystenLabs.github.io/walrus/pr-preview/pr-2514/

Built to branch gh-pages at 2025-09-11 17:45 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

Copy link
Contributor

This PR is stale because it has been open 14 days with no activity. It will be closed in 7 days unless you remove the stale label, add the do-not-close label, or comment on it.

@github-actions github-actions bot added the stale label Sep 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant