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

cluster_id is vulnerable to race condition when called concurrently #94

Merged
merged 2 commits into from
Aug 11, 2016

Conversation

jackfrancis
Copy link
Member

@jackfrancis jackfrancis commented Aug 9, 2016

The Get() method is in fact an "insert if not exist"-style retriever, so it should be protected with a RW lock.

fixes #93

@jackfrancis jackfrancis added this to the v2.4 milestone Aug 9, 2016
@jackfrancis jackfrancis self-assigned this Aug 9, 2016
@deis-bot
Copy link

deis-bot commented Aug 9, 2016

@arschles and @kmala are potential reviewers of this pull request based on my analysis of git blame information. Thanks @jackfrancis!

@codecov-io
Copy link

codecov-io commented Aug 9, 2016

Current coverage is 43.47% (diff: 0.00%)

Merging #94 into master will increase coverage by 0.21%

@@             master        #94   diff @@
==========================================
  Files            11         11          
  Lines           578        582     +4   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
+ Hits            250        253     +3   
- Misses          284        285     +1   
  Partials         44         44          

Powered by Codecov. Last update 2582640...dc8ee48

1) add generic data.ClusterID type in sendVersions type struct
2) enable common clusterID reference to be included in multiple, concurrent jobs, so that appropriate locking can be enforced
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.

intermittent cluster component data collection failures
5 participants