Error Message "ClusterRetrieveException" Is Displayed When the flink Command Is Executed on the Flink Client

Context and Symptom

An error is reported when the flink run/list/cancel command is executed on the client. The error information is as follows:

org.apache.flink.util.FlinkException: Failed to retrieve job list.
 at org.apache.flink.client.cli.CliFrontend.listJobs(CliFrontend.java:448)
 at org.apache.flink.client.cli.CliFrontend.lambda$list$0(CliFrontend.java:430)
 at org.apache.flink.client.cli.CliFrontend.runClusterAction(CliFrontend.java:985)
 at org.apache.flink.client.cli.CliFrontend.list(CliFrontend.java:427)
 at org.apache.flink.client.cli.CliFrontend.parseParameters(CliFrontend.java:1053)
 at org.apache.flink.client.cli.CliFrontend.lambda$main$11(CliFrontend.java:1126)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAs(Subject.java:422)
 at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1729)
 at org.apache.flink.runtime.security.HadoopSecurityContext.runSecured(HadoopSecurityContext.java:41)
 at org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1126)
Caused by: java.util.concurrent.TimeoutException
 at org.apache.flink.runtime.concurrent.FutureUtils$Timeout.run(FutureUtils.java:795)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)

Possible Causes

• A client outside the cluster is used.
• The specified Flink cluster does not exist, or the client fails to connect to the cluster.
• An incorrect client is used. The client configuration is different from that used for submitting tasks.

Solution

1. Check whether the client is outside the cluster. If it is outside the cluster, add the client IP address to the /etc/hosts file of the cluster.
2. Log in to the native page of the Yarn service and check whether the Flink cluster connected to the client is in the Running state.
3. Check whether the client used for submitting the task is the same as the current client and whether the values of configuration item high-availability.zookeeper.path.root are the same.