[
https://issues.apache.org/jira/browse/FLINK-19964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17227153#comment-17227153
]
Zhu Zhu commented on FLINK-19964:
---------------------------------
We recently noticed the issue FLINK-19994 that pipelined region scheduling will
eagerly schedule all the vertices in a DataSet iteration job.
[~roman_khachatryan] Is it possible that the problem is caused by downstream
task allocated all available network buffers from global pool, and then the
upstream task cannot obtain any buffer and get stuck? If so, I think
FLINK-19994 can fix this problem.
However, I cannot reproduce the problem after 1700+ runs locally. So I'm not
sure whether my guess is correct.
> Gelly ITCase stuck on Azure in HITSITCase.testPrintWithRMatGraph
> ----------------------------------------------------------------
>
> Key: FLINK-19964
> URL: https://issues.apache.org/jira/browse/FLINK-19964
> Project: Flink
> Issue Type: Bug
> Components: Library / Graph Processing (Gelly), Runtime / Network,
> Tests
> Affects Versions: 1.12.0
> Reporter: Chesnay Schepler
> Assignee: Roman Khachatryan
> Priority: Blocker
> Labels: test-stability
> Fix For: 1.12.0
>
>
> The HITSITCase has gotten stuck on Azure. Chances are that something in the
> scheduling or network has broken it.
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=8919&view=logs&j=c5f0071e-1851-543e-9a45-9ac140befc32&t=1fb1a56f-e8b5-5a82-00a0-a2db7757b4f5
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
