Details
-
Improvement
-
Status: Open
-
P3
-
Resolution: Unresolved
-
None
-
None
Description
This is especially important for Fn API reads, where each element represents a shard to read and may be very expensive, but many elements may be waiting in the Fn API buffer.
The need for this will be mitigated with full SDF support for liquid sharding over the Fn API, but not eliminated unless the runner can "unread" elements it has already sent.
This is especially important in for dataflow jobs that start out small but then detect that they need more workers (e.g. due to the initial inputs being an SDF).
Attachments
Issue Links
- causes
-
BEAM-8998 Avoid excessive bundle progress polling in Dataflow Runner
- Resolved
- links to