Re: Welcome Meng Zhu as PMC member and committer!
Congrats, Meng! On Mon, Nov 5, 2018 at 9:54 AM Benno Evers wrote: > Congratulations, Meng! > > On Thu, Nov 1, 2018 at 9:54 AM Yan Xu wrote: > >> Congratulations! >> >> >> On Wed, Oct 31, 2018 at 4:50 PM Vinod Kone wrote: >> >>> Congrats Meng! >>> >>> Thanks, >>> Vinod >>> >>> > On Oct 31, 2018, at 4:26 PM, Gilbert Song >>> wrote: >>> > >>> > Well deserved, Meng! >>> > >>> >> On Wed, Oct 31, 2018 at 2:36 PM Benjamin Mahler >>> wrote: >>> >> Please join me in welcoming Meng Zhu as a PMC member and committer! >>> >> >>> >> Meng has been active in the project for almost a year and has been >>> very productive and collaborative. He is now one of the few people of >>> understands the allocator code well, as well as the roadmap for this area >>> of the project. He has also found and fixed bugs, and helped users in slack. >>> >> >>> >> Thanks for all your work so far Meng, I'm looking forward to more of >>> your contributions in the project. >>> >> >>> >> Ben >>> >> > > -- > Benno Evers > Software Engineer, Mesosphere >
Re: [API WG] Proposals for dealing with master subscriber leaks.
>- We can add heartbeats to the SUBSCRIBE call. > This would need to be > part of a separate operator Call, because one platform (browsers) that > might subscribe to the master does not support two-way streaming. This doesn't make sense to me, the heartbeats should still be part of the same connection (request and response are infinite and heartbeating) by default. Splitting into a separate call is messy and shouldn't be what we force everyone to do, it should only be done in cases that it's impossible to use a single connection (e.g. browsers). On Sat, Nov 10, 2018 at 12:03 AM Joseph Wu wrote: > Hi all, > > During some internal scale testing, we noticed that, when Mesos streaming > endpoints are accessed via certain proxies (or load balancers), the proxies > might not close connections after they are complete. For the Mesos master, > which only has the /api/v1 SUBSCRIBE streaming endpoint, this can generate > unnecessary authorization requests and affects performance. > > We are considering a few potential solutions: > >- We can add heartbeats to the SUBSCRIBE call. This would need to be >part of a separate operator Call, because one platform (browsers) that >might subscribe to the master does not support two-way streaming. >- We can add (optional) arguments to the SUBSCRIBE call, which tells the >master to disconnect it after a while. And the client would have to > remake >the connection every so often. >- We can change the master to hold subscribers in a circular buffer, and >disconnect the oldest ones if there are too many connections. > > We're tracking progress on this issue here: > https://issues.apache.org/jira/browse/MESOS-9258 > Some prototypes of the code changes involved are also linked in the JIRA. > > Please chime in if you have any suggestions or if any of these options > would be undesirable/bad, > ~Joseph >
