Re: Surfacing additional issues on agent host to schedulers

Hi Avinash, Sorry for the slow response. On Wed, Feb 21, 2018 at 11:50 AM, Avinash Sridharan wrote: > On Wed, Feb 21, 2018 at 11:18 AM, Zhitao Li wrote: > > > Hi Avinash, > > > > We use haproxy of all outgoing traffic. For example, if instance of

Re: Surfacing additional issues on agent host to schedulers

On Wed, Feb 21, 2018 at 11:18 AM, Zhitao Li wrote: > Hi Avinash, > > We use haproxy of all outgoing traffic. For example, if instance of service > A wants to talk to service B, what it does is actually call a > "localhost:" backed by the local haproxy instance, which then

Re: Surfacing additional issues on agent host to schedulers

Hi Avinash, We use haproxy of all outgoing traffic. For example, if instance of service A wants to talk to service B, what it does is actually call a "localhost:" backed by the local haproxy instance, which then forwards the request to some instance of service B. In such a situation, if local

Re: Surfacing additional issues on agent host to schedulers

Hi James, The "condition" list you described fits our modeling pretty well, although I don't know whether the eviction is made by a scheduler or the local kubelet proxy. Do you know whether the conditions can be extended and operator can define additional conditions which is not in the provided

Re: Surfacing additional issues on agent host to schedulers

On Tue, Feb 20, 2018 at 3:54 PM, James Peach wrote: > > > On Feb 20, 2018, at 11:11 AM, Zhitao Li wrote: > > > > Hi, > > > > In one of recent Mesos meet up, quite a couple of cluster operators had > > expressed complaints that it is hard to model host

Re: Surfacing additional issues on agent host to schedulers

> On Feb 20, 2018, at 11:11 AM, Zhitao Li wrote: > > Hi, > > In one of recent Mesos meet up, quite a couple of cluster operators had > expressed complaints that it is hard to model host issues with Mesos at the > moment. > > For example, in our environment, the only

Surfacing additional issues on agent host to schedulers

Hi, In one of recent Mesos meet up, quite a couple of cluster operators had expressed complaints that it is hard to model host issues with Mesos at the moment. For example, in our environment, the only signal scheduler would know is whether Mesos agent has disconnected from the cluster. However,