Ok, I figured out what was happening. I was not passing the IP of the
virtual machine which generates the source using MQTT protocol. So, I was
seeing results only if the operator was placed on the machine that was
generating the data (the virtual machine). If the operator was placed on
the other m
I guess there is something to do with the parallelism of the cluster. When
I set "taskmanager.numberOfTaskSlots" to 1 and do not use
"setParallelism()" I can see the logs. And on Eclipse I can see the logs.
Does anybody have a clue?
Thanks
*--*
*-- Felipe Gutierrez*
*-- skype: felipe.o.gutierrez*
no. It did not work.
I also created a Sink that is a MQTT publisher (
https://github.com/felipegutierrez/explore-flink/blob/master/src/main/java/org/sense/flink/mqtt/MqttSensorPublisher.java)
and on my eclipse it works. When I deploy my job on my Flink cluster it
does not work. It might be somethi
This kind of sounds like a Outputstream flushing issue. Try calling
"System.out.flush()" now and then in your sink and report back.
On 04/04/2019 18:04, Felipe Gutierrez wrote:
Hello,
I am studying the parallelism of tasks on DataStream. So, I have
configured Flink to execute on my machine (m
Hello,
I am studying the parallelism of tasks on DataStream. So, I have configured
Flink to execute on my machine (master node) and one virtual machine
(worker node). The master has 4 cores (taskmanager.numberOfTaskSlots: 4)
and the worker only 2 cores (taskmanager.numberOfTaskSlots: 2). I don't