Re: Flink(1.12.2/scala 2.11) HA with Zk in kubernetes standalone mode deployment is not working

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Flink(1.12.2/scala 2.11) HA with Zk in kubernetes standalone mode deployment is not working

Matthias
Hi Bhagi,
Thanks for reaching out to the Flink community. The error the UI is showing is normal during an ongoing leader election. Additionally, the connection refused warnings seem to be normal according to other mailing list threads. Are you referring to the UI error as the issue you are facing? 

What puzzles me a bit are the timestamps of your provided logs. They do not seem to be fully aligned. Are there more logs that might indicate other issues?

Matthias

PS: I'm gonna add the user mailing list as this issue should usually be posted there.

On Mon, May 3, 2021 at 5:21 PM bhagi@R <[hidden email]> wrote:
Hi Team,

I deployed kubernetes standalone deployment flink cluster with ZK HA, but
facing some issues, i have attached taskmanager and job manger logs.

Can you please see the logs and help me solve this issue.

UI is throwing this error:

{"errors":["Service temporarily unavailable due to an ongoing leader
election. Please refresh."]}

jobmanager.log
<http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/file/t1598/jobmanager.log
taskmanager.log
<http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/file/t1598/taskmanager.log
screenshot-1.png
<http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/file/t1598/screenshot-1.png



--
Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: Flink(1.12.2/scala 2.11) HA with Zk in kubernetes standalone mode deployment is not working

Till Rohrmann
Somewhere the system retrieves the address x.x.x.x:43092 which cannot be connected to. Can you check that this points towards a valid Flink process? Maybe it is some leftover information in the ZooKeeper from a previous run? Maybe you can check what's written in the Znodes for /leader/resource_manager_lock. You can also enable DEBUG logs which will tell you a bit more about what is happening.

Cheers,
Till

On Mon, May 3, 2021 at 7:12 PM Matthias Pohl <[hidden email]> wrote:
Hi Bhagi,
Thanks for reaching out to the Flink community. The error the UI is showing is normal during an ongoing leader election. Additionally, the connection refused warnings seem to be normal according to other mailing list threads. Are you referring to the UI error as the issue you are facing? 

What puzzles me a bit are the timestamps of your provided logs. They do not seem to be fully aligned. Are there more logs that might indicate other issues?

Matthias

PS: I'm gonna add the user mailing list as this issue should usually be posted there.

On Mon, May 3, 2021 at 5:21 PM bhagi@R <[hidden email]> wrote:
Hi Team,

I deployed kubernetes standalone deployment flink cluster with ZK HA, but
facing some issues, i have attached taskmanager and job manger logs.

Can you please see the logs and help me solve this issue.

UI is throwing this error:

{"errors":["Service temporarily unavailable due to an ongoing leader
election. Please refresh."]}

jobmanager.log
<http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/file/t1598/jobmanager.log
taskmanager.log
<http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/file/t1598/taskmanager.log
screenshot-1.png
<http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/file/t1598/screenshot-1.png



--
Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/