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/05/17 03:31:50 UTC

[GitHub] [flink] sunhaibotb opened a new pull request #8471: [FLINK-12529][runtime] Release record-deserializer buffers timely to improve the efficiency of heap usage on taskmanager

sunhaibotb opened a new pull request #8471: [FLINK-12529][runtime] Release record-deserializer buffers timely to improve the efficiency of heap usage on taskmanager
URL: https://github.com/apache/flink/pull/8471
 
 
   ## What is the purpose of the change
   
   This pull request releases the buffer of  the corresponding record deserializer after receiving `EndOfPartitionEvent` from the input channel  to improve the efficiency of heap memory usage on taskmanager.
   
   
   ## Brief change log
   
     - Change `StreamInputProcessor` to release the buffer of the corresponding record deserializer immediately after receiving `EndOfPartitionEvent` from the input channel
     - Change `StreamTwoInputProcessor` to release the buffer of the corresponding record deserializer immediately after receiving `EndOfPartitionEvent` from the input channel
   
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as `OneInputStreamTaskTest`, `TwoInputStreamTaskTest`.
   
   
   ## 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