Hi, I'm afraid you are running into roughly this problem: https://issues.apache.org/jira/browse/FLINK-6689 <https://issues.apache.org/jira/browse/FLINK-6689>
It's not possible anymore to connect to a LocalFlinkMiniCluster, either via a RemoteExecutionEnvironment or via the queryable state client. Best, Aljoscha > On 3. Aug 2017, at 15:39, Biplob Biswas <revolutioni...@gmail.com> wrote: > > Hi Nico, > > I had actually tried doing that but I still get the same error as before > with the actor not found. I then ran on my mock cluster and I was getting > the same error although I could observe the jobmanager on the yarn cluster > mode with a defined port. > > The addres and port combination was random and as mentioned here > <https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/yarn_setup.html> > > , the the JobManager is always allocated at different machines. > > So to circumvent this issue, I created a flink yarn session and ran my job > within this session. As the jobmanager is fixed within a yarn session, so I > set my jobmanager address and port using the corresponding data. > > Now it can connect to jobmanager (only on cluster, still not on local mode) > but the job id I specified was wrong and I don't really know how to fetch > the jobid of my flink job within a running instance. > > Thanks, > Biplob > > > > -- > View this message in context: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Can-t-find-correct-JobManager-address-job-fails-with-Queryable-state-tp14644p14661.html > Sent from the Apache Flink User Mailing List archive. mailing list archive at > Nabble.com.
