stackabletech / stackabletech/hdfs-operator
HDFS controller doesn't watch Listeners
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 53
- Forks
- 9
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 10
Description
Controllers should watch for every object that they read, otherwise it's easy to end up "stuck" with stale data.
In this case, NameNode listeners are used to feed the discovery configmap, so we should reconcile whenever they change.
The issue is somewhat mitigated by that pod startup is inhibited by listener-operator until an address has been acquired (which we do watch, via the StatefulSets), but it's still a good to paint both sides of the fence...
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 at the HDFS controller and its NameNode listener handling; trace how the discovery ConfigMap is fed and how StatefulSets are currently watched. Confirm that listener changes trigger reconciliation and refresh the discovery ConfigMap, covering the stated stale-data case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100