[Geoserver-devel] [JIRA] (GEOS-8613) Add support for priority in control-flow bounded queues

Andrea Aime created an issue

GeoServer / ImprovementGEOS-8613

Add support for priority in control-flow bounded queues

Issue Type:

ImprovementImprovement

Assignee:

Unassigned

Components:

Control-flow

Created:

02/Mar/18 3:16 PM

Priority:

MediumMedium

Reporter:

Andrea Aime

Currently OWS flow controllers block incoming requests to control concurrency.
The wake up from such locks is not controlled, and left to the JVM devices.

Add a way to indicate the priority of a request, and order wake up based on it.
For the initial implementation:

  • Priority would be controlled by a HTTP header (GeoServer cannot be the sole priority controller in a clustered system, some collaboration at the load balancer level might be needed to evenly spread out high priority requests)
  • Priority would be “hard”, no starvation control on lower priority requests, that can be left there to time out in case many higher priority requests come in.

The configuration syntax would be:

ows.priority.http=<header>,<defaultPriority>

Where the header is supposed to contain a numeric value, with the default priority used in case the header is missing. Higher numerical values would lead to higher priority.

Add Comment

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS


This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081-sha1:3770edd)

Atlassian logo