[
https://issues.apache.org/jira/browse/FLINK-31228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31228:
-----------------------------------
Labels: Docker auto-deprioritized-major pull-request-available (was:
Docker pull-request-available stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Major, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> flink-playgrounds is using a buggy zookeeper
> --------------------------------------------
>
> Key: FLINK-31228
> URL: https://issues.apache.org/jira/browse/FLINK-31228
> Project: Flink
> Issue Type: Bug
> Reporter: CHEN Zhongpu
> Priority: Minor
> Labels: Docker, auto-deprioritized-major, pull-request-available
>
> The flink-playgrounds [1] is using a buggy zookeeper image from docker hub,
> and thus the kafka can never connect to the zookeeper server.
> ----
> How to reproduce the bug?
> For example, after running "docker-compose up -d" in operations-playground
> [2], we can observe in Flink web UI that the job will in "restarting" state
> soon, and both "zookeeper" and "kafka" are stopped.
> ----
> I noticed that the used "wurstmeister/zookeeper:3.4.6" image was published in
> 7 years ago, and it is badly documented. In my test, switching to
> "bitnami/zookeeper:3.7.1" can solve this problem.
> Also, I think it would be better to discard images published by wurstmeister,
> since they are not updated frequently (and there buggy), and we should switch
> to bitnami.
>
>
> [1][https://github.com/apache/flink-playgrounds|https://github.com/apache/flink-playgrounds)]
> [2]
> [https://github.com/apache/flink-playgrounds/tree/master/operations-playground)]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
