Avoid trace span buffer becoming too large #39609
Open
+14
−0
Conversation
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
Signed-off-by: 白泽 <[email protected]>
Patrick0308
force-pushed
the
fix-opentelemetry-buffer-too-big
branch
from
adfbd33 to
d4e3790
Compare
Signed-off-by: 白泽 <[email protected]>
|
@yanavlasov @wbpcode PTAL |
Signed-off-by: 白泽 <[email protected]>
mattklein123
requested changes
May 27, 2025
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.
Commit Message: Avoid trace span buffer becoming too large
Additional Description:
See istio/istio#55439 (comment) , the sidecar space-inuse flame graph shows sometimes span serialize message grow too large, maybe it's caused by sending span to remote server is too slow. We should avoid this memory growing.
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features: