linkedin/cruise-control

Dynamically change replication throttle for an on-going rebalance

Open

#929 opened on Sep 3, 2019

View on GitHub
 (11 comments) (10 reactions) (0 assignees)Java (649 forks)auto 404
functionalitygood first issuerobustness

Repository metrics

Stars
 (3,036 stars)
PR merge metrics
 (PR metrics pending)

Description

Now that we have support for replication throttle (https://github.com/linkedin/cruise-control/pull/748, thanks again @aaronlevin-stripe), I thought it would be great to have a way to change a throttle in the middle of a rebalance.

In cases where you set one throttle but later realized it wasn't satisfactory (e.g things going too slow or too unstable), it is invaluable to have a quick way to revert it.

I thought adding a new endpoint for updating throttle (or maybe extending /admin?) may be straightforward to do. What are people's thoughts on this?

Contributor guide

Research direction
Look into the existing admin endpoint and replication throttle implementation in cruise control to design and add a new endpoint for dynamically updating the throttle during a rebalance.
Tech stack
java
Domain
backendapi
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.
1-2 days
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.
Mostly clear
Prerequisites
JavaKafkaREST API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65