1716272 – H2MinWorkers and H2MaxWorkerIdleSeconds do not work

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1716272 - H2MinWorkers and H2MaxWorkerIdleSeconds do not work

Summary: H2MinWorkers and H2MaxWorkerIdleSeconds do not work

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 8
Classification:	Red Hat
Component:	mod_http2
Sub Component:
Version:	8.0
Hardware:	x86_64
OS:	Linux
Priority:	medium
Severity:	medium
Target Milestone:	rc
Target Release:	8.9
Assignee:	Luboš Uhliarik
QA Contact:	rhel-cs-infra-services-qe
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2019-06-03 05:48 UTC by kazuhiro kawana
Modified:	2024-01-20 04:25 UTC (History)
CC List:	4 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-21 20:25:11 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	kwalker: mirror+

Attachments	(Terms of Use)
conf file (1.08 KB, text/plain) 2019-06-03 05:49 UTC, kazuhiro kawana	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-6764	0	None	Migrated	None	2023-09-21 20:25:01 UTC

Description kazuhiro kawana 2019-06-03 05:48:03 UTC

### Description of problem:

It seems that H2MinWorkers and H2MaxWorkerIdleSeconds do not work.
And it looks to me that the following commit changed the behavior:

trunk: https://github.com/apache/httpd/commit/e78889fcb6599e2c353f4bcfeb44aa9c598794a7
2.4.x: https://github.com/apache/httpd/commit/2f8392ad9d821109e941773712bcf8e54ba0a3ce

CHANGES log says "There are H2MaxWorkers threads created at start and the number is kept constant for now". 
So, the number of threads is always fixed (created at start-up and never reclaimed). It looks the behavior is changed intentionally for better performance. 

~~~
  *) mod_http2: h2 workers with improved scalability for better scheduling
     performance. There are H2MaxWorkers threads created at start and the
     number is kept constant for now. [Stefan Eissing]
~~~

### Version-Release number of selected component (if applicable):

httpd-2.4.37-11.module+el8.0.0+2969+90015743.x86_64


### How reproducible:

anytime


### Steps to Reproduce:
1: yum install httpd-2.4.37-11.module+el8.0.0+2969+90015743.x86_64

2: vim /etc/httpd/conf/httpd.conf (Please see attachement for details)

#cat httpd.conf
Protocols h2 h2c http/1.1

StartServers 1
MinSpareThreads 1
MaxSpareThreads 1
ThreadLimit 1
ThreadsPerChild 1
MaxRequestWorkers 1
MaxConnectionsPerChild 0

H2MaxWorkerIdleSeconds 10

H2MaxWorkers 10
H2MinWorkers 2
....snip....

3:systemctl start httpd


### Actual results:
Even if 10 seconds(=H2MaxWorkerIdleSeconds) or more passes, it does not become H2MinWorkers value.

# ps auxww -L | grep -e mysqld -e httpd -e NLWP | grep -v grep
USER       PID   LWP %CPU NLWP %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      5936  5936  0.8    1  0.3  96192  6656 ?        Ss   10:35   0:00 /usr/sbin/httpd -DFOREGROUND
apache    5938  5938  0.0    8  0.2 305560  4912 ?        Sl   10:35   0:00 /usr/sbin/httpd -DFOREGROUND
apache    5938  5939  0.0    8  0.2 305560  4912 ?        Sl   10:35   0:00 /usr/sbin/httpd -DFOREGROUND
apache    5938  5940  0.0    8  0.2 305560  4912 ?        Sl   10:35   0:00 /usr/sbin/httpd -DFOREGROUND
apache    5938  5941  0.0    8  0.2 305560  4912 ?        Sl   10:35   0:00 /usr/sbin/httpd -DFOREGROUND
apache    5938  5942  0.0    8  0.2 305560  4912 ?        Sl   10:35   0:00 /usr/sbin/httpd -DFOREGROUND
apache    5938  5943  0.0    8  0.2 305560  4912 ?        Sl   10:35   0:00 /usr/sbin/httpd -DFOREGROUND
apache    5938  5945  0.0    8  0.2 305560  4912 ?        Sl   10:35   0:00 /usr/sbin/httpd -DFOREGROUND
apache    5938  5946  0.0    8  0.2 305560  4912 ?        Sl   10:35   0:00 /usr/sbin/httpd -DFOREGROUND

