I finally sorted my problem out. Using the CLI instead of the Web UI for
debugging with simple System.out.println() statements. I noticed that a
local installation launched with start-cluster.sh worked A-OK.
In order to reproduce a simple learning environment with docker images,
I ended up
Just to recap
I use Flink 1.4.2 with Docker compose which launches a jobmanager and a
taskmanager.
My hope is to learn another library which can be used with Flink, so
logging is important to me.
I start the cluster and deploy the following task (I dropped all calls
to that library so I can focus
Nico, all,
I am still stuck with this. Upgraded the docker image to 1.4.2 and the
AMIDST library to 0.7.0
Just noticed this issue which signals logging issues outside transforms:
https://issues.apache.org/jira/browse/FLINK-7990
Could this be related? Although I don't see the relation to
in the docker-compose.yaml I have a volume entry which maps my
log4j.properties with /opt/flink/conf/log4j-console.properties
Not pretty but it works after I determined how it was being launched.
See below
version: "2.1"
services:
jobmanager:
image: flink
expose:
- "6123"
I'm a bit curious on how you hand your log4j into the docker image for
consumption. On SO you are referring to bin/flink-console.sh but
executing Flink in docker is a bit different.
Maybe I'm wrong, but looking at the sources of the docker image [1], it
will not forward any additional parameters
Just a guess, but probably our logging initialisation changes the global
log level (see conf/log4j.properties). DataStream.collect() executes the
program along with creating a local Flink "cluster" (if you are testing
locally / in an IDE) and initializing logging, among other things.
Please
Hello,
I am learning Flink and using the docker image along with the AMIDST
library for this.
Below is a sample task from AMIDST which provides INFO output up until I
reach updateModel(). I pasted the short method as well and wonder what
prevents the Logger from
//Set-up Flink
