Change default parameters for better mean-time-to-recovery (MTTR)

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes
Domain
databases, infrastructure

Research direction

Start by reviewing the HBase MTTR documentation, HBASE-21186, and the referenced Ambari hbase-site.xml configuration. Check which parameters exist in the operator, whether they are needed, and whether the suggested values remain appropriate. Done means the defaults are justified and updated where needed, with any upstream documentation fixes identified for contribution.

Written by the indexing model from the issue text.

Description

customer-request refinement-needed

HBase has a few knobs that can be turned to improve the time it takes to recover from failure.

These are documented here:

As part of this issue we need to check whether all of these parameters still exist, whether they are still needed and whether the values suggested still make sense.

If not we should also contribute documentation fixes upstream.

Dominant language
Rust
Stars
21
Forks
6
Avg merge
1d 19h
Merged PRs (30d)
9

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.

More from stackabletech/hbase-operator

All issues in stackabletech/hbase-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.