Hi,
+1 on dropping Mesos support to clear dependencies in the flink-runtime
module:
- I tend to think as Seth and Israel and see a bit of a decline of the
use of Mesos: as an example of that, AFAICT, Amazon EMR and Amazon EKS
provide Yarn and Kubernates support but no Mesos. I did not know about
most of the Mesos PMC leaving that Fabian mentioned but it is once again
a sign IMHO.
- the survey among users seems to have concluded that the removal is
possible.
Best,
Etienne
On 23/06/2021 14:29, Stephan Ewen wrote:
I would prefer to remove Mesos from the Flink core as well.
I also had a similar thought as Seth: As far as I know, you can package
applications to run on Mesos with "Marathon". That would be like deploying
an opaque Flink standalone cluster on Mesos
The implication is similar to going from an active integration to a
standalone cluster (like from native Flink Kubernetes Application
Deployment to a Standalone Application Deployment on Kubernetes): You need
to make sure the number of TMs / slots and the parallelism fit together (or
use the new reactive mode). Other than that, I think it should work well
for streaming jobs.
Having a Flink-Marathon template in https://flink-packages.org/ would be a
nice thing for Mesos users.
@Oleksandr What do you think about that?
On Wed, Jun 23, 2021 at 11:31 AM Leonard Xu <xbjt...@gmail.com> wrote:
+ 1 for dropping Mesos. I checked both commit history and mail list, the
Mesos related issue/user question has been rarely appeared.
Best,
Leonard
