Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 3 Aug 2017 06:39:31 -0700 (PDT)
From: Biplob Biswas <revolutionisme@gmail.com>
To: user@flink.apache.org
Message-ID: <1501767571314-14661.post@n4.nabble.com>
In-Reply-To: <8995551.xB4HX2ZWU8@nico-work>
References: <1501687739704-14644.post@n4.nabble.com> <1501753212112-14653.post@n4.nabble.com> <8995551.xB4HX2ZWU8@nico-work>
Subject: Re: Can't find correct JobManager address, job fails with Queryable
 state
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Thu, 03 Aug 2017 13:40:16 -0000

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.