Fix for https://issues.redhat.com/browse/MODCLUSTER-852.#873
Merged
jajik merged 1 commit intomodcluster:1.3.xfrom Feb 14, 2025
Merged
Fix for https://issues.redhat.com/browse/MODCLUSTER-852.#873jajik merged 1 commit intomodcluster:1.3.xfrom
jajik merged 1 commit intomodcluster:1.3.xfrom
Conversation
jajik
reviewed
Feb 13, 2025
Member
jajik
left a comment
There was a problem hiding this comment.
Upstream should go first, but that's not an issue as big as failing ci. But it doesn't look like your fault. I'll check it out.
Member
That's correct, though the order of opening doesn't matter, the order of merging is the crucial one. Thanks for policing ;-) |
Member
|
CI failure is caused by httpd. Hopefully it will be fixed soon. |
This was referenced Feb 13, 2025
Member
|
httpd is fixed, pipeline looks fine now. We need to merge the upstream PR first and then we can go with this one. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix for https://issues.redhat.com/browse/MODCLUSTER-852.
Changes in httpd-2.4.59 are causing the sockets to stop being reused, that results in many sockets in TIME_WAIT and on windows when doing a load tests to get "All workers are in error state" due to:
(OS 10048) Only one usage of each socket address (protocol/network address/port) is normally permitted.
because the OS runs out of sockets.
Note that increasing the number of socket in the OS helps to some extend:
netsh int ipv4 set dynamicport tcp start=9000 num=25000
netsh int ipv6 set dynamicport tcp start=9000 num=25000
Note the same fix is need in mod_proxy_cluster upstream.