stackabletech / stackabletech/hbase-operator
Change default parameters for better mean-time-to-recovery (MTTR)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 6
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 9
Description
HBase has a few knobs that can be turned to improve the time it takes to recover from failure.
These are documented here:
- https://hbase.apache.org/book.html#mttr
- https://issues.apache.org/jira/browse/HBASE-21186
- https://github.com/apache/ambari/blob/1fb531c31e86688d5d3a696d4ad6d07921d99aa1/ambari-server/src/main/resources/stacks/BIGTOP/3.2.0/services/HBASE/configuration/hbase-site.xml#L4
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100