zhu created FLINK-32943:
---------------------------
Summary: sometime run batch tasks concurrently, the tasks still in
the initialization status
Key: FLINK-32943
URL: https://issues.apache.org/jira/browse/FLINK-32943
Project: Flink
Issue Type: Bug
Environment: flink 1.15.2
|*lob.server.port*|6124|
|*classloader.resolve-order*|parent-first|
|*jobmanager.execution.failover-strategy*|region|
|*jobmanager.memory.heap.size*|2228014280b|
|*jobmanager.memory.jvm-metaspace.size*|536870912b|
|*jobmanager.memory.jvm-overhead.max*|322122552b|
|*jobmanager.memory.jvm-overhead.min*|322122552b|
|*jobmanager.memory.off-heap.size*|134217728b|
|*jobmanager.memory.process.size*|3gb|
|*jobmanager.rpc.address*|naf-flink-ms-flink-manager-1-4gcwz|
|*jobmanager.rpc.port*|6123|
|*parallelism.default*|1|
|*query.server.port*|6125|
|*rest.address*|0.0.0.0|
|*rest.bind-address*|0.0.0.0|
|*rest.connection-timeout*|60000|
|*rest.server.numThreads*|8|
|*slot.request.timeout*|3000000|
|*state.backend.rocksdb.localdir*|/home/nafplat/data/flinkStateStore|
|*state.backend.type*|rocksdb|
|*taskmanager.bind-host*|0.0.0.0|
|*taskmanager.host*|0.0.0.0|
|*taskmanager.memory.framework.off-heap.batch-shuffle.size*|256mb|
|*taskmanager.memory.framework.off-heap.size*|512mb|
|*taskmanager.memory.managed.fraction*|0.4|
|*taskmanager.memory.network.fraction*|0.2|
|*taskmanager.memory.process.size*|16gb|
|*taskmanager.memory.task.off-heap.size*|268435456bytes|
|*taskmanager.numberOfTaskSlots*|6|
|*taskmanager.runtime.large-record-handler*|true|
|*web.submit.enable*|true|
|*web.tmpdir*|/tmp/flink-web-4be192ba-870a-4f88-8185-d07fa6303cca|
|*web.upload.dir*|/opt/flink/nafJar|
Reporter: zhu
run 1.15.2 flink session on k8s，In most cases, there is no problem. Sometimes,
tasks are initialized continuously, and subsequent tasks are also initialized
continuously，
I run batch job with 6 concurrent,jobmanage with 2cpu and 3g Memory
This problem always occurs, it seems that there is a deadlock during
initialization, but my job does not have any deadlock issues
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
