Re: [API WG] Proposals for dealing with master subscriber leaks.

2018-11-21 Thread Greg Mann
Thanks for the proposal Joseph! I think I'm also leaning toward the circular buffer approach. The one real concern there seems to be the potential for "DDoS"-type scenarios when users hit the subscriber limit using clients which have retry logic. Providing a metric for the number of currently

Re: [API WG] Proposals for dealing with master subscriber leaks.

2018-11-11 Thread Benjamin Mahler
>- 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

[API WG] Proposals for dealing with master subscriber leaks.

2018-11-09 Thread Joseph Wu
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