flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [flink] zhijiangW opened a new pull request #8557: [FLINK-12544][network] Fix the deadlock while releasing memory triggered by multiple threads in SpillableSubpartition
Date Tue, 28 May 2019 10:50:23 GMT
zhijiangW opened a new pull request #8557: [FLINK-12544][network] Fix the deadlock while releasing
memory triggered by multiple threads in SpillableSubpartition
URL: https://github.com/apache/flink/pull/8557
 
 
   ## What is the purpose of the change
   
   *Fix the deadlock while releasing memory triggered by multiple threads in `SpillableSubpartition`.*
   
   ## Brief change log
   
     - *Make the call of `releaseMemory(1)` outside `synchronized` in `LocalBufferPool#requestMemorySegment`*
     - *Refactor the `NoOpTaskActions` as a separate class for using in other tests*
   
   ## Verifying this change
   
   This change is covered by new test `SpillableSubpartitionTest#testConcurrentRequestAndReleaseMemory`*.
   
   ## 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

Mime
View raw message