[FLINK-12536] Make BufferOrEventSequence#getNext() non-blocking

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.9.0
• Component/s: Runtime / Network
• Labels: pull-request-available
• Assignee: Congxian Qiu
• Reporter: Piotr Nowojski
• Created: 16/May/19 13:20
• Updated: 01/Jun/20 05:53
• Resolved: 24/Oct/19 07:27

Description

Currently it is non-blocking in case of credit-based flow control (default), however for SpilledBufferOrEventSequence it is blocking on reading from file. We might want to consider reimplementing it to be non blocking with CompletableFuture<?> isAvailable() method.

 

Otherwise we will block mailbox processing for the duration of reading from file - for example we will block processing time timers and potentially in the future network flushes.

 

This is not a high priority change, since it affects non-default configuration option AND at the moment only processing time timers are planned to be moved to the mailbox for 1.9.

Issue Links

• is related to: FLINK-12535 Make CheckpointBarrierHandler non-blocking
• is superceded by: FLINK-14516 Remove non credit based network code
• links to: GitHub Pull Request #8895