-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] [Setting Center] dinky was down when set Resource mode to oss #4173
Comments
Please have a try in Dinky1.2.1 |
i am using 1.2.1,sorry i close it ,how to reopen it |
当在不知情的时候按了oss,会导致整个部署的dinky直接挂彩,并且启动不起来,我认为需要一个保护措施 |
I agree with you. |
otherwise, the name "oss" should change to "s3" better |
这个问题是由于你开启了HistoryServer,它会加载Resource的配置。当Resource中的配置不正确时,HistoryServer抛oss相关的异常会把dinky也停止。 可以考虑暂时关闭HistoryServer,等以后版本修复这个问题 This issue occurs because you have enabled the HistoryServer, which loads the configuration of the Resource. When the configuration in the Resource is incorrect, the HistoryServer throws an exception related to OSS, which also stops Dinky. Additionally, OSS depends on the AWS SDK, while HistoryServer depends on flink-s3-presto, and these two handle the leading "/" in the path differently. |
Search before asking
What happened
What you expected to happen
will not down when set to oss
How to reproduce
only to change it on web
Anything else
No response
Version
1.2.0
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: