Re: Containers are not released after job failed

Thank you, it is fixed in the new version. -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/

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

Thank you very much. -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/

Re: IntervalJoin is stucked in rocksdb'seek for too long time in flink-1.6.2

Yes, you are right. I add log to record the time of seek and find that sometimes it is very slow. Then I use the rocksdb's files to test locally and the same problem appears. It is very weird to find that rocksdb's seek iterate data one by one. Until now, I add cache for rocksdb. The time is faster

Re: IntervalJoin is stucked in rocksdb'seek for too long time in flink-1.6.2

This is not my case. Thank you. -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/

Re: IntervalJoin is stucked in rocksdb'seek for too long time in flink-1.6.2

Thank you very much. I have something to say. Each data is 20KB. The parallelism is 500 and each taskmanager memory is 10G. The memory is enough, and I think the parallelism is big enough. Only the intervalJoin thread is beyond 100% because of rockdb's seek. I am confused that why rockdb's seek tak

IntervalJoin is stucked in rocksdb'seek for too long time in flink-1.6.2

I am using IntervalJoin function to join two streams within 10 minutes. As below: labelStream.intervalJoin(adLogStream) .between(Time.milliseconds(0), Time.milliseconds(60)) .process(new processFunction()) .sink(kafkaProducer) labelStream and adLogStream are pr