Only add to cache if log stream is created #1569
Merged
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.
Same change as #1566
Description of the issue
If there are multiple instances of the CloudWatch agent that are trying to create the same log group, there are cases where streams within those log groups will not be created because
CreateLogGroup
returnsResourceAlreadyExists
.amazon-cloudwatch-agent/plugins/outputs/cloudwatchlogs/internal/pusher/target.go
Line 72 in af960d7
Description of changes
Resource already exists shouldn't be considered a failure to create the resource. Only add the target to the cache if the log stream was created or already exists.
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Added more unit test cases to cover the issue. Added checks for cache sizes after each test.
Added tests run before changes
Requirements
Before commit the code, please do the following steps.
make fmt
andmake fmt-sh
make lint