epam / epam/cloud-pipeline

Inconsistent node memory usage metrics

Open
#4,367 0 comments 0 reactions 0 assignees View on GitHub
kind/bug
Dominant language
Java
Stars
163
Forks
65
Avg merge
11h 46m
Merged PRs (30d)
29

Description

**Describe the bug**
Inconsistency has been observed between memory statistics reported by `/cluster/node/{name}/usage` for an instance node and the memory usage reported by `/cluster/node/{name}/usage?runId={runId}` for a run on the same node. In some cases, the values differ significantly, with the run memory usage reported as several times higher than the node level memory.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the responses from /cluster/node/{name}/usage and /cluster/node/{name}/usage?runId={runId} for the same instance node, using a case where the values differ significantly. Trace how node-level and run-level memory usage are calculated, then verify that both endpoints report consistent memory values for the same node.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.