# pstack 5938
Thread 8 (Thread 0x7fd285381700 (LWP 5946)):
#0  0x00007fd28dd73d97 in epoll_wait () from target:/lib64/libc.so.6
#1  0x00007fd28e48672a in impl_pollset_poll () from target:/lib64/libapr-1.so.0
#2  0x00007fd28c199592 in listener_thread () from target:/etc/httpd/modules/mod_mpm_event.so
#3  0x00007fd28e2472de in start_thread () from target:/lib64/libpthread.so.0
#4  0x00007fd28dd73a63 in clone () from target:/lib64/libc.so.6
Thread 7 (Thread 0x7fd285b82700 (LWP 5945)):
#0  0x00007fd28e24d48c in pthread_cond_wait@@GLIBC_2.3.2 () from target:/lib64/libpthread.so.0
#1  0x00005576b1e544bd in ap_queue_pop_something ()
#2  0x00007fd28c19900a in worker_thread () from target:/etc/httpd/modules/mod_mpm_event.so
#3  0x00007fd28e2472de in start_thread () from target:/lib64/libpthread.so.0
#4  0x00007fd28dd73a63 in clone () from target:/lib64/libc.so.6
Thread 6 (Thread 0x7fd286b84700 (LWP 5943)):
#0  0x00007fd28e24d48c in pthread_cond_wait@@GLIBC_2.3.2 () from target:/lib64/libpthread.so.0
#1  0x00007fd28b96fb52 in slot_run () from target:/etc/httpd/modules/mod_http2.so
#2  0x00007fd28e2472de in start_thread () from target:/lib64/libpthread.so.0
#3  0x00007fd28dd73a63 in clone () from target:/lib64/libc.so.6
Thread 5 (Thread 0x7fd287385700 (LWP 5942)):
#0  0x00007fd28e24d48c in pthread_cond_wait@@GLIBC_2.3.2 () from target:/lib64/libpthread.so.0
#1  0x00007fd28b96fb52 in slot_run () from target:/etc/httpd/modules/mod_http2.so
#2  0x00007fd28e2472de in start_thread () from target:/lib64/libpthread.so.0
#3  0x00007fd28dd73a63 in clone () from target:/lib64/libc.so.6
Thread 4 (Thread 0x7fd287b86700 (LWP 5941)):
#0  0x00007fd28e24d48c in pthread_cond_wait@@GLIBC_2.3.2 () from target:/lib64/libpthread.so.0
#1  0x00007fd28b96fb52 in slot_run () from target:/etc/httpd/modules/mod_http2.so
#2  0x00007fd28e2472de in start_thread () from target:/lib64/libpthread.so.0
#3  0x00007fd28dd73a63 in clone () from target:/lib64/libc.so.6
Thread 3 (Thread 0x7fd288387700 (LWP 5940)):
#0  0x00007fd28e24d48c in pthread_cond_wait@@GLIBC_2.3.2 () from target:/lib64/libpthread.so.0
#1  0x00007fd28b96fb52 in slot_run () from target:/etc/httpd/modules/mod_http2.so
#2  0x00007fd28e2472de in start_thread () from target:/lib64/libpthread.so.0
#3  0x00007fd28dd73a63 in clone () from target:/lib64/libc.so.6
Thread 2 (Thread 0x7fd288b88700 (LWP 5939)):
#0  0x00007fd28e24d48c in pthread_cond_wait@@GLIBC_2.3.2 () from target:/lib64/libpthread.so.0
#1  0x00007fd28b96fb52 in slot_run () from target:/etc/httpd/modules/mod_http2.so
#2  0x00007fd28e2472de in start_thread () from target:/lib64/libpthread.so.0
#3  0x00007fd28dd73a63 in clone () from target:/lib64/libc.so.6
Thread 1 (Thread 0x7fd28f66d900 (LWP 5938)):
#0  0x00007fd28e250b44 in read () from target:/lib64/libpthread.so.0
#1  0x00005576b1e5364b in ap_mpm_podx_check ()
#2  0x00007fd28c1968f7 in child_main () from target:/etc/httpd/modules/mod_mpm_event.so
#3  0x00007fd28c196c2a in make_child () from target:/etc/httpd/modules/mod_mpm_event.so
#4  0x00007fd28c196cbb in startup_children () from target:/etc/httpd/modules/mod_mpm_event.so
#5  0x00007fd28c1979af in event_run () from target:/etc/httpd/modules/mod_mpm_event.so
#6  0x00005576b1e27c8e in ap_run_mpm ()
#7  0x00005576b1e20383 in main ()


### Expected results:
 If this change is permanent (= design change = document bug), please correct the content of the document. 

or

If this change is temporal (= H2MaxWorkerIdleSeconds and H2MinWorkers will be reimplemented in the future release), please change to be functional

Comment 1 kazuhiro kawana 2019-06-03 05:49:58 UTC

Created attachment 1576485 [details]
conf file

Comment 4 RHEL Program Management 2023-09-21 20:12:14 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-09-21 20:25:11 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 6 Red Hat Bugzilla 2024-01-20 04:25:03 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days

Note You need to log in before you can comment on or make changes to this bug.