-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Streams
-
Release Notes Summary:Fixed scale metrics when there is no processors information.
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform #110
-
Story Points:3
It has been seen that it's possible to have missing `processors` information, in this case the number of threads for a computation is unknown resulting in an infinite number of worker nodes (MAX_INT)
GET /management/stream
... ], "processors": [], // No processors information "metrics": [ { "timestamp": 1710942380, ...
GET /management/stream/scale
{ "scale": { "currentNodes": 1, "bestNodes": 2147483647, // infinity of nodes (MAX_INT) "metric": 2147483646 }, "nodes": [], "computations": [ { "computation": "bulk-XXX", "streams": {...}, "nodes": [ { "nodeId": "worker-1", "threads": null, // we don't know the number of threads because we lost the processor information "timestamp": 1710942565, "count": 26346, ... } ], "current": { "nodes": 1, "threads": 0, "rate1m": 0.00042257344, "eta": 18562454 }, "best": { "nodes": 2147483647, "threads": 1, "rate1m": "Infinity", "eta": 0 } } ] }
- causes
-
NXP-32496 Avoid warning about stream metrics when starting from scratch
- Resolved