Hi.
Have anyone seen this project?
https://github.com/jiangwenyuan/nuster
It's a high-performance HTTP proxy cache server and RESTful NoSQL cache server
based on HAProxy.
The HAProxy version in use is 1.9.
Regards
Alex
Hello everyone,
I am running HAProxy v2.0.9 on Ubuntu using the dedicated PPA
(ppa:vbernat/haproxy-2.0). There seems to be a behavior change for a specific
endpoint between HTX enabled and HTX disabled, but I have not been able to
pin-point the exact root cause.
With HTX disabled (`no option
On Thu, Nov 21, 2019 at 05:18:58PM +0100, Willy Tarreau wrote:
> On Thu, Nov 21, 2019 at 02:12:09PM +0100, Baptiste wrote:
> > Hi there,
> >
> > Since a short term reliable solution can't be found, we can apply this
> > patch as a workaround.
>
> Yep, as discussed on the github issue I think it
On Thu, Nov 21, 2019 at 02:12:09PM +0100, Baptiste wrote:
> Hi there,
>
> Since a short term reliable solution can't be found, we can apply this
> patch as a workaround.
Yep, as discussed on the github issue I think it remains the most
reasonable short-term approach.
Thanks,
Willy
On 2019-11-20 11:05, William Lallemand wrote:
On Wed, Nov 20, 2019 at 10:19:20AM +0100, Christian Ruppert wrote:
Hi William,
thanks for the patch. I'll test it later today. What I actually
wanted to
achieve is:
https://cbonte.github.io/haproxy-dconv/2.0/management.html#4 Then
HAProxy tries
Hi Christopher,
On Tue, Nov 19, 2019 at 04:35:47PM +0100, Christopher Faulet wrote:
> +/* Parse the query stirng of request URI to filter the metrics. It returns 1
> on
> + * success and -1 on error. */
> +static int promex_parse_uri(struct appctx *appctx, struct stream_interface
> *si)
> +{
>
Hi there,
Since a short term reliable solution can't be found, we can apply this
patch as a workaround.
Baptiste
>
Am 21.11.2019 um 11:23 schrieb Christian Ruppert:
Hi Aleks,
On 2019-11-21 11:01, Aleksandar Lazic wrote:
Hi.
Am 21.11.2019 um 10:49 schrieb Christian Ruppert:
Hi list,
for an old exchange cluster I have some check listener like:
listen chk_s015023
[snipp]
The new healthcheck is marked as
чт, 21 нояб. 2019 г. в 15:18, William Dauchy :
> On Thu, Nov 21, 2019 at 03:09:30PM +0500, Илья Шипицин wrote:
> > I understand. However, those patches add complexity (which might be moved
> > to another dedicated tool)
>
> those patch makes sense for heavy haproxy instances. As you might have
>
Hi Aleks,
On 2019-11-21 11:01, Aleksandar Lazic wrote:
Hi.
Am 21.11.2019 um 10:49 schrieb Christian Ruppert:
Hi list,
for an old exchange cluster I have some check listener like:
listen chk_s015023
bind 0.0.0.0:1001
mode http
monitor-uri /check
On Thu, Nov 21, 2019 at 03:09:30PM +0500, Илья Шипицин wrote:
> I understand. However, those patches add complexity (which might be moved
> to another dedicated tool)
those patch makes sense for heavy haproxy instances. As you might have
seen above, we are talking about > 130MB of data. So for a
чт, 21 нояб. 2019 г. в 15:07, William Dauchy :
> On Thu, Nov 21, 2019 at 03:00:02PM +0500, Илья Шипицин wrote:
> > is it common thing in Prometheus world to perform cascade export ? like
> > "exporter" --> "filter out" --> "aggregate" --> "deliver to prometheus"
> > in order to keep things simple
On Thu, Nov 21, 2019 at 03:00:02PM +0500, Илья Шипицин wrote:
> is it common thing in Prometheus world to perform cascade export ? like
> "exporter" --> "filter out" --> "aggregate" --> "deliver to prometheus"
> in order to keep things simple and not to push everything into single tool
no, the
Hi.
Am 21.11.2019 um 10:49 schrieb Christian Ruppert:
Hi list,
for an old exchange cluster I have some check listener like:
listen chk_s015023
bind 0.0.0.0:1001
mode http
monitor-uri /check
tcp-request connection reject if { nbsrv lt 6 } { src LOCALHOST }
btw, side question...
is it common thing in Prometheus world to perform cascade export ? like
"exporter" --> "filter out" --> "aggregate" --> "deliver to prometheus"
in order to keep things simple and not to push everything into single tool
чт, 21 нояб. 2019 г. в 14:49, Christopher Faulet :
>
Hi list,
for an old exchange cluster I have some check listener like:
listen chk_s015023
bind 0.0.0.0:1001
mode http
monitor-uri /check
tcp-request connection reject if { nbsrv lt 6 } { src LOCALHOST
}
monitor fail if { nbsrv lt 6 }
Le 20/11/2019 à 21:23, William Dauchy a écrit :
Hi Christopher,
On Wed, Nov 20, 2019 at 02:56:28PM +0100, Christopher Faulet wrote:
Nice, Thanks for your feedback. It is merged now. And I'm on the backports
for the 2.0.
You apparently forgot to backport
commit 0d1c2a65e8370a770d01 (MINOR:
Hello,
On Wed, Nov 20, 2019 at 9:51 AM Alexander Kasantsev wrote:
>
> Good day everyone!
>
> I’m migrated from haproxy 1.5 to 1.7.11 and I have some troubles with logging
>
> I have a following in config file for logging
>
> capture request header Host len 200
> capture request header
Am 21.11.2019 um 08:09 schrieb Alexander Kasantsev:
I updated haproxy to 1.7.12 but nothing changed
Okay that's bad, because I thought this commit will fix your issue.
http://git.haproxy.org/?p=haproxy-1.7.git;a=commit;h=777a0aa4c8a704e06d653aed5f00e6cda2017a4d
Regards
Aleks
20 нояб. 2019
19 matches
Mail list logo
