Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S ssg
  • 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 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • sds
  • ssg
  • Issues
  • #6

Closed
Open
Created Jul 03, 2017 by Shane Snyder@ssnyderOwner

add raft support to SSG

SSG+SWIM will allow for us to provide weakly-consistent group membership views across an SSG group, but that might not be enough for all use cases -- some services are likely going to require strict ordering of group membership changes.

We should investigate how the RAFT protocol can be integrated into SSG as a consensus component responsible for ordering membership updates.

Our Intel friends have already forked and improved a publicly available Raft implementation, with their fork available here: https://github.com/daos-stack/raft

Assignee
Assign to
Time tracking