akashk99 opened a new issue, #31085:
URL: https://github.com/apache/beam/issues/31085

   ### What happened?
   
   When there are idle subtasks in flink, they dont propagate watermarks to 
downstream operators and thus windowing function that are based on watermarks  
never get triggered. I can see that when setting parallelism exactly equal to 
the number of kinesis shards, the problem doesnt exists, however, if this 
number is different, then I see the flink UI showing no watermarks and my 
windows never get triggered. 
   
   I also have custom DoFns that output with timestamp before so in theory, 
that should be used as the watermark for windowing, however, this is not the 
case. 
   
   When using native flink, I have seen solutions such as using methods like 
"withIdlenss", but these dont exist in beam. Is there something I am missing in 
my kinesis config or is this a known issue with the read transform,
   
   
   This only occurs on the flink runner and not the direct or dataflow runner. 
Its also possible this isnt an issue with the kinesis io reader, but maybe the 
windowing function should ignore watermarks from idle upstream tasks.
   
   ### Issue Priority
   
   Priority: 2 (default / most bugs should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [X] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam YAML
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Spark Runner
   - [X] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to