[ 
https://issues.apache.org/jira/browse/FLINK-22938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359777#comment-17359777
 ] 

Robert Metzger commented on FLINK-22938:
----------------------------------------

The log you've uploaded is not the full jobmanager log (it's located in the 
log/ directory). Most likely, the TaskManagers are unable to connect to your 
JobManager. I'd recommend checking the JobManager interface to see if 
TaskManagers are connecting. If not, check the TaskManager logs to find out why.

> Slot request bulk is not fulfillable! Could not allocate the required slot 
> within slot request timeout
> ------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-22938
>                 URL: https://issues.apache.org/jira/browse/FLINK-22938
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.12.4
>            Reporter: Bhagi
>            Priority: Major
>         Attachments: flink -jobmanager logs.txt
>
>
> Hi team,
> I tested cluster upgrade from Flink Version 1.12.4 to 1.13.1 ,due to 1 job 
> issues latest version cluster went into crashloopbackoff with error. hence i 
> degraded to old cluster version. from latest upgraded version 1.13.1 to  
> 1.12.4 it was successful. But all job executions are failed state.
> with following error."Slot request bulk is not fulfillable! Could not 
> allocate the required slot within slot request ".please find the log.
> flink@flink-jobmanager-657cb5d847-5b579:~$ cat conf/flink-conf.yaml
> taskmanager.numberOfTaskSlots: 2
> jobmanager.rpc.address: flink-jobmanager
> blob.server.port: 6124
> jobmanager.rpc.port: 6123
> taskmanager.rpc.port: 6122
> queryable-state.proxy.ports: 6125
> jobmanager.memory.process.size: 1600m
> taskmanager.memory.process.size: 1728m
> parallelism.default: 2
> rest.connection-timeout: 25000
> web.log.path: /opt/flink/log/output.log
> taskmanager.log.path: /opt/flink/log/output.log
> state.backend: rocksdb
> state.checkpoints.dir: file:///persistent/flinkData/checkpoints
> state.backend.rocksdb.log.dir: /persistent/flinkData/rocksdb/logging/
> state.savepoints.dir:  file:///persistent/flinkData/savepoints
> state.backend.incremental: true
> state.checkpoints.num-retained: 1
> web.upload.dir: /persistent/flinkData
> classloader.resolve-order: parent-first
> kubernetes.cluster-id: 222
> kubernetes.namespace: flink-mcd
> high-availability: 
> org.apache.flink.kubernetes.highavailability.KubernetesHaServicesFactory
> high-availability.storageDir: file:///persistent/flinkData/checkpoints
> jobmanager.archive.fs.dir: file:///persistent/flinkData/completed-jobs
> historyserver.archive.fs.refresh-interval: 10000
> historyserver.archive.fs.dir: file:///persistent/flinkData/completed-jobs
> metrics.reporters: prom
> metrics.reporter.prom.class: 
> org.apache.flink.metrics.prometheus.PrometheusReporter
> metrics.reporter.prom.port: 9090
> akka.framesize: 10485760b
> flink@flink-jobmanager-657cb5d847-5b579:~$



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to