[
https://issues.apache.org/jira/browse/FLINK-31282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-31282:
-----------------------------------
Labels: pull-request-available stale-major (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Create and Close the zookeeper connection frequently
> ----------------------------------------------------
>
> Key: FLINK-31282
> URL: https://issues.apache.org/jira/browse/FLINK-31282
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission
> Affects Versions: 1.16.0
> Reporter: shenyue
> Priority: Major
> Labels: pull-request-available, stale-major
>
> When I use sql " *select * from table* " , I found there are a lot logs about
> zookeeper connection Information. There is *critical* for Zookeeper ，because
> *the Connection* is *create and close frequently*
>
> [
>
> 2023-03-01 19:38:38.423 INFO (Thread-262) [ ]
> o.a.f.r.l.DefaultLeaderRetrievalService Starting DefaultLeaderRetrievalServic
> e with
> ZookeeperLeaderRetrievalDriver\{connectionInformationPath='/leader/rest_server/connection_info'}.
> 2023-03-01 19:38:38.424 INFO (Thread-262-SendThread(node53.hde.com:2181)) [
> ] o.a.f.s.z.o.a.z.ClientCnxn Socket connection
> established, initiating session, client: /10.121.65.53:58428, server:
> node53.hde.com/10.121.65.53:2181
> 2023-03-01 19:38:38.427 INFO (Thread-262-SendThread(node53.hde.com:2181)) [
> ] o.a.f.s.z.o.a.z.ClientCnxn Session establishm
> ent complete on server node53.hde.com/10.121.65.53:2181, session id =
> 0x10000038726412a, negotiated timeout = 60000
> 2023-03-01 19:38:38.427 INFO (Thread-262-EventThread) [ ]
> o.a.f.s.c.o.a.c.f.s.ConnectionStateManager State change: CONNECTE
> D
> 2023-03-01 19:38:38.430 INFO (Thread-262-EventThread) [ ]
> o.a.f.s.c.o.a.c.f.i.EnsembleTracker New config event received: {s
> erver.1=node53.hde.com:2888:3888:participant, version=0,
> server.3=node55.hde.com:2888:3888:participant, server.2=node54.hde.co
> m:2888:3888:participant}
> 2023-03-01 19:38:38.431 INFO (Thread-262-EventThread) [ ]
> o.a.f.s.c.o.a.c.f.i.EnsembleTracker New config event received: {s
> erver.1=node53.hde.com:2888:3888:participant, version=0,
> server.3=node55.hde.com:2888:3888:participant, server.2=node54.hde.co
> m:2888:3888:participant}
> 2023-03-01 19:38:38.700 INFO (ForkJoinPool.commonPool-worker-11) [ ]
> o.a.f.r.l.DefaultLeaderRetrievalService Stopping Defau
> ltLeaderRetrievalService.
> 2023-03-01 19:38:38.700 INFO (ForkJoinPool.commonPool-worker-11) [ ]
> o.a.f.r.l.ZooKeeperLeaderRetrievalDriver Closing Zooke
> eperLeaderRetrievalDriver\{connectionInformationPath='/leader/rest_server/connection_info'}.
> 2023-03-01 19:38:38.702 INFO (Curator-Framework-0) [ ]
> o.a.f.s.c.o.a.c.f.i.CuratorFrameworkImpl backgroundOperationsLoop ex
> iting
> 2023-03-01 19:38:38.708 WARN (Thread-262-SendThread(node53.hde.com:2181)) [
> ] o.a.f.s.z.o.a.z.ClientCnxn An exception was t
> hrown while closing send thread for session 0x10000038726412a.
> org.apache.flink.shaded.zookeeper3.org.apache.zookeeper.ClientCnxn$EndOfStreamException:
> Unable to read additional data from s
> erver sessionid 0x10000038726412a, likely server has closed socket
> at
> org.apache.flink.shaded.zookeeper3.org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:77)
> ~[fli
> nk-shaded-zookeeper-3.6.3.jar:3.6.3-15.0]
> at
> org.apache.flink.shaded.zookeeper3.org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:35
> 0) ~[flink-shaded-zookeeper-3.6.3.jar:3.6.3-15.0]
> at
> org.apache.flink.shaded.zookeeper3.org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1290)
> [flink-shad
> ed-zookeeper-3.6.3.jar:3.6.3-15.0]
> 2023-03-01 19:38:38.810 INFO (Thread-262-EventThread) [ ]
> o.a.f.s.z.o.a.z.ClientCnxn EventThread shut down for session: 0x1
> 0000038726412a
> 2023-03-01 19:38:38.810 INFO (ForkJoinPool.commonPool-worker-11) [ ]
> o.a.f.s.z.o.a.z.ZooKeeper Session: 0x10000038726412a c
> losed
> 2023-03-01 19:38:38.813 INFO (Thread-262) [ ] o.a.f.r.u.ZooKeeperUtils
> Enforcing default ACL for ZK connections
> 2023-03-01 19:38:38.813 INFO (Thread-262) [ ] o.a.f.r.u.ZooKeeperUtils
> Using '/flink/application_1677479737242_0025' as Zoo
> keeper namespace.
> 2023-03-01 19:38:38.814 INFO (Thread-262) [ ]
> o.a.f.s.c.o.a.c.f.i.CuratorFrameworkImpl Starting
> 2023-03-01 19:38:38.814 INFO (Thread-262) [ ] o.a.f.s.z.o.a.z.ZooKeeper
> Initiating client connection, connectString=node54.
> hde.com:2181,node55.hde.com:2181,node53.hde.com:2181 sessionTimeout=60000
> watcher=org.apache.flink.shaded.curator5.org.apache.
> curator.ConnectionState@74e5bc14
> 2023-03-01 19:38:38.814 INFO (Thread-262) [ ]
> o.a.f.s.z.o.a.z.ClientCnxnSocket jute.maxbuffer value is 1048575 Bytes
> 2023-03-01 19:38:38.814 INFO (Thread-262) [ ] o.a.f.s.z.o.a.z.ClientCnxn
> zookeeper.request.timeout value is 0. feature enab
> led=false
> 2023-03-01 19:38:38.815 INFO (Thread-262) [ ]
> o.a.f.s.c.o.a.c.f.i.CuratorFrameworkImpl Default schema
> 2023-03-01 19:38:38.815 INFO (Thread-262) [ ]
> o.a.f.r.l.DefaultLeaderRetrievalService Starting DefaultLeaderRetrievalServic
> e with
> ZookeeperLeaderRetrievalDriver\{connectionInformationPath='/leader/rest_server/connection_info'}.
> 2023-03-01 19:38:38.817 INFO (Thread-262-SendThread(node53.hde.com:2181)) [
> ] o.a.f.s.z.o.a.z.ClientCnxn Opening socket con
> nection to server node53.hde.com/10.121.65.53:2181.
> 2023-03-01 19:38:38.817 INFO (Thread-262-SendThread(node53.hde.com:2181)) [
> ] o.a.f.s.z.o.a.z.ClientCnxn SASL config status
> : Will not attempt to authenticate using SASL (unknown error)
> 2023-03-01 19:38:38.817 INFO (Thread-262-SendThread(node53.hde.com:2181)) [
> ] o.a.f.s.z.o.a.z.ClientCnxn Socket connection
> established, initiating session, client: /10.121.65.53:58432, server:
> node53.hde.com/10.121.65.53:2181
> 2023-03-01 19:38:38.821 INFO (Thread-262-SendThread(node53.hde.com:2181)) [
> ] o.a.f.s.z.o.a.z.ClientCnxn Session establishm
> ent complete on server node53.hde.com/10.121.65.53:2181, session id =
> 0x10000038726412b, negotiated timeout = 60000
> 2023-03-01 19:38:38.821 INFO (Thread-262-EventThread) [ ]
> o.a.f.s.c.o.a.c.f.s.ConnectionStateManager State change: CONNECTE
> D
> 2023-03-01 19:38:38.824 INFO (Thread-262-EventThread) [ ]
> o.a.f.s.c.o.a.c.f.i.EnsembleTracker New config event received: {s
> erver.1=node53.hde.com:2888:3888:participant, version=0,
> server.3=node55.hde.com:2888:3888:participant, server.2=node54.hde.co
> m:2888:3888:participant}
>
> ]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
