github-actions[bot]
commented
1 year ago Search before asking
- [X] I had searched in the issues and found no similar issues.
What happened
After installing flink, although some key configurations of flink are reflected on the interface, they are still empty in the configuration file flink-conf.yaml
- datasophon-manager : datasophon-manager-1.1.1
- DDP : 1.1.1
For example, the default configuration automatically generated in the graphical interface is as follows
high-availability: zookeeper
high-availability.storageDir: hdfs://nameservice1/flink/ha/
high-availability.zookeeper.quorum: ds-1:2181,ds-2:2181,ds-3:2181
high-availability.zookeeper.path.root: /flink
high-availability.zookeeper.client.acl: openBut the configuration file actually generated after flink starts is as follows
high-availability:
high-availability.storageDir:
high-availability.zookeeper.quorum: ds-1:2181,ds-2:2181,ds-3:2181
high-availability.zookeeper.client.acl:
high-availability.zookeeper.path.root:Only the high-availability.zookeeper.quorum option is correctly written into the file All other configurations are empty
Although the configuration is correct on the interface, all files are empty
If I write the above configuration into custom.flink.conf.yaml, the flink-conf.yaml file will become as follows
high-availability:
high-availability.storageDir:
high-availability.zookeeper.quorum: ds-1:2181,ds-2:2181,ds-3:2181
high-availability.zookeeper.client.acl:
high-availability.zookeeper.path.root:
high-availability: zookeeper
high-availability.storageDir: hdfs://nameservice1/flink/ha/
high-availability.zookeeper.path.root: /flinkConfigurations that are not correctly assigned will be retained, and then will be duplicated with existing configuration options, and those that are left blank will remain blank. I don't know if this counts as a bug, but it seems to be handled in a weird way
What you expected to happen
The flink configuration does not actually take effect
How to reproduce
The flink configuration does not actually take effect
Anything else
No response
Version
dev
Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
datasophon
Search before asking
What happened
在安装完flink之后flink的一些关键配置虽然在界面上有所体现但是在配置文件 flink-conf.yaml 中依然是空值
譬如,图形界面中自动生成的默认配置如下
但是在flink启动后实际生成的配置文件如下
只有 high-availability.zookeeper.quorum 这个选项是被正确的写入文件当中 其他配置全是空的
在界面上虽然配置正确但是文件中全部是空的
如果我把上面的配置写到 custom.flink.conf.yaml 中 flink-conf.yaml 文件会变成下面这样
未正确赋值的配置会被保留, 然后会和已存在的配置选项发生重复, 留空的依然留空, 我不知道这算不算的上是bug, 但是看起来这种处理方式很奇怪
What you expected to happen
flink 配置未实际生效
How to reproduce
flink 配置未实际生效
Anything else
No response
Version
dev
Are you willing to submit PR?
Code of Conduct