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/07/23 15:56:53 UTC

[GitHub] [flink] tweise commented on issue #9183: [FLINK-12768][tests] FlinkKinesisConsumerTest.testSourceSynchronization flakiness

tweise commented on issue #9183: [FLINK-12768][tests] FlinkKinesisConsumerTest.testSourceSynchronization flakiness
URL: https://github.com/apache/flink/pull/9183#issuecomment-514272711
 
 
   The records and watermarks are emitted from separate threads (the thread that emits the records will indicate what the next candidate watermark is). The logic in this test relies on the watermark for the last record being emitted when advancing the processing time. Therefore it is important that  record emit and watermark state change occur atomically. Otherwise the context switch can occur after the record emit and the watermark is generated using previous state, which lead to the flakiness. All this only matters for this test. In a job watermarks are emitted periodically and it only matters that the record is emitted prior to the corresponding watermark state change.
   

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