linkedin / linkedin/ambry

Trigger compaction based on store size

Open
#738 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
1.8k
Forks
298
Avg merge
21h 43m
Merged PRs (30d)
9

Description

Explore ways to trigger compaction based on the how "full" the store is. There should be a mechanism to request compaction (akin to how admin requests to trigger compaction are made) when the store discovers that it is past a certain fill size.

One of the things to keep in mind is that compaction should not get triggered often, a store must be able to determine either if a compaction request will be useful (might be undesirable since it might redo work that compaction will do) or that it is not repeating a request that yielded no results in a previous call.

This also works well in conjunction with #737

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing admin mechanism for requesting compaction and the related work in #737. Define how a store determines that its fill size warrants compaction, avoids repeating ineffective requests, and ensures requests do not trigger compaction unnecessarily often; the issue is complete when that behavior is implemented and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.