One of the key challenges is isolation, eg. ensuring that one job cannot
access the credentials of another. The easiest solution today is to use
the YARN deployment mode, with a separate app per job. Meanwhile,
improvements being made under the FLIP-6 banner for 1.4+ are lying
groundwork for a mu
Thanks for the overview.
Currently a single flink cluster seems to run all tasks with the same user.
I would want to be able to run each flink job as a separate user instead.
The update for separate read/write users is nice though.
Tzu-Li (Gordon) Tai schrieb am Mi. 2. Aug. 2017 um
10:59:
> Hi,
Hi,
There’s been quite a few requests on this recently on the mailing lists and
also mentioned by some users offline, so I think we may need to start with
plans to probably support this.
I’m CC’ing Eron to this thread to see if he has any thoughts on this, as he was
among the first authors driv
Hi,
flink currently only seems to support a single kerberos ticket for
deployment. Are there plans to support different users per each job?
regards,
Georg
