Skip to content

[23.0 backport] awslogs: fix non-blocking log drop bug#45350

Merged
thaJeztah merged 1 commit into
moby:23.0from
PettitWesley:awslogs-non-blocking-bug-23.0
Apr 19, 2023
Merged

[23.0 backport] awslogs: fix non-blocking log drop bug#45350
thaJeztah merged 1 commit into
moby:23.0from
PettitWesley:awslogs-non-blocking-bug-23.0

Conversation

@PettitWesley
Copy link
Copy Markdown
Contributor

@PettitWesley PettitWesley commented Apr 17, 2023

Previously, the AWSLogs driver attempted to implement non-blocking itself. Non-blocking is supposed to
implemented solely by the Docker RingBuffer that
wraps the log driver.

Please see issue and explanation here:
#45217

Signed-off-by: Wesley Pettit [email protected]
(cherry picked from commit c8f8d11)

This fix has been tested and proven to reduce log loss as shown here: #45217 (comment)

We agreed to backport it here, where it was merged into master: #45227 (comment)

Previously, the AWSLogs driver attempted to implement
non-blocking itself. Non-blocking is supposed to
implemented solely by the Docker RingBuffer that
wraps the log driver.

Please see issue and explanation here:
moby#45217

Signed-off-by: Wesley Pettit <[email protected]>
(cherry picked from commit c8f8d11)
@thaJeztah thaJeztah changed the title awslogs: fix non-blocking log drop bug [backport 23.0] [23.0 backport] awslogs: fix non-blocking log drop bug Apr 17, 2023
@thaJeztah thaJeztah added this to the 23.0.5 milestone Apr 17, 2023
@PettitWesley PettitWesley marked this pull request as draft April 17, 2023 20:27
@PettitWesley PettitWesley marked this pull request as ready for review April 17, 2023 21:29
Copy link
Copy Markdown
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thaJeztah thaJeztah merged commit 8fdca28 into moby:23.0 Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants