Great to hear that you solved the problem!
Cheers,
Till
On Fri, Nov 13, 2020 at 4:56 PM Marco Villalobos
wrote:
> Hi Till,
>
> Thank you for following up.
>
> We were trying to set up s3 file sinks, and rocksdb with s3 checkpointing.
> We upgraded to Flink 1.11 and attempt to run the job in EMR
Hi Till,
Thank you for following up.
We were trying to set up s3 file sinks, and rocksdb with s3 checkpointing. We
upgraded to Flink 1.11 and attempt to run the job in EMR.
On startup, the logs showed an error that the flink-conf.yaml could not be
found. I tried to trouble shoot the command l
Hi Marco,
as Klou said, -m yarn-cluster should try to deploy a Yarn per job cluster
on your Yarn cluster. Could you maybe share a bit more details about what
is going wrong? E.g. the cli logs could be helpful to pinpoint the problem.
I've tested that both `bin/flink run -m yarn-cluster
examples/s
Hi Marco,
I agree with you that the -m help message is misleading but I do not
think it has changed between releases.
You can specify the address of the jobmanager or, for example, you can
put "-m yarn-cluster" and depending on your environment setup Flink
will pick up a session cluster or will cr
The flink CLI documentation says that the -m option is to specify the job
manager.
but the examples are passing in an execution target. I am quite confused by
this.
./bin/flink run -m yarn-cluster \
./examples/batch/WordCount.jar \
--input hdfs:///
