apache / dolphinscheduler

Apache DolphinScheduler is the modern data orchestration platform. Agile to create high performance workflow with low-code
https://dolphinscheduler.apache.org/
Apache License 2.0
12.62k stars 4.56k forks source link

Kerberos expired #4430

Closed zongqiren closed 1 month ago

zongqiren commented 3 years ago

The team uses the dolphinscheduler to schedule the spark2 task. Because the Kerberos environment is enabled in the cluster environment, the spark task cannot be executed after a period of time. It is found in the worker log that the authentication has expired. If you try to restart the dolphinscheduler, you can resume normal execution. It is not a solution to restart all the time. Do you want to know what can be solved?

zongqiren commented 3 years ago

I've revised it common.properties , put kerberos.expire.time Parameter modification, restart, can unlimited modification is very big, because to find a way to solve the problem of expiration, always can't old restart to solve

zhuangchong commented 3 years ago

Set up a timed task to refresh the keytab. You can also try this method.

zongqiren commented 3 years ago

Do you want to refresh the KeyTab of DS authentication or the KeyTab of the user executing the program on DS regularly? Do you have any examples? If you are not familiar with this part, please write a method to refresh the KeyTab. Thank you

zhuangchong commented 3 years ago

Dolphin sets up a timed task that uses the shell task node to call the script kinit-kt/XXX /xxx.keytab xxx@xxx.xxx.com to swipe the keytab of a specific user

shiliquan commented 3 years ago

@zongqiren
I suggest you upgrade to version 1.3.4. I've had the same problem as you before, upgrade to 1.3.4 and modify krb 5. After a week of testing, nothing like this has happened. image

JinLin6564 commented 3 years ago

@zongqiren 我建议您升级到1.3.4版。我遇到了与您之前相同的问题,升级到1.3.4并修改krb5。经过一周的测试,没有发生任何类似的事情。 图像

I have the same problem. Excuse me, have you solved it? How to solve the problem

shiliquan commented 3 years ago

好像解决了!

shiliquan commented 3 years ago

你把common.properties里的kerberos.expire.time这个参数改一下试试。 image

JinLin6564 commented 3 years ago

你把common.properties里的kerberos.expire.time这个参数改一下试试。 image

好,我等今晚过期后修改一下,然后重启worker。目前配置的是24

zongqiren commented 3 years ago

emmm,我测试过,没有用 ------------------ 原始邮件 ------------------ 发件人: "apache/incubator-dolphinscheduler" <notifications@github.com>; 发送时间: 2021年3月1日(星期一) 下午5:22 收件人: "apache/incubator-dolphinscheduler"<incubator-dolphinscheduler@noreply.github.com>; 抄送: "470096567"<470096567@qq.com>;"Mention"<mention@noreply.github.com>; 主题: Re: [apache/incubator-dolphinscheduler] Kerberos expired (#4430)

你把common.properties里的kerberos.expire.time这个参数改一下试试。

好,我等今晚过期后修改一下,然后重启worker。目前配置的是24

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

JinLin6564 commented 3 years ago

emmm,我测试过,没有用 ------------------ 原始邮件 ------------------ 发件人: "apache/incubator-dolphinscheduler" <notifications@github.com>; 发送时间: 2021年3月1日(星期一) 下午5:22 收件人: "apache/incubator-dolphinscheduler"<incubator-dolphinscheduler@noreply.github.com>; 抄送: "470096567"<470096567@qq.com>;"Mention"<mention@noreply.github.com>; 主题: Re: [apache/incubator-dolphinscheduler] Kerberos expired (#4430) 你把common.properties里的kerberos.expire.time这个参数改一下试试。 好,我等今晚过期后修改一下,然后重启worker。目前配置的是24 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

你现在情况怎么样。解决了么?

shiliquan commented 3 years ago

那不知道啊,反正我是可以了!

JinLin6564 commented 3 years ago

魔幻的问题啊啊啊啊

shiliquan commented 3 years ago

一、我用的是1.3.4版本 二、我的krb5认证文件如下:(这个文件建议把本机认证的krb5文件统一,所有work都要改) image 三、修改了kerberos.expire.time=1(如果不行,这个参数建议你可以修改小一点,可以用0.2、0.5.....试一下) 然后install重装了一下。 其他的我也没改啥了。 希望可以帮到你。

shiliquan commented 3 years ago

@JinLin6564 问题解决了么?

JinLin6564 commented 3 years ago

@ JinLin6564问题解决了么?

没有。哎。。

github-actions[bot] commented 1 month ago

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] commented 1 month ago

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.