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 <sjwies...@gmail.com> wrote: > 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 > mode going forward. > > Seth > > On Tue, Jun 22, 2021 at 5:02 AM Arvid Heise <ar...@apache.org> wrote: > > > +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 <trohrm...@apache.org> > > wrote: > > > > > 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, Jun 22, 2021 at 10:29 AM Chesnay Schepler <ches...@apache.org> > > > wrote: > > > > > > > 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 the Scala versions required by the > runtime > > > > and API, and would allow us to upgrade Akka as we'd no longer be > > limited > > > > to Scala 2.11. It would rid the classpath of a few dependencies, and > > > > remove the need for scala suffixes on quite a few modules. > > > > > > > > However, our Mesos support has unfortunately a hard dependency on > Akka, > > > > which naturally does not play well with the goal of isolating Akka in > > > > it's own ClassLoader. > > > > > > > > To solve this issue I was thinking of simple dropping flink-mesos in > > > > 1.14 (it was deprecated in 1.13). > > > > > > > > Truth be told, I picked this option because it is the easiest to do. > We > > > > _could_ probably make things work somehow (likely by shipping a > second > > > > Akka version just for flink-mesos), but it doesn't seem worth the > > hassle > > > > and would void some of the benefits. So far we kept flink-mesos > around, > > > > despite not really developing it further, because it didn't hurt to > > have > > > > it in still in Flink, but this has now changed. > > > > > > > > Please tell me what you think. > > > > > > > > > > > > > >
