Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix race condition in reading the dropped spans number #2615

Merged
merged 2 commits into from Feb 16, 2022

Conversation

bogdandrutu
Copy link
Member

As any race condition this should be consider an undefined behavior, and a patch release should be done.

Signed-off-by: Bogdan Drutu bogdandrutu@gmail.com

As any race condition this should be consider an undefined behavior, and a patch release should be done.

Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
@codecov
Copy link

codecov bot commented Feb 16, 2022

Codecov Report

Merging #2615 (a16ce67) into main (cd21df4) will not change coverage.
The diff coverage is 100.0%.

Impacted file tree graph

@@          Coverage Diff          @@
##            main   #2615   +/-   ##
=====================================
  Coverage   76.2%   76.2%           
=====================================
  Files        173     173           
  Lines      12238   12238           
=====================================
  Hits        9328    9328           
  Misses      2667    2667           
  Partials     243     243           
Impacted Files Coverage Δ
sdk/trace/batch_span_processor.go 82.1% <100.0%> (ø)

CHANGELOG.md Outdated Show resolved Hide resolved
sdk/trace/batch_span_processor.go Show resolved Hide resolved
Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
Copy link
Member

@pellared pellared left a comment

Choose a reason for hiding this comment

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

While the synchornization logic behind bsp.dropped could be improved I still see value in this PR.

Copy link
Member

@XSAM XSAM left a comment

Choose a reason for hiding this comment

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

atomic.LoadUint32(&bsp.dropped) could be a marker that indicates a logging point for dropped spans while refactoring the synchronization logic.

@bogdandrutu
Copy link
Member Author

Since this is an important bug fix, can you please merge and release 1.4.1. This blocks downstream dependencies to upgrade, since tools will block the upgrade because of race condition detected.

@MrAlias MrAlias merged commit 2a9cedf into open-telemetry:main Feb 16, 2022
@MrAlias MrAlias added the bug Something isn't working label Feb 16, 2022
@MrAlias
Copy link
Contributor

MrAlias commented Feb 16, 2022

Working on the release now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants