On Tue, Sep 18, 2018 at 08:12:20AM -0400, Thomas Ward wrote:
> Downstream in Ubuntu, it has been proposed to demote pcre3 and
> use pcre2 instead as it is newer.
> https://trac.nginx.org/nginx/ticket/720 shows it was marked 4
> years ago that NGINX does not support pcre2. Are there any
> plans to use pcre2 instead of pcre3?
There are no immediate plans.
When we last checked, there were no problems with PCRE, but PCRE2
wasn't available in most distributions we support, making the
switch mostly meaningless.
Also, it looks like PCRE2 is still not supported even by Exim,
which is the parent project of PCRE and PCRE2:
As such, adding PCRE2 support to nginx looks premature.
This patch applies cache locking behaviour to stale cache entries, so
in the case where the *_cache_lock directives are used, the same
locking behaviour is used for stale content as it is for new entries.
Previously, this was only done for new cache entries.
This is useful when serving stale content is not permissable but sending
many requests upstream is undesriable.
This patch exposes the ngx_http_file_cache_lock function; this function
is then called in ngx_http_upstream if a cache entry has expired.
I have attached two versions of this patch, a "minimal" one that avoids
changes where not strictly necessary, and a "cleaner" version which is
more invasive but (in my opinion) cleaner.
Both patches cause no (additional) failures in the nginx test suite.
I tested with as many modules as I could reasonably enable.
Additionally, a colleague will add tests for this new behaviour in a
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
Hit a rather strange issue today on a production service where during a
configuration reload (evident by the worker processes in the process of
being shutdown). During this reload a percentage of connections were not
getting accepted (and hence not processed). I was able to confirm that none
of the processes were accepting the connections.
Our configuration includes the reuseport option so my theory was that for
some reason connections were still being routed to the shutting down
worker, which was not accepting new connections.
This has a striking resemblance to the HAProxy issues in previous years
with connections received during live configuration reloads.
nginx version: nginx/1.15.8
linux kernel: 4.9.2
Does anyone have an idea of where to look for this issue? Or have you see
anything like it before?
I am aware the kernel is a bit on the older side, anyone seen any relevant
issues / patches?