-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fix] Split cpuUsage into systemCpuUsage and jvmCpuUsage #15803
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #15803 +/- ##
============================================
- Coverage 39.20% 39.17% -0.04%
+ Complexity 4909 4888 -21
============================================
Files 1326 1323 -3
Lines 45217 45184 -33
Branches 4818 4810 -8
============================================
- Hits 17729 17702 -27
+ Misses 25617 25603 -14
- Partials 1871 1879 +8 ☔ View full report in Codecov by Sentry. |
09951e1
to
9406a6b
Compare
...inscheduler-common/src/main/java/org/apache/dolphinscheduler/common/model/BaseHeartBeat.java
Fixed
Show fixed
Hide fixed
...inscheduler-common/src/main/java/org/apache/dolphinscheduler/common/model/BaseHeartBeat.java
Fixed
Show fixed
Hide fixed
protected double jvmMemoryUsage; | ||
protected double memoryUsage; | ||
protected double diskUsage; | ||
protected ServerStatus serverStatus; |
Check notice
Code scanning / CodeQL
Missing Override annotation Note
HeartBeat.getServerStatus
...scheduler-common/src/main/java/org/apache/dolphinscheduler/common/model/MasterHeartBeat.java
Fixed
Show fixed
Hide fixed
...scheduler-common/src/main/java/org/apache/dolphinscheduler/common/model/WorkerHeartBeat.java
Fixed
Show fixed
Hide fixed
506c918
to
b952ea4
Compare
fb2d3ac
to
8e8ed13
Compare
8e8ed13
to
22bd4c1
Compare
systemMetrics.getJvmCpuUsagePercentage(), maxJvmCpuUsagePercentageThresholds); | ||
return true; | ||
} | ||
if (systemMetrics.getJvmMemoryUsedPercentage() > maxJvmMemoryUsagePercentageThresholds) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if judging a jvm's memory usage is necessary. I think the heap memory of JVM will always increase over time. After reaching certain conditions, minor/major GC will be triggered and the memory usage will decrease.
Therefore, I think that the temporary increase in jvm memory utilization is not abnormal. But due to memory leaks and other reasons, it is indeed an anomaly that the JVM's memory utilization remains high for a long time.
Others LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, I have removed this setting, PTAL
22bd4c1
to
34a56cd
Compare
34a56cd
to
705b1fa
Compare
Quality Gate failedFailed conditions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Purpose of the pull request
fix #15579
Brief change log
Split
maxCpuUsagePercentageThresholds
intomaxSystemCpuUsagePercentageThresholds
andmaxJvmCpuUsagePercentageThresholds
, to avoid judging overload by CPU might confusion.Verify this pull request
This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(or)
If your pull request contain incompatible change, you should also add it to
docs/docs/en/guide/upgrede/incompatible.md