One source is much slower than the other side when join history data

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

One source is much slower than the other side when join history data

liujiangang
      When consuming history data in join operator with eventTime, reading data from one source is much slower than the other. As a result, the join operator will cache much data from the faster source in order to wait the slower source. 
      The question is that how can I make the difference of consumers' speed small?
Reply | Threaded
Open this post in threaded view
|

Re: One source is much slower than the other side when join history data

Konstantin Knauf-2
Hi,

this topic has been discussed a lot recently in the community as "Event Time Alignment/Synchronization" [1,2]. These discussion should provide a starting point.

Cheers,

Konstantin




On Wed, Feb 27, 2019 at 3:03 AM 刘建刚 <[hidden email]> wrote:
      When consuming history data in join operator with eventTime, reading data from one source is much slower than the other. As a result, the join operator will cache much data from the faster source in order to wait the slower source. 
      The question is that how can I make the difference of consumers' speed small?


--

Konstantin Knauf | Solutions Architect

+49 160 91394525


Follow us @VervericaData

--

Join Flink Forward - The Apache Flink Conference

Stream Processing | Event Driven | Real Time

--

Data Artisans GmbH | Invalidenstrasse 115, 10115 Berlin, Germany

--

Data Artisans GmbH
Registered at Amtsgericht Charlottenburg: HRB 158244 B
Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen   
Reply | Threaded
Open this post in threaded view
|

Re: One source is much slower than the other side when join history data

liujiangang