Listeners do not re-attach post deletion without podrestart
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- kubernetes, python
- Domain
- backend, networking
Research direction
Start by tracing how listener UIDs are assigned and how pod labels are matched to recreated listener services; the issue does not name specific files or tests. Reproduce the deletion and recreation scenario with a HiveCluster and a ClusterInternal listener, then check that the recreated service can reach the original ready pods without a pod restart.
Written by the indexing model from the issue text.
Description
Affected Stackable version
all
Current and expected behavior
Current behaviour
Assume a HiveCluster using a listener class e.g. ClusterInternal. A HiveCluster get's created with a listener discovered by label and IP provisioned by a volumeMount at the STS level.
If a Listener service gets deleted e.g. by hand or by e.g. only updating listener-operator, a new listener service gets created, the products operator does not reconcile and thus although pods are ready it fails to be reached via the fresh listener service.
Cause
Whenever a listener is recreated, it comes with a new UID. Pod's are labeled with something like listener.stackable.tech/mnt.<uid> referencing the listener UID created for this pod. Those UIDs change when a listener restarts and the pod don't. This mismatch will cause the pod being unavailable through it's listener address while becoming healthy and available
Expected behaviour
Listeners should reattach to its original pod after restart.
Possible solution
Probably something like a label which doesn't contain the UID.
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
- Dominant language
- Python
- Stars
- 9
- Forks
- 3
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from stackabletech/listener-operator
-
ListenerClass CRD restructureMay be free again @NickLarsenNZ claimed this 450 days ago, and no pull request is open. Open
stackabletech/listener-operator#330 · 5 comments · 1 reaction · 1 assignee ·
-
OpenShift Route backendMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
customer-request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/listener-operator#302 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
-
Rename `listeners.stackable.tech/listener-class` PVC annotation to `listeners.stackable.tech/class`Open
Difficulty 3/5 1-2 days Newbie friendliness 43/100
stackabletech/listener-operator#271 · 1 comment ·
All issues in stackabletech/listener-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
deepchem/deepchem#5289 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
UKGovernmentBEIS/inspect_evals#2892 · 1 comment ·
Maintainers usually reply within 1 day
-
Versioning docs: say that no output from the 0.46 warning check means nothing is affectedPossibly taken @grelinfo claimed this today. Opendocumentation priority:low size:S
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
alphacrack/readme2demo#293 ·