httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: [Bug 62044] shared memory segments are not found in global list, but appear to exist in kernel.
Date Fri, 02 Feb 2018 14:19:59 GMT
To be honest, I don't think we ever envisioned an actual environ
where the config files change every hour and the server gracefully
restarted... I think our working assumptions have been that actual
config file changes are "rare", hence the number of modules that
allow for "on-the-fly" reconfiguration which avoid the need for
restarts.

So this is a nice "edge case"

> On Feb 1, 2018, at 11:49 AM, Mark Blackman <mark@exonetric.com> wrote:
> 
> 
> 
>> On 1 Feb 2018, at 16:27, Yann Ylavic <ylavic.dev@gmail.com> wrote:
>> 
>>> On Thu, Feb 1, 2018 at 5:15 PM, Yann Ylavic <ylavic.dev@gmail.com> wrote:
>>> On Thu, Feb 1, 2018 at 4:32 PM, Mark Blackman <mark@exonetric.com> wrote:>
>>> 
>>>> SHM clean-up is the key here and any patch that doesn’t contribute to
>>>> that has no immediate value for me.
>>> 
>>> What you may want to try is remove "s->defn_line_number" from the id there:
>>> https://github.com/apache/httpd/blob/trunk/modules/proxy/mod_proxy_balancer.c#L787
>>> If your configuration file changes often, that contributes to changing
>>> the name of the SHM...
>> 
>> FWIW, here is (attached) the patch I'm thinking about.
>> <balancer_id-no_line_number.patch>
> 
> Thanks, the configuration changes once an hour or so. Typically, we have about 1000 active
shared memory segments (yes, they are SHMs) attached to the httpd processes.
> 
> For now, we’ll just have to implement a SHM clean-up in the start/stop wrappers until
we can address the root cause or find a cleaner mitigation, which your patch might help with.
> 
> - Mark


Mime
View raw message