Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

server /status endpoint not closing connection

Description

The server /status health-check endpoint is not closing the connection. Closing the connection is a requirement for the Google Compute load balancer health-checks (https://cloud.google.com/compute/docs/load-balancing/health-checks#overview), and likely others. My understanding is that this endpoint is built on top of netty-http. Can netty-http be configured to not to keep-alive this connection?

sample tcpdump snippet for an instance behind a google loadbalancer attached, showing continual connection resets

Release Notes

None

Attachments

1

Activity

Show:

Chris Gianelloni January 15, 2015 at 11:01 PM

This prevents Coopr Server from being directly load-balanced in Google. Instead, we have to run Apache HTTPd in front of the services, increasing complexity and potential for breakage. This also prevents other load balancing, such as F5 LTM health checks.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

Created November 24, 2014 at 7:36 PM
Updated January 27, 2015 at 9:33 PM
Resolved January 22, 2015 at 12:20 AM
Configure