[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-721) Setting smax results in very small max connection pool on mod_cluster

Jean-Frederic Clere (Jira) issues at jboss.org
Thu Apr 23 04:50:00 EDT 2020


     [ https://issues.redhat.com/browse/MODCLUSTER-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Frederic Clere updated MODCLUSTER-721:
-------------------------------------------
              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/modcluster/mod_proxy_cluster/pull/27


> Setting smax results in very small max connection pool on mod_cluster
> ---------------------------------------------------------------------
>
>                 Key: MODCLUSTER-721
>                 URL: https://issues.redhat.com/browse/MODCLUSTER-721
>             Project: mod_cluster
>          Issue Type: Bug
>          Components: Native (httpd modules)
>    Affects Versions: 1.3.13.Final
>            Reporter: Aaron Ogburn
>            Assignee: Jean-Frederic Clere
>            Priority: Major
>
> mod_clusters connection pool is sized differently in httpd 2.4 now compared to httpd 2.2.  If smax is set, mod_cluster now sets that pool max to smax+1:
> {code}
>         if (worker->s->hmax < node->mess.smax)
>             worker->s->hmax = node->mess.smax + 1;
> {code}
> Before the max would be ThreadsPerChild+1.  Now if someone sets smax=1, then they start seeing severe responsiveness issues if moving an equivalent config from httpd 2.2 to httpd 2.4 because it fails to acquire a connection with 3 concurrent requests:
> {code}
> [Tue Apr 21 10:02:08.995604 2020] [proxy:debug] [pid 27148:tid 139854005438432] proxy_util.c(1981): AH00927: initializing worker http://127.0.0.1:8080 local
> [Tue Apr 21 10:02:08.995616 2020] [proxy:debug] [pid 27148:tid 139854005438432] proxy_util.c(2016): AH00930: initialized pool in child 27148 for () min=0 max=2 smax=1
> ...
> [Tue Apr 21 10:20:41.123443 2020] [:debug] [pid 27147:tid 139853093992192] mod_proxy_cluster.c(2479): proxy: byrequests balancer DONE (http:///127.0.0.1:8080)
> [Tue Apr 21 10:20:41.123456 2020] [proxy:debug] [pid 27147:tid 139853093992192] proxy_util.c(1919): AH00924: worker http:///127.0.0.1:8080 shared already initialized
> [Tue Apr 21 10:20:41.123460 2020] [proxy:debug] [pid 27147:tid 139853093992192] proxy_util.c(1976): AH00926: worker http:///127.0.0.1:8080 local already initialized
> [Tue Apr 21 10:20:41.123464 2020] [proxy:debug] [pid 27147:tid 139853093992192] mod_proxy.c(1254): [client 127.0.0.1:40760] AH01143: Running scheme balancer handler (attempt 0)
> [Tue Apr 21 10:20:41.125726 2020] [proxy:error] [pid 27147:tid 139853093992192] (70007)The timeout specified has expired: AH00941: HTTP: failed to acquire connection for ()
> {code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the mod_cluster-issues mailing list