We recently bumped to Flink 1.4 from 1.3.2, and found out an issue on HDFS configuration.
We are using FlinkYarnSessionCli to start the cluster and submit job.
In 1.3.2, we set below Flink properties when using checkpoints:
The mapping between logical nameservice (nameservice0) and actual namenodes hostports are passed to Flink via yarnship/core-site.xml (by providing the -yt option), and set fs.hdfs.hadoopconf=yarnship/
However, we encountered below error after bumping to 1.4, which caused the checkpointing to fail.
It does not recognize nameservice0 because the core-site.xml on the actual machine (read in by Flink via $HADOOP_CONF_DIR) does not use nameservice0 but something else for the fs.defaultFs
Digging a little bit, I found that the hadoopConfig
) does not have the properties we set via yarnship/core-site.xml
. Especially, I suspect it is due to the cached HadoopFsFactory
is initialized with an dummy Configuration (code
), which prevents future flinkConfig
getting passed in (code
I am not sure if this is intentional, or has been solved in later releases. Has anyone encountered the same problem? And I would appreciate any suggestions.