Hi Dominique,
Had another quick look at the error trace you provided, the problem doesn’t
seem to be related to Kerberos authentication.
For some reason the JobManager simply isn’t reachable from the client, as
Robert has pointed out. There should be some clue about this in the JM logs.
On 1 J
Can you check the logs of the JobManager? (maybe in DEBUG level), to see if
you see something that tries to establish a connection with it?
Are you sure you are properly authenticated to access the JM?
On Tue, May 30, 2017 at 4:41 PM, Dominique Rondé <
dominique.ro...@allsecur.de> wrote:
> Hi Gor
Hi Gordon,
we use Flink Flink 1.2.0 bundled with Hadoop 2.6 and Scala 2.11 build on
2017-02-02.
Cheers
Dominique
Am 30.05.2017 um 16:31 schrieb Tzu-Li (Gordon) Tai:
> Hi Dominique,
>
> Could you tell us the version / build commit of Flink that you’re using?
>
> Cheers,
> Gordon
>
>
> On 30 May
Hi Dominique,
Could you tell us the version / build commit of Flink that you’re using?
Cheers,
Gordon
On 30 May 2017 at 4:29:08 PM, Dominique Rondé (dominique.ro...@allsecur.de)
wrote:
Hi folks,
I just become into the need to bring Flink into a yarn system, that is
configured with kerberos.
Hi folks,
I just become into the need to bring Flink into a yarn system, that is
configured with kerberos. According to the documentation, I changed the
flink.conf.yaml like that:
security.kerberos.login.use-ticket-cache: true
security.kerberos.login.contexts: Client
I know that providing a keyt
