HIVE-30033: Hive K8s operator: log replica changes - #6773
Open
abstractdog wants to merge 1 commit into
Open
Conversation
abstractdog
force-pushed
the
HIVE-30033
branch
from
September 10, 2026 09:42
5959b04 to
28daa2a
Compare
asf-ci-hive
added
tests failed
tests pending
and removed
tests pending
tests failed
labels
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Log an INFO line in the reconciler whenever a HiveCluster component is created or scaled to a different replica count. Covers LLAP, TezAM, HiveServer2 and Metastore.
Why are the changes needed?
Scales driven by an SSA on the CR (helm upgrade,
kubectl edit, a tool changing.spec.*.replicas) reached the workload silently — only the autoscaler path logged. On a scale that didn't converge you couldn't tell from the operator log whether the reconciler had seen the change at all.Does this PR introduce any user-facing change?
Operator log only. Example:
INFO HiveDependentResource: Scaling hiveserver2 lbodor-perf/hive-hiveserver2: 2 -> 1 replicas
INFO HiveDependentResource: Scaling metastore lbodor-perf/hive-metastore: 2 -> 1 replicas
INFO HiveClusterReconciler: Scaling llap lbodor-perf/hive-llap0: 12 -> 15 replicas
Silence still means "no change" — the log fires only on a real delta.
How was this patch tested?
Manually on an EKS cluster: scaled HS2, Metastore and LLAP up and down; confirmed the "Scaling …: A -> B replicas" line on each real change and no line when the count already matched.