Re: Understanding watermark

2020-01-19 Thread Guowei Ma
>>What I understand from you, one operator has two watermarks? If so, one operator's output watermark would be an input watermark of the next operator? Does it sounds redundant? There are no two watermarks for an operator. What I want to say is "watermark metrics". >>Or do you mean the Web UI

Re: Understanding watermark

2020-01-14 Thread Cam Mach
Hi Guowei, Thanks for your response. What I understand from you, one operator has two watermarks? If so, one operator's output watermark would be an input watermark of the next operator? Does it sounds redundant? Or do you mean the Web UI only show the input watermarks of every operator, but

Re: Understanding watermark

2020-01-14 Thread Guowei Ma
Hi, Cam, I think you might want to know why the web page does not show the watermark of the source. Currently, the web only shows the "input" watermark. The source only outputs the watermark so the web shows you that there is "No Watermark". Actually Flink has "output" watermark metrics. I think

Re: Understanding watermark

2020-01-14 Thread Cam Mach
Hi Till, Thanks for your response. Our sources are S3 and Kinesis. We have run several tests, and we are able to take savepoint/checkpoint, but only when S3 complete reading. And at that point, our pipeline has watermarks for other operators, but not the source operator. We are not running

Re: Understanding watermark

2020-01-14 Thread Till Rohrmann
Hi Cam, could you share a bit more details about your job (e.g. which sources are you using, what are your settings, etc.). Ideally you can provide a minimal example in order to better understand the program. >From a high level perspective, there might be different problems: First of all, Flink

Understanding watermark

2020-01-13 Thread Cam Mach
Hello Flink expert, We have a pipeline that read both bounded and unbounded sources and our understanding is that when the bounded sources complete they should get a watermark of +inf and then we should be able to take a savepoint and safely restart the pipeline. However, we have source that