Hi
In the apache flink documentation https://ci.apache.org/projects/flink/flink-docs-release-1.4/ops/deployment/kubernetes.html The order of creating the deployment and services are incorrect. It is mentioned in the order as follows- kubectl create -f jobmanager-deployment.yaml kubectl create -f taskmanager-deployment.yaml kubectl create -f jobmanager-service.yaml But this order of execution would fail if there is sufficient delay between the execution of 2nd and 3rd command. The reason being that the task manager is trying to connect to job manager through service name which is still not up. Ideally the order must be like this- kubectl create -f jobmanager-deployment.yaml kubectl create -f jobmanager-service.yaml kubectl create -f taskmanager-deployment.yaml Regards Sampath |
Adding on, it would be great if this is updated. If given the permission
then I can change it myself. On Mon, Mar 19, 2018 at 12:26 PM, Sampath Bhat <[hidden email]> wrote: > Hi > > In the apache flink documentation > https://ci.apache.org/projects/flink/flink-docs- > release-1.4/ops/deployment/kubernetes.html > > The order of creating the deployment and services are incorrect. It is > mentioned in the order as follows- > > kubectl create -f jobmanager-deployment.yaml > kubectl create -f taskmanager-deployment.yaml > kubectl create -f jobmanager-service.yaml > > But this order of execution would fail if there is sufficient delay > between the execution of 2nd and 3rd command. > > The reason being that the task manager is trying to connect to job manager > through service name which is still not up. > > Ideally the order must be like this- > > kubectl create -f jobmanager-deployment.yaml > kubectl create -f jobmanager-service.yaml > kubectl create -f taskmanager-deployment.yaml > > Regards > > Sampath > > |
Hi Sampath,
you can find the file under flink/docs/ops/deployment/kubernetes.md. Feel free to apply the change and open a PR against Flink's repository. Cheers, Till On Mon, Mar 19, 2018 at 7:57 AM, Sampath Bhat <[hidden email]> wrote: > Adding on, it would be great if this is updated. If given the permission > then I can change it myself. > > On Mon, Mar 19, 2018 at 12:26 PM, Sampath Bhat <[hidden email]> > wrote: > > > Hi > > > > In the apache flink documentation > > https://ci.apache.org/projects/flink/flink-docs- > > release-1.4/ops/deployment/kubernetes.html > > > > The order of creating the deployment and services are incorrect. It is > > mentioned in the order as follows- > > > > kubectl create -f jobmanager-deployment.yaml > > kubectl create -f taskmanager-deployment.yaml > > kubectl create -f jobmanager-service.yaml > > > > But this order of execution would fail if there is sufficient delay > > between the execution of 2nd and 3rd command. > > > > The reason being that the task manager is trying to connect to job > manager > > through service name which is still not up. > > > > Ideally the order must be like this- > > > > kubectl create -f jobmanager-deployment.yaml > > kubectl create -f jobmanager-service.yaml > > kubectl create -f taskmanager-deployment.yaml > > > > Regards > > > > Sampath > > > > > |
Hi I have modified the documentation.
Please refer the link: https://github.com/apache/flink/pull/5721 Let me know if I have to do any further action On Mon, Mar 19, 2018 at 3:28 PM, Till Rohrmann <[hidden email]> wrote: > Hi Sampath, > > you can find the file under flink/docs/ops/deployment/kubernetes.md. Feel > free to apply the change and open a PR against Flink's repository. > > Cheers, > Till > > On Mon, Mar 19, 2018 at 7:57 AM, Sampath Bhat <[hidden email]> > wrote: > > > Adding on, it would be great if this is updated. If given the permission > > then I can change it myself. > > > > On Mon, Mar 19, 2018 at 12:26 PM, Sampath Bhat <[hidden email]> > > wrote: > > > > > Hi > > > > > > In the apache flink documentation > > > https://ci.apache.org/projects/flink/flink-docs- > > > release-1.4/ops/deployment/kubernetes.html > > > > > > The order of creating the deployment and services are incorrect. It is > > > mentioned in the order as follows- > > > > > > kubectl create -f jobmanager-deployment.yaml > > > kubectl create -f taskmanager-deployment.yaml > > > kubectl create -f jobmanager-service.yaml > > > > > > But this order of execution would fail if there is sufficient delay > > > between the execution of 2nd and 3rd command. > > > > > > The reason being that the task manager is trying to connect to job > > manager > > > through service name which is still not up. > > > > > > Ideally the order must be like this- > > > > > > kubectl create -f jobmanager-deployment.yaml > > > kubectl create -f jobmanager-service.yaml > > > kubectl create -f taskmanager-deployment.yaml > > > > > > Regards > > > > > > Sampath > > > > > > > > > |
Free forum by Nabble | Edit this page |