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.
Thisobservation does not match the description of the inputQueueSize.
Therefore, does this
Regarding the inputQueueSize metric. What does it express after all?
Observing the inputQueueSize and inPoolUsage metrics in Prometheus, Ifound
that when the inPoolUsage is high, the inputQueueSize is low. Thisobservation
does not match the description of the inputQueueSize.Therefore, does
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
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
> Hello,
> >
> > I am trying to determine the buffered records in the input buffers of a
> > task. I found the inputQueueSize metric. According to the docs it
is "The
> > real size of queued input buffers in bytes". The docs also state
that "The
&g
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 inp
Hello,
I am trying to determine the buffered records in the input buffers of a task. I
found the inputQueueSize metric. According to the docs it is "The real size of
queued input buffers in bytes". The docs also state that "The size for local
input channels is always 0 since th
