Hi Aitozi,
the difference is the scope: the normal metrics (without
taskmanager.net.detailed-metrics) reflect _all_ buffers of a task while the
detailed statistics are more fine-grained and give you statistics per input (or
output) gate - the "total" there reflects the fact that each gate has mu
hi,
i have understood it.
thanks,
aitozi
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
The metrics registered in initializeBufferMetrics aggregate across all
InputGates, whereas the metrics registered in the InputGateMetrics are
separate for each InputGate.
As an example, let's say a task has 2 input gates, with each having 2
input buffers queued:
// IOMetricGroup#initializeBu
Hi Aitozi,
I will loop in people that are more familar with the network stack and
metrics. Maybe this is a bug?
Regards,
Timo
Am 10/22/17 um 4:36 PM schrieb aitozi:
Hi,
i see in version 1.3, it add the ResultPartitionMetrics with
issue:https://issues.apache.org/jira/browse/FLINK-5090
but
