Snapchat/KeyDB

Refactor Code to Use “Replica”

Open

#75 opened on Aug 23, 2019

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C++ (495 forks)batch import
good first issue

Repository metrics

Stars
 (8,383 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

This tracks renaming any code still using the old master/slave terminology where back compat is not affected.

The older terminology is divisive and that’s not what KeyDB is about. On top of that “Replica” is simply a more descriptive name especially now that replicas can also push changes with Active Replication.

Contributor guide

Research direction
Search the codebase for occurrences of 'master' and 'slave' that can be safely renamed to 'replica' without affecting backward compatibility. Use grep or similar tools to identify files, then update variable names, comments, and documentation. Ensure no API or configuration changes break existing users.
Tech stack
cpp
Domain
databasebackend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85