te orthogonal to the health checking idea. I would be in favor of
>>> separating the different concepts. I even thought about this yesterday,
>>> because in our environment we only want health checking but now also have
>>> to pay a price of 10secs additional latency wh
b/master/include/mesos/mesos.proto#L141
>>
>>
>> Regards,
>> Stephan
>>
>>
>> From: Florian Pfeiffer
>> Sent: Saturday, February 21, 2015 4:27 AM
>> To: dev@aurora.incubator.apache.org
>> Subject: R
egards,
> Stephan
>
>
> From: Florian Pfeiffer
> Sent: Saturday, February 21, 2015 4:27 AM
> To: dev@aurora.incubator.apache.org
> Subject: RFC HealthCheck
>
> Hi,
>
> I would like to start working on the Healthchecker
>
ceful kill escalation.
[1] https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L141
Regards,
Stephan
From: Florian Pfeiffer
Sent: Saturday, February 21, 2015 4:27 AM
To: dev@aurora.incubator.apache.org
Subject: RFC HealthCheck
Hi,
I
Hi,
I would like to start working on the Healthchecker
1) Enable configuration of the portname to which run health checks on (this
should also tackle AURORA-321 )
This seems like a very small change consisting of adding a new variable named
„port“ to the HealthCheckConfig in base.py with a def
