Oct 27, 2020 at 12:29 PM Oleksandr Nitavskyi <
> > >>>> > o.nitavs...@criteo.com> wrote:
> > >>>> >
> > >>>> >> Hello Xintong,
> > >>>> >>
> > >>>> >> Thanks for the insights and support.
> > >>>> >>
> > >
> >>>> >> is left there.
> >>>> >>
> >>>> >> I see that there are were quite a lot of contributions to the
> Flink Mesos
> >>>> >> in the recent version:
> >>>> >> https://github.com/apache/fl
the Flink
>>>> >> Mesos
>>>> >> in the recent version:
>>>> >> https://github.com/apache/flink/commits/master/flink-mesos.
>>>> >> We plan to validate the current Flink master (or release 1.12 branch)
>&
utions to the Flink
>>> Mesos
>>> >> in the recent version:
>>> >> https://github.com/apache/flink/commits/master/flink-mesos.
>>> >> We plan to validate the current Flink master (or release 1.12 branch)
>>> our
>>> >> Mes
(or release 1.12 branch)
>> our
>> >> Mesos setup. In case of any issues, we will try to propose changes.
>> >> My feeling is that our test results shouldn't affect the Flink 1.12
>> >> release cycle. And if any potential commits will land into the 1.12.1
>> it
&
;> Yarn for some our Flink workloads when we can. Mesos is only used when
> we
> >> need streaming capabilities in our WW dcs (as our Yarn is centralized in
> >> one DC)
> >> * We’re currently on Flink 1.9 (old planner). We have a plan to bump
> >> to 1.1
d be glad to help you guys with any
>> maintenance-related questions. One of the highest priorities around this
>> component seems to be the development of the full e2e test.
>>
>> Kind Regards
>> Oleksandr Nitavskyi
>>
>> From:
ntenance-related questions. One of the highest priorities around this
> component seems to be the development of the full e2e test.
>
> Kind Regards
> Oleksandr Nitavskyi
>
> From: Xintong Song
> Sent: Tuesday, October 27, 2020 7:14 AM
> To: dev
Song
Sent: Tuesday, October 27, 2020 7:14 AM
To: dev ; user
Cc: Piyush Narang
Subject: [BULK]Re: [SURVEY] Remove Mesos support
Hi Piyush,
Thanks a lot for sharing the information. It would be a great relief that you
are good with Flink on Mesos as is.
As for the jira issues, I believe the most
port it over.
>
>
>
> Thanks,
>
>
>
> -- Piyush
>
>
>
>
>
> *From: *Xintong Song
> *Date: *Sunday, October 25, 2020 at 10:57 PM
> *To: *dev , user
> *Cc: *Lasse Nedergaard , <
> p.nar...@criteo.com>
> *Subject: *Re: [SURVEY] Remove Me
in Flink on Yarn / K8s that we want in Mesos to put in the request to port it
over.
Thanks,
-- Piyush
From: Xintong Song
Date: Sunday, October 25, 2020 at 10:57 PM
To: dev , user
Cc: Lasse Nedergaard ,
Subject: Re: [SURVEY] Remove Mesos support
Thanks for sharing the information with us
e as well when they touch the
>> resource managers?)
>> >
>> >
>> >
>> > Thanks,
>> >
>> >
>> >
>> > -- Piyush
>> >
>> >
>> >
>> &
hey touch the
>> resource managers?)
>> >
>> >
>> >
>> > Thanks,
>> >
>> >
>> >
>> > -- Piyush
>> >
>> >
>> >
>> >
>> >
>>
> Thanks,
> >
> >
> >
> > -- Piyush
> >
> >
> >
> >
> >
> > From: Till Rohrmann
> > Date: Friday, October 23, 2020 at 8:19 AM
> > To: Xintong Song
> > Cc: dev , user
>
; Date: Friday, October 23, 2020 at 8:19 AM
> To: Xintong Song
> Cc: dev , user
> Subject: Re: [SURVEY] Remove Mesos support
>
>
>
> Thanks for starting this survey Robert! I second Konstantin and Xintong
in the sense that our Mesos user's op
Friday, October 23, 2020 at 8:19 AM
> To: Xintong Song
> Cc: dev , user
> Subject: Re: [SURVEY] Remove Mesos support
>
>
>
> Thanks for starting this survey Robert! I second Konstantin and Xintong in
> the sense that our Mesos user's opinions should matter most here. If our
to ensure PRs handle the Mesos piece
as well when they touch the resource managers?)
Thanks,
-- Piyush
From: Till Rohrmann
Date: Friday, October 23, 2020 at 8:19 AM
To: Xintong Song
Cc: dev , user
Subject: Re: [SURVEY] Remove Mesos support
Thanks for starting this survey Robert! I second
Thanks for starting this survey Robert! I second Konstantin and Xintong in
the sense that our Mesos user's opinions should matter most here. If our
community is no longer using the Mesos integration, then I would be +1 for
removing it in order to decrease the maintenance burden.
Cheers,
Till
On F
+1 for adding a warning about the removal of Mesos support and I would
also propose to state explicitly in the warning the version that we
are planning to actually remove it (e.g. 1.13 or even 1.14 if we feel
it is too aggressive).
This will help as a reminder to users and devs about the upcoming
+1 for adding a warning in 1.12 about planning to remove Mesos support.
With my developer hat on, removing the Mesos support would
definitely reduce the maintaining overhead for the deployment and resource
management related components. On the other hand, the Flink on Mesos users'
voices definite
Hi Robert,
+1 to the plan you outlined. If we were to drop support in Flink 1.13+, we
would still support it in Flink 1.12- with bug fixes for some time so that
users have time to move on.
It would certainly be very interesting to hear from current Flink on Mesos
users, on how they see the evolut
Hi all,
I wanted to discuss if it makes sense to remove support for Mesos in Flink.
It seems that nobody is actively maintaining that component (except for
necessary refactorings because of interfaces we are changing), and there
are almost no users reporting issues or asking for features.
The Apa
22 matches
Mail list logo
