Hi Team, We are analysing different deployment options for managing Flink Jobs on AWS EC2 instances. -> Deploy using Mesos/Marthon -> Deploy using Kubernetes/Docker |
Hi CVP,
On how people use Flink, you can check this blogpost to see how Alibaba does it: In addition, you can also find some more information on the matter on the talks from the last Flink Forwards conference: http://berlin.flink-forward.org/program/sessions/ For example Netflix also shares some information here: Now for how things work under the hood, I will provide links to the Flink documentation. I hope that this will also help you figure out what fits your needs best: For deployment and operations, the main resource is the Flink documentation, and for what is about to come on that front, you can check out the FLIP-6 page: To dynamically scale your Flink job you have to take a savepoint and restart your job with different parallelism. You can find some details here https://www.slideshare.net/tillrohrmann/dynamic-scaling-how-apache-flink-adapts-to-changing-workloads , but unfortunately, this talk is a little bit outdated. We will update our documentation on dynamic scaling soon. For the Resource allocation and Job Scheduling, you can check the links I included for deployment and operations, and also this: https://ci.apache.org/projects/flink/flink-docs-release-1.3/internals/job_scheduling.html For metrics and monitoring you can check here: https://ci.apache.org/projects/flink/flink-docs-release-1.2/monitoring/metrics.html and the related pages in the Debugging and monitoring section of the Flink documentation. I hope this can help as a first step, Kostas
|
Free forum by Nabble | Edit this page |