flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aljoscha Krettek <aljos...@apache.org>
Subject Re: Partitioner is spending around 2 to 4 minutes while pushing data to next operator
Date Wed, 28 Jun 2017 13:05:02 GMT
I think then there is something going wrong somewhere. Usually people get millisecond latencies
even when they have a “keyBy” or shuffle in-between operations (which are not different
to a custom partitioner at the system level).

What kind of sources/sinks is your program using?

Best,
Aljoscha

> On 27. Jun 2017, at 17:04, sohimankotia <sohimankotia@gmail.com> wrote:
> 
> So In following execution flow :
> 
> source -> map -> partitioner -> flatmap -> sink 
> 
> I am attaching current time to tuple while emitting from map function , and
> then extracting that timestamp value from tuple in flatmap at a very first
> step . Then I am calculating difference between time attached while emitting
> from map and entering into flatmap .
> 
> 
> 
> --
> View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Partitioner-is-spending-around-2-to-4-minutes-while-pushing-data-to-next-operator-tp13913p14025.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.


Mime
View raw message