Jeff Zhang

@amit-shahi You can download latest zeppelin 0.9 which support flink 1.11, but we haven't verified it on k8s

I am afraid the docker image of 0.9 is still using 0.9.0-preview2, we are working on it to upgrade to 0.9.0 But it still support flink 1.11 IIRC.

@amit-shahi You can refer the document here, remote mode is the way you should use I believe, https://app.gitbook.com/@jeffzhang/s/flink-on-zeppelin/execution-mode/remote-mode

flink should be put in the same host of zeppelin. FLINK_HOME point to that location.

You need to put flink in pod3 and specify FLINK_HOME to this path. Then specify flink.execution.remote.host and flink.execution.remote.port as the JobManager rest api address

You need to set `zeppelin.run.mode` as `local` in zeppelin-site.xml, otherwise zeppelin would launch flink interpreter in another pod which may cause this issue.

@amit-shahi Let's discuss that in user mail list.

> So, modify to the average policy and start the same number of interpreters in each server. Then it will require all the machines in the cluster to be the...

This is what I concern. Why do you think choosing A is correct ? IIUC, we have to assume that A,B,C have the same computing resources (cpu cores and memory)...

> So scheduling by quantity is better than following the way of resources. This is based on the 2 assumptions I mentioned above, right ?