[
https://issues.apache.org/jira/browse/FLINK-23535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393042#comment-17393042
]
tim yu commented on FLINK-23535:
--------------------------------
Hi [~jark], [~yunta], The following steps can reproduce this issue on the node
host1.
# Configure high availability mode and ZooKeeper quorum in
{{$FLINK_CONF_DIR/flink-conf.yaml}}:
high-availability: zookeeper
high-availability.zookeeper.quorum: host1:2181,host2:2181,host3:2181
high-availability.zookeeper.path.root: /flink
high-availability.cluster-id: /cluster_001
high-availability.storageDir: hdfs:///flink/recovery
# Use yarn-session.sh to create succesfully a YARN session cluster.
# Use sql-client.sh to run an INSERT statement.
The JobSubmissionException that is caused by the TimeoutException is thrown. I
find a line log "Using /flink/application_xxxxxxxxxxxxx_xxxx as Zookeeper
namespace" in log file of sql-client.
I can only describe this issue simply because copy the log file of sql-client
from my company node is very difficult.
> The value of option high-availability.cluster-id in flink-conf.yaml is
> replaced improperly
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-23535
> URL: https://issues.apache.org/jira/browse/FLINK-23535
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission, Table SQL / Client
> Affects Versions: 1.12.3
> Reporter: tim yu
> Priority: Major
>
> The value of option high-availability.cluster-id in flink-conf.yaml is
> replaced improperly with application ID when submitting a job to YARN.
> I guess that maybe the FLINK-19493 causes this problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
