← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1260406] [NEW] allow disable wsgi keepalive

 

Public bug reported:

The wsgi server used in most if not  all openstack services currently
has keepalive=True by default thus keeping connections open after each
request. This can cause problems when using load balancers in front of
these services e.g. connections for requests that take a long time can
get closed in the load balancers once a timeout has expired. This can
then cause issues if a client performs a request using the same source
port as a previous request that is not closed in the LB but still open
in the server due to TCP packet sequecing in the LB and the new client
not expecting the connection to already be open. So, it would be useful
to be able to disable wsgi keepalive.

** Affects: keystone
     Importance: Undecided
     Assignee: Edward Hope-Morley (hopem)
         Status: In Progress

** Changed in: keystone
     Assignee: (unassigned) => Edward Hope-Morley (hopem)

** Changed in: keystone
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1260406

Title:
  allow disable wsgi keepalive

Status in OpenStack Identity (Keystone):
  In Progress

Bug description:
  The wsgi server used in most if not  all openstack services currently
  has keepalive=True by default thus keeping connections open after each
  request. This can cause problems when using load balancers in front of
  these services e.g. connections for requests that take a long time can
  get closed in the load balancers once a timeout has expired. This can
  then cause issues if a client performs a request using the same source
  port as a previous request that is not closed in the LB but still open
  in the server due to TCP packet sequecing in the LB and the new client
  not expecting the connection to already be open. So, it would be
  useful to be able to disable wsgi keepalive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1260406/+subscriptions


Follow ups

References