morhidi opened a new pull request, #612:
URL: https://github.com/apache/flink-kubernetes-operator/pull/612
## What is the purpose of the change
LOAD_MAX can be used to identify the busiest vertices in a job graph, hence
it's useful to have it as a metric.
## Brief change log
- Store `LOAD_MAX` as evaluated scaling metrics which is reported by
default
- This change is already covered by existing tests, some extra test data
and assertions where added
## Verified by
- This change is already covered by existing tests, some extra sample data
and assertions where added
- Manually by looking at the reported metrics:
```
AutoScaler.jobVertexID.90bea66de1c231edf33913ecd54406c1.LOAD_MAX.Current:
0.834
AutoScaler.jobVertexID.cbc357ccb763df2852fee8c4fc7d55f2.LOAD_MAX.Current:
0.683
AutoScaler.jobVertexID.90bea66de1c231edf33913ecd54406c1.LOAD_MAX.Average:
0.837
AutoScaler.jobVertexID.cbc357ccb763df2852fee8c4fc7d55f2.LOAD_MAX.Average:
0.678
AutoScaler.jobVertexID.90bea66de1c231edf33913ecd54406c1.LOAD_MAX.Current:
0.834
AutoScaler.jobVertexID.cbc357ccb763df2852fee8c4fc7d55f2.LOAD_MAX.Current:
0.683
```
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (no)
- The public API, i.e., is any changes to the `CustomResourceDescriptors`:
(no)
- Core observer or reconciler logic that is regularly executed: (no)
## Documentation
- Does this pull request introduce a new feature? (no)
- If yes, how is the feature documented? (not applicable / docs / JavaDocs
/ not documented)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
