HDFS controller doesn't watch Listeners

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
kubernetes, rust
Domain
infrastructure

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.

Description

type/bug

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...

Dominant language
Rust
Stars
53
Forks
9
Avg merge
1d 13h
Merged PRs (30d)
10

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/hdfs-operator

All issues in stackabletech/hdfs-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.