The standalone-job process fails because no task executors are around to
request slots from.
It _should_ wait for a bit to give task executors time to start up,
controlled via resourcemanager.standalone.start-up-time or, if unset,
slot.request.timeout.
Does the standalone-job process fail immed
You mean taskmanager? I tried using this command:
docker run --env FLINK_PROPERTIES="${FLINK_PROPERTIES}" flink_pipeline
taskmanager
after running above script but got:
2021-01-15 13:03:05,069 INFO
org.apache.flink.runtime.util.LeaderRetrievalUtils [] - Trying
to select the network in
Where are you starting the task executor?
On 1/15/2021 11:57 AM, Manas Kale wrote:
Hi all,
I've got a job that I am trying to run using docker as per [1].
Here's the dockerfile:
# Start from base Flink image. FROM flink:1.11.0 # Add fat JAR and logger
properties file to image. ADD
./target/fli
Hi all,
I've got a job that I am trying to run using docker as per [1].
Here's the dockerfile:
# Start from base Flink image.
FROM flink:1.11.0
# Add fat JAR and logger properties file to image.
ADD ./target/flink_POC-0.1.jar /opt/flink/usrlib/flink_POC-0.1.jar
ADD ./target/classes/log4j.properti