Hi.

Am 10-08-2018 17:12, schrieb Willy Tarreau:
On Fri, Aug 10, 2018 at 09:54:38AM -0400, Patrick Hemmer wrote:
Merge it!

Now done!

Quite happy to see this done with. Any issues can be addressed as bug fixes.

Yes, same here. I've updated the ROADMAP file to remove this 8-years
old entry :-)

Great ;-)

As we now have this feature, Patrick do you plan to create a blog post or a example config for this new feature?

Sorry to say this but I haven't understand this feature fully.

I was going through the discussion and there are some mentions about time based and a example with date.

I have found some informations about "load balancer priority based" but I'm not sure if this matches the implementation in haproxy.

https://docs.citrix.com/en-us/netscaler/12-1/priority-load-balancing.html
https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-basics-12-1-0/4.html#unique_260681479
https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-routing-methods#priority

Let me explain how I understand this feature and you can fix my gabs for this feature.

I think it is a requeue mechanism for the connection and not a selector for a server or a backend, but I can be wrong.

###

listen|frontend test001
  bind :8080
  # some other options
  http-request set-priority-class -10s if PAY_BUTTON
  http-request set-priority-offset 5s if LOGO
  http-request set-priority-offset 5s if LOGO

  # as a sample expression can also be this, right?
  http-request set-priority-class \
    %[req.fhdr(User-Agent),51d.single(DeviceType,IsMobile,IsTablet)]

  # could this work ?
  use_backend high_priority if priority-class > 5
###

The set-priority-offset is for separate the *same* classes in more pieces right.

request 500 -> class -4 -> set-priority-offset 0
request 600 -> class -4 -> offset -3

request 600 will be delivered before 500 right?


I'm also willing to write such a blog post as soon as I have understood the feature ;-), similar to spoe feature.
https://www.me2digital.com/blog/2017/02/15-haproxy-1-7-feature-spoe/


Thanks!
Willy

Best regards
Aleks

Reply via email to