Hi Weihua,
Good to hear that you have found the problem. Let us know if you find some
other problems after all.
Piotrek
> On 27 May 2020, at 14:18, Weihua Hu wrote:
>
> Hi Piotrek,
>
> Thanks for your suggestions, I found some network issues which seems to be
> the cause of back pressure.
>
Hi Piotrek,
Thanks for your suggestions, I found some network issues which seems to be the
cause of back pressure.
Best
Weihua Hu
> 2020年5月26日 02:54，Piotr Nowojski 写道：
>
> Hi Weihua,
>
> > After dumping the memory and analyzing it, I found:
> > Sink (121)'s RemoteInputChannel.unannouncedCred
Hi Weihua,
> After dumping the memory and analyzing it, I found:
> Sink (121)'s RemoteInputChannel.unannouncedCredit = 0,
> Map (242)'s CreditBasedSequenceNumberingViewReader.numCreditsAvailable = 0.
> This is not consistent with my understanding of the Flink network
> transmission mechanism.
It
Hi Weihua,
From your below info, it is with the expectation in credit-based flow control.
I guess one of the sink parallelism causes the backpressure, so you will see
that there are no available credits on Sink side and
the outPoolUsage of Map is almost 100%. It really reflects the credit-based
Hi, all
I ran into a weird single Task BackPressure problem.
JobInfo:
DAG: Source (1000)-> Map (2000)-> Sink (1000), which is linked via rescale.
Flink version: 1.9.0
There is no related info in jobmanager/taskamanger log.
Through Metrics, I see that Map (242) 's outPoolUsage is fu
