linkedin / linkedin/ambry

Server should not be up if too many stores cannot start up

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

Nobody has claimed this yet.

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

Description

Set a threshold for the acceptable number of down stores for a server to even come up. Due to configuration issues or due to multiple disk failures, it is possible that too many stores are unable to start up. In such cases, it is probably wise to not let the server start up. Today, a server can start up even when none of the stores do, which may result in these servers receiving requests they cannot process.

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 tracing the server startup path and how store startup failures are reported. Determine how an acceptable down-store threshold should be configured and enforced, then verify that the server does not come up when too many stores—or all stores—fail to start.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.