superfly/corrosion

Explore priority broadcasts

Closed

#148 opened on Jan 31, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (83 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (1,817 stars)
PR merge metrics
 (PR metrics pending)

Description

Broadcasts are all treated the same in Corrosion right now. However, nodes will broadcast their local changes to neighboring nodes immediately instead of randomly and eventually.

A concept of "priority" could be added for broadcasts to neighboring nodes.

When a node receives a priority broadcast, it should apply it immediately instead of queueing it to later batch insert it with other changes.

This is useful for faster eventual consistency "where it matters". It's likely a client interacting with a Corrosion node will be affecting data required on another node in close proximity.

Contributor guide

Research direction
Understand the current broadcast mechanism in Corrosion, then design a priority queue for broadcasts to neighboring nodes that are applied immediately. Study the node's message handling pipeline to see where to integrate priority handling.
Tech stack
rust
Domain
distributed systemsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustDistributed SystemsGossip Protocols
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30