-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Streams
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform #107, nxplatform #108
-
Story Points:2
The aggregated best number of nodes and the scale metric are wrong when the current nodes is already optimal and there is only one active computation.
In the following output we should have bestNodes: 4 and metric: 0
"scale": { "currentNodes": 4, "bestNodes": 1, "metric": -3 }, ... "current": { "nodes": 4, "threads": 8, "rate1m": 0.28108606, "eta": 536728 }, "best": { "nodes": 4, "threads": 8, "rate1m": 0.28108606, "eta": 536728 } } ]