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 a
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 act
+ 1 for dropping Mesos. I checked both commit history and mail list, the Mesos
related issue/user question has been rarely appeared.
Best,
Leonard
+ 1 for dropping mesos. Most of the PMCs have already left the project [1] and
a move to attic
was barely avoided. Overall kubernetes has taken its place and it is unlikely
that we will see a
surge in Mesos very soon.
Best,
Fabian
[1]
https://lists.apache.org/thread.html/rab2a820507f7c846e54
+1 for dropping mesos support.
AFAIK, mesos(including marathon for the container management) is phasing
out gradually and has been replaced with Kubernetes in the containerized
world.
Best,
Yang
Matthias Pohl 于2021年6月23日周三 下午2:04写道：
> +1 for dropping Mesos support. There was no feedback oppos
+1 for dropping Mesos support. There was no feedback opposing the direction
from the community in the most-recent discussion [1,2] on deprecating it.
Matthias
[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/SURVEY-Remove-Mesos-support-td45974.html
[2]
http://apache-flink-mailin
+1 for dropping if there is no strong demand from the community.
I'm willing to help with the removal of e2e tests part.
Best,
Yangze Guo
On Wed, Jun 23, 2021 at 10:09 AM Xintong Song wrote:
>
> +1 for dropping.
>
> I like Seth's idea. I don't have any real Mesos experience either.
> According
+1 for dropping.
I like Seth's idea. I don't have any real Mesos experience either.
According to this article [1], it looks like we can deploy a standalone
cluster on Mesos similar to Kubernetes. However, we should only do it if
there's indeed a strong demand from the community for deploying a
lat
I am in favor of dropping the support for Mesos.
In terms of the landscape for users leveraging Mesos for the kind of
workloads Flink is used, I think it is on the decline.
+1 from me
On Tue, Jun 22, 2021 at 11:32 AM Seth Wiesman wrote:
> Sorry if this is a naive question, I don't have any rea
Sorry if this is a naive question, I don't have any real Mesos experience.
Is it possible to deploy a standalone cluster on top of Mesos in the same
way you can with Kubernetes? If so, and there is still Mesos demand from
the community, we could document that process as the recommended deployment
m
+1 for dropping. Frankly speaking, I don't see it having any future (and D2iQ
agrees).
If there is a surprisingly huge demand, I'd try to evaluate plugins for it.
On Tue, Jun 22, 2021 at 11:46 AM Till Rohrmann wrote:
> I'd be ok with dropping support for Mesos if it helps us to clear our
> depe
I'd be ok with dropping support for Mesos if it helps us to clear our
dependencies in the flink-runtime module. If we do it, then we should
probably update our documentation with a pointer to the latest Flink
version that supports Mesos in case of users strictly need Mesos.
Cheers,
Till
On Tue, J
I'm adding Oleksandr from Criteo to this thread, they've mentioned in the
past that they are using Flink on Mesos (IIRC the only company that seemed
to be doing so)
I'm personally fine with dropping Mesos support.
On Tue, Jun 22, 2021 at 10:29 AM Chesnay Schepler
wrote:
> Last week I spent some
Last week I spent some time looking into making flink-runtime scala
free, which effectively means to move the Akka-reliant classes to
another module, and load that module along with Akka and all of it's
dependencies (including Scala) through a separate classloader.
This would finally decouple
14 matches
Mail list logo
