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

Expose race case with ubuntu container #71

Merged
merged 6 commits into from
Oct 15, 2022
Merged

Conversation

Dreeseaw
Copy link
Collaborator

@Dreeseaw Dreeseaw commented Jul 3, 2022

Hello,

I've managed to reliably replicate the race case found in multiple git workflow runs. This requires using a docker container that mocks the specifications of the Github Actions environment, while increasing the exposure area of the edge case within TestSnapshot.

txn.go Outdated
@@ -514,9 +514,11 @@ func (txn *Txn) commitUpdates(chunk commit.Chunk) (updated bool) {

// Range through all of the pending updates and apply them to the column
// and its associated computed columns.
txn.owner.lock.Lock()
Copy link
Owner

Choose a reason for hiding this comment

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

Wouldn't the chunk be already locked? I'm afraid that we'd limit concurrency significantly as only a single writer would be allowed to apply the transaction concurrently in this case. Now, that might not be too bad but I wonder if there's some better way instead of locking the entire Apply?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Unfortunately, I'm not able to work around locking the fill map completely - but I think I've come up with a quicker method that still (seems) to fix the race.

@Dreeseaw Dreeseaw requested a review from kelindar September 3, 2022 16:40
@Dreeseaw
Copy link
Collaborator Author

Dreeseaw commented Sep 3, 2022

As an aside, I can't seem to bring the coverage back up to 100%, and can't figure out why. I think the snapshot recorder has a bug with the commit IDs within certain collection sizes

@kelindar kelindar merged commit 48677f6 into kelindar:main Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants