bug: diable haproxy zero copy forwarding #214
Merged
Conversation
This file contains 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
laverya
previously approved these changes
Jan 8, 2024
haproxy version 2.9.1 is consuming > 100% of cpu. the problem does not happen in older versions. this commit disables the zero copy forwarding as per workaround here: haproxy/haproxy#2402 (comment) we may want to enable this back in once it is fixed upstream.
ricardomaraschini
force-pushed
the
disable-zero-copy-forwarding
branch
from
0893011 to
ec41340
Compare
laverya
approved these changes
Jan 8, 2024
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.
haproxy version 2.9.1 is consuming > 100% of cpu. the problem does not happen in older versions. this commit disables the zero copy forwarding as per workaround here:
haproxy/haproxy#2402 (comment)
we may want to enable this back in once it is fixed upstream.