stackabletech / stackabletech/hive-operator
The metastore offers replicas > 1 but no HA ist configured
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 29
- Forks
- 2
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 12
Description
Currently, the Hive metastore can be configured with multiple replicas > 1 per role group. This results in the feeling for high availability. The service discovery to offers multiple FQDN's to different (and completely unrelated) metastores (https://github.com/stackabletech/hive-operator/pull/145).
We should consolidate the behavior and have two options:
- Fix
replicasto 1 and offer a warning if set > 1. Add in the documentation that metastores from different rolegroups do not offer HA or interact with each other - Implement HA for the metastore (e.g. using
ZooKeeperTokenStore)?
TODO: They all share the same database, Metastore should still be stateless, ZK discovery does exist but not sure what uses that. This is for Jim to research
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 current Hive metastore replica behavior described in issue #154 and the service-discovery context in pull request #145. Research whether the shared database and ZooKeeperTokenStore support real HA, then choose between limiting replicas to one with documentation or implementing HA; done means the selected behavior is implemented and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100