Open asicoe opened 6 years ago
So a workaround is to set the Java property:
mesos.resourcemanager.tasks.bootstrap-cmd=FLINK_HOME=/mnt/mesos/sandbox/flink
I suspect that the root cause is that the docker image has set a working directory, but Flink assumes that it is being launched from the sandbox directory. Usually that assumption is correct.
The reason why FLINK_HOME
is set to flink
is because the entire flink distribution is automatically copied into the sandbox directory; note the log files related to "fetching" above.
I would characterize this issue as a feature request to support an arbitrary working directory.
I'm guessing that there should be a feature request on the flink project and not this one correct?
Using DCOS 1.10 and dcos-flink-service 1.3.1-1.2.1
Setting either: -Dmesos.resourcemanager.tasks.container.type=docker -Dmesos.resourcemanager.tasks.container.image.name=custom_image:tag or -Dmesos.resourcemanager.tasks.container.type=mesos -Dmesos.resourcemanager.tasks.container.image.name=custom_image:tag
Job Manager std out:
Task manager std out:
The above is the same as this closed issue
/bin/sh: 1: flink/bin/mesos-taskmanager.sh: not found
I am reopening it here to see if there is any workaround.
The command actually ran is $FLINK_HOME/bin/mesos-taskmanager.sh and it seems $FLINK_HOME is set to "flink". So the intention seems for this to be a relative path to some working directory that is not correctly set.