Skip to content

fix: Ensure tailnet coordinations are sent orderly #4198

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

Merged
merged 1 commit into from
Sep 26, 2022
Merged

Conversation

kylecarbs
Copy link
Member

No description provided.

@kylecarbs kylecarbs requested a review from coadler September 25, 2022 17:57
@kylecarbs kylecarbs self-assigned this Sep 25, 2022
@kylecarbs kylecarbs changed the title fix: Ensure tailnet coordinator can never be blocked fix: Ensure tailnet coordinations are sent orderly Sep 26, 2022
if err != nil {
return
}
server.lastMutex.Lock()
if s.AsOf.Before(server.lastStatus) {
// Don't process outdated status!
server.lastMutex.Unlock()
Copy link
Contributor

Choose a reason for hiding this comment

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

I think you could just defer the Unlock here instead of calling it twice.

Copy link
Member Author

Choose a reason for hiding this comment

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

Nah, because sendNode can take some time

@kylecarbs kylecarbs merged commit b8ec5c7 into main Sep 26, 2022
@kylecarbs kylecarbs deleted the fixblockage branch September 26, 2022 15:16
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