Corrects BlockingBuffer's bufferUsage metric and adds capacityUsed metric #3937
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.
Description
This PR has two changes for the
bounded_blocking
buffer:capacityUsed
metric which tracks the capacity used within the buffer as determined by the semaphore which controls admission to the buffer.bufferUsage
metric to track the percentage of the capacity used against the total capacity. This is done by tracking the semaphore. But, it is also logically equivalent to tracking the sum ofrecordsInBuffer
andrecordsInFlight
. Previously, this metric only trackedrecordsInBuffer
.I configured a tight buffer to fill it quickly and test the changes.
The following CloudWatch graphs show the metrics in action.
This graph shows the metrics and how the values correspond to each other correctly.
This is the same graph, but I pinpointed a specific point it time to show the values at that time.
Issues Resolved
Resolves #3936.
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.