Thanks,nacisimsek.I will try your suggestion.
-- Original --
From:
"nacisimsek"
Thanks,Gyula.I agree with you on Autoscaler,and I will try the latest Flink
Operator version.
-- --
??:
"Gyula F??ra"
Hi Enric,
You can try using persistent volume claim on your kubernetes cluster as a
JobResultStore, instead of using a local path from your underlying host, and
see if it works.
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: flink-data-pvc
spec:
resources:
requests:
st
Hi Eric!
The community cannot support old versions of the Flink operator, please
upgrade to the latest version (1.9.0)
Also, we do not recommend using the Reactive mode (with standalone). You
should instead try Native Mode + Autoscaler which works much better in most
cases.
Cheers,
Gyula
Hi,Community:
I hava encountered a problem when deploy reactive flink scheduler
on kubernetes with flink kubernetes operator 1.6.0,the manifest and exception
stack info listed as follows.
Any clues would be appreciated.
#
