kubernetes
8 minKubernetes finalizers: deletion is a protocol, not a cleanup callback
Follow deletion timestamps and controller-owned finalizer removal without hiding leaked resources.
Search the library
4 matching resultsArticles and interview answers
Q&A
Q&AWhy can a Kubernetes object remain after deletion was requested?
A controller has not removed its finalizer after completing external cleanup.
Read the concise answer
The API server records deletion and retains the object while finalizers remain. The owning controller must retry idempotent cleanup and remove only its own finalizer after confirmed completion.
databases
5 minSQL Event Gaps: LAG, Stable Ordering, and Explicit Window Frames
Investigate missing heartbeats with PostgreSQL interval arithmetic and a separate SQLite integer-millisecond contract.
Q&A
Q&AWhat does it mean when a Java object becomes eligible for garbage collection?
It is no longer strongly reachable from GC roots, though collection timing is not guaranteed.
Read the concise answer
An object becomes eligible when no strong-reference path leads to it from roots such as live thread stacks, static fields, or JNI references. Eligibility does not guarantee immediate collection or finalization. To diagnose retention, inspect heap dumps and dominator paths; do not rely on System.gc() as a fix.