You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/12/06 16:34:35 UTC

[GitHub] [flink] wsry opened a new pull request #10472: [FLINK-14872][runtime] Temporary fix for potential deadlock problem when tasks read from blocking ResultPartitions.

wsry opened a new pull request #10472: [FLINK-14872][runtime] Temporary fix for potential deadlock problem when tasks read from blocking ResultPartitions.
URL: https://github.com/apache/flink/pull/10472
 
 
   ## What is the purpose of the change
   
   This commit implements a temporary fix for the potential deadlock problem reported in FLINK-14872. The problem itself is not solved completely, however the possibility of deadlock is largely reduced. We leave the proper fix of this problem to the future version. Because the fix does not solve the deadlock problem completely and the fix is trivial, so no new test is attached.
   
   
   ## Brief change log
   
     - Reduce the max size of local buffer pool from ```Integer.MAX_VALUE``` to ```floatingNetworkBuffersPerGate``` for InputGates reading from blocking result partition.
   
   
   ## Verifying this change
   
   Because the fix does not solve the deadlock problem completely and the fix is trivial, so no new test is attached.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not documented)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services