Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Health check fwd_host #4

Open
rgamba opened this issue Sep 29, 2017 · 0 comments
Open

Health check fwd_host #4

rgamba opened this issue Sep 29, 2017 · 0 comments

Comments

@rgamba
Copy link
Owner

rgamba commented Sep 29, 2017

Health check the fwd host. Add the following parameters to the config file:

[http.forward]
host = "" # fwd_host instead of fwd_host

[http.forward.health_check]
interval = 5 # Interval in seconds
url = "/" # Relative to host
threshold = 3 # Consecutive healthy/unhealthy checks to flag the host as active/inactive
max_execution_time = 5 # Above this response time (in seconds), we'll consider it a failed check

If an instance is unhealthy, we need to either:

  1. Stop consuming new messages from the service request queue, or
  2. When a new request gets routed our way, we'll:
    IF the AMQP header unhealthy_count exists and it is >= 3, THEN we'll return a no_available_instances error to the response_queue
    ELSE, create or increment the unhealthy_count AMQP header by 1 and put the message back in the request queue so other instances can process it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant