[
https://issues.apache.org/jira/browse/AURORA-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507123#comment-15507123
]
Kai Huang commented on AURORA-1224:
-----------------------------------
I would propose making the following changes to the client:
1. Add min_consecutive_health_checks to HealthCheckConfig struct. (Default = 1)
2. Add the following constraint:
initial_interval_secs >= interval_secs * min_consecutive_health_checks
3. Remove the client constraint:
watch_secs >= initial_interval_secs + (max_consecutive_failures *
interval_secs)
4. Add a new constraint(OPTIONAL):
If watch_secs is 0, the Health Check should be enabled (either by providing
a "health" port or a ShellHealthChecker). Otherwise the instance will always
marked as healthy.
> Add a new "min_consecutive_health_checks" setting in .aurora config
> -------------------------------------------------------------------
>
> Key: AURORA-1224
> URL: https://issues.apache.org/jira/browse/AURORA-1224
> Project: Aurora
> Issue Type: Task
> Components: Client, Scheduler
> Reporter: Maxim Khutornenko
> Assignee: Kai Huang
>
> HealthCheckConfig should accept a new configuration value that will tell how
> many positive consecutive health checks an instance requires to move from
> STARTING to RUNNING.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
