Closed Vince-Cercury closed 6 years ago
Problem solved. I added this to my Flink task manager manifest file
`- name: data port: 6121
And this in the flink conf files :
taskmanager.data.port: 6121
So basically I pinned a data port for task manager. I had done that for the job manager (blob server port). And it was fine. But it looks like Calico works differently than Flannel and it could not use a random data port for task manager
I'm not sure it should be posted here. Please let me know if not appropriate.
We run Flink in Kubernetes 1.8 in AWS. It's been fine for monthsWe can also make it work with this helm. . I've setup a new k8s clusters recently.Everything the same EXCEPT we enabled Calico (instead of using only Flannel)
Calico gives us networking between containers.
Since enabling Calico, Flink client receive this error when trying to send a jar file to job manager:
It looks like the file cannot be transferred from the client to the job manager. I believe Invalid BLOB addressing is because the job manager did not receive any file.
I don't understand why we get Connection reset. I can see in tcpdump that the job manager and client use a number of ports to communicate and transfer file
Everything is the same. Works on one cluster. Does not work on another. Ports are configured the same. Every artefact is the same.
We don't have any NetworkPolicy. But would Calico enabled have some form of effect on networking?