Thank you for your previous response Feng. It clears things up a little.
Regarding the inputQueueSize metric. What does it express after all?
Observing the inputQueueSize and inPoolUsage metrics in Prometheus, I
found that when the inPoolUsage is high, the inputQueueSize is low. This
observati
Hi Dimitris
Yes, the inputQueueLength metric can only represent the number of buffers,
and cannot obtain the actual size of the messages.
Regarding the inputQueueSize metric, it ignores the LocalChannel.
Therefore, when tasks are connected through the Forward partition strategy,
it will consisten
As per the docs, the `inputQueueLength` metric refers to the number of
queued input buffers, and cannot be used on its own in order to
determine buffered records.
For instance, if I know that there are 5 queued input buffers, I cannot
conclude anything regarding buffered records if the size of
Hi Dimitris
Maybe you can use the `inputQueueLength` metric.
Best,
Feng
On Tue, Nov 28, 2023 at 12:07 AM Dimitris Mpanelas via user <
user@flink.apache.org> wrote:
> Hello,
>
> I am trying to determine the buffered records in the input buffers of a
> task. I found the inputQueueSize metric. Ac
