Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • S swh-objstorage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Platform
  • Development
  • swh-objstorage
  • Issues
  • #3057
Closed
Open
Issue created Feb 17, 2021 by Loïc Dachary@dachary

Using seaweedfs to store objects

The metadata are in the master service which is a custom database. It must be updated when an object is written and read must lookup this database to figure out on which volume to get the data.

The metadata database is a implemented in seaweedfs. It is strongly consistent (Raft), meaning that the leader handles all writes and acknowledges an update once all running servers have a copy. Reads can be from any servers.

The test coverage is unclear and appears to be low. There does not seem to be integration tests.


Migrated from T3057 (view on Phabricator)

Assignee
Assign to
Time tracking