Hi Oliver, which Flink image are you using? If you are using the docker image from docker hub [1], then the memory logging will go to stdout and not to a log file. The reason for this behavior is that the docker image configures the logger to print to stdout such that one can easily access the logs via `docker logs`. If this is the case, then you should find the memory logging statements somewhere in the console output.
[1] https://hub.docker.com/r/_/flink/ Cheers, Till On Tue, Jul 24, 2018 at 1:43 PM Oliver Breit <oliver.br...@relayr.io> wrote: > Hi everyone, > > We are using a simple Flink setup with one jobmanager and one taskmanager > running inside a docker container. We are having issues enabling the > *taskmanager.debug.memory.startLogThread > *setting. We added > *taskmanager.debug.memory.startLogThread: true* > *taskmanager.debug.memory.logIntervalMs: 1000* > to our flink conf (/opt/flink/conf/flink-conf.yaml). > > The console prints > *2018-07-24 09:53:42,497 INFO > org.apache.flink.configuration.GlobalConfiguration - Loading > configuration property: taskmanager.debug.memory.startLogThread, true* > (similarly for logIntervalMs). So it seems that those values are being > read. > > In the log folder, there is only a flink--client-bc7592c47b7b.log file > with no relevant information. We don't see any task- or jobmanager logs. > We've tried adding the env.log.dir and taskmanager.log.path directly to > flink-conf.yaml. We've also added custom log4j.properties to > /opt/flink/conf/ without any apparent success. > > Is there something obvious that I am missing? > > Let me know if you need more information. > > Thanks! > > Best, > Oliver > > >
