Make ingress buffer parameters configurable #604
Closed
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
cf-foundation-community-automation
bot
moved this to Inbox
in Application Runtime Platform Working Group
chombium
force-pushed
the
ingress-diode-size-config
branch
from
2cdfab9 to
9703363
Compare
Contributor
Author
|
Thanks for the review @ZPascal. Hi @ameowlia! It looks like we've got stuck. I've opened the PR, @ZPascal has reviewed it, but he's not in the logging and metrics approver team. I cannot approve and merge the PR as I've opened it and I'm not the owner of the repo so that I can change the behavior. We need some help. Maybe @mkocher would be kind enough to approve the PR... |
This change exposes the ingress buffer configuration parameters to the outside world. Sometimes, depending on the scaling of Log Cache, the number of sources (CF applications and platform components) and the log load, ingress drops may occur when Log Cache nodes send items between each other. The Log Cache `ingress_dropped` metric should be monitored, to make sure that there are no drops. For such cases, the following three parameters can be adjusted until the log loss is gone. - Ingress Buffer Size - The ingress buffer (diode) size in number of items used when LogCache nodes send items between each other. The default size is 10000. Can be increased when ingress drops occur. - Ingress Buffer Read Batch Size - The ingress buffer read batch size in number of items. The size of the ingress buffer read batch used when LogCache nodes send items between each other. The default size is 100. Can be increased when ingress drops occur. - Ingress Buffer Read Batch Interval - The ingress buffer read interval in milliseconds. The default value is 250. Can be increased when ingress drops occur.
chombium
force-pushed
the
ingress-diode-size-config
branch
from
9703363 to
96b3555
Compare
Contributor
Author
|
Closing this in favor of #605 |
github-project-automation
bot
moved this from Inbox
to Done
in Application Runtime Platform Working Group
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change exposes the ingress buffer configuration parameters to the outside world.
Sometimes, depending on the scaling of Log Cache, the number of sources (CF applications and platform components) and the log load, ingress drops may occur when Log Cache nodes send items between each other. The Log Cache
ingress_droppedmetric should be monitored, to make sure that there are no drops. For such cases, the following three parameters can be adjusted until the log loss is gone.Type of change
Testing performed?
Checklist:
mainbranch, or relevant version branchIf you have any questions, or want to get attention for a PR or issue please reach out on the #logging-and-metrics channel in the cloudfoundry slack