Re: BlobCache and its functioning

Ok, thank you very much! So that was nothing actually related to what I was trying to do. I guess I'll have to investigate further on the effective correctness of the implementation of the OutputFormat then, because the total lack of other log lines was the most strucking thing about this whole

Re: BlobCache and its functioning

to sum up: the lines you were seeing seem to be the down- and upload of the TaskManager logs from the web interface which go through the BlobServer and its components. Nico On Thursday, 31 August 2017 11:51:27 CEST Federico D'Ambrosio wrote: > Hi, > > 1) I'm using Flink 1.3.2 > > 2) Th

Re: BlobCache and its functioning

Hi, 1) I'm using Flink 1.3.2 2) Th JobManager log is pretty much the same concerning those lines: 2017-08-30 14:16:53,343 INFO org.apache.zookeeper.ClientCnxn - Opening socket connection to server master-1.localdomain/10.0.0.55:2181 2017-08-30 14:16:53,344 INFO

Re: BlobCache and its functioning

Hi Federico, 1) Which version of Flink are you using? 2) Can you also share the JobManager log? 3) Why do you think, Flink is stuck at the BlobCache? Is it really blocked, or do you still have CPU load? Can you post stack traces of the TaskManager (TM) and JobManager processes when you think

Re: BlobCache and its functioning

Hi Federico, Not sure what's going on there but Nico (in CC) is more familiar with the blob cache and might be able to help. Best, Fabian 2017-08-30 15:35 GMT+02:00 Federico D'Ambrosio : > Hi, > > I have a rather simple Flink job which has a KinesisConsumer as a source >

BlobCache and its functioning

Hi, I have a rather simple Flink job which has a KinesisConsumer as a source and an HBase table as sink, in which I write using writeOutputFormat. I'm running it on a local machine with a single taskmanager (2 slots, 2G). The KinesisConsumer works fine and the connection to the HBase table gets