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

Clean up remoteSites with no active tunnels #11435

Merged
merged 4 commits into from
Mar 31, 2022

Conversation

rosstimothy
Copy link
Contributor

Not closing a remoteSite causes a continuous retry to init the cache
on the remote auth client. Not only does this cause log spam but is
a waste of resources.

We now stop tracking and close a remoteSite when its heartBeat fails
and no active tunnels are established for the site.

Fixes #11197

Not closing a remoteSite causes a continuous retry to init the cache
on the remote auth client. Not only does this cause log spam but is
a waste of resources.

We now stop tracking and close a remoteSite when its heartBeat fails
and no active tunnels are established for the site.

Fixes #11197
@rosstimothy rosstimothy marked this pull request as ready for review March 24, 2022 22:08
@github-actions github-actions bot added the database-access Database access related issues and PRs label Mar 24, 2022
@rosstimothy rosstimothy merged commit 3d5928f into master Mar 31, 2022
@rosstimothy rosstimothy deleted the tross/remote_site_clean_up branch March 31, 2022 12:46
rosstimothy added a commit that referenced this pull request Apr 4, 2022
Not closing a remoteSite causes a continuous retry to init the cache
on the remote auth client. Not only does this cause log spam but is
a waste of resources.

We now stop tracking and close a remoteSite when its heartBeat fails
and no active tunnels are established for the site.

Fixes #11197

(cherry picked from commit 3d5928f)

# Conflicts:
#	lib/reversetunnel/fake.go
#	lib/srv/db/access_test.go
rosstimothy added a commit that referenced this pull request Apr 4, 2022
Not closing a remoteSite causes a continuous retry to init the cache
on the remote auth client. Not only does this cause log spam but is
a waste of resources.

We now stop tracking and close a remoteSite when its heartBeat fails
and no active tunnels are established for the site.

Fixes #11197

(cherry picked from commit 3d5928f)

# Conflicts:
#	lib/reversetunnel/fake.go
#	lib/srv/db/access_test.go
rosstimothy added a commit that referenced this pull request Apr 4, 2022
Not closing a remoteSite causes a continuous retry to init the cache
on the remote auth client. Not only does this cause log spam but is
a waste of resources.

We now stop tracking and close a remoteSite when its heartBeat fails
and no active tunnels are established for the site.

Fixes #11197

(cherry picked from commit 3d5928f)

# Conflicts:
#	lib/reversetunnel/fake.go
#	lib/srv/db/access_test.go
@rosstimothy
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
branch/v7
branch/v8
branch/v9

Questions ?

Please refer to the Backport tool documentation

rosstimothy added a commit that referenced this pull request Apr 5, 2022
Not closing a remoteSite causes a continuous retry to init the cache
on the remote auth client. Not only does this cause log spam but is
a waste of resources.

We now stop tracking and close a remoteSite when its heartBeat fails
and no active tunnels are established for the site.

Fixes #11197

(cherry picked from commit 3d5928f)
rosstimothy added a commit that referenced this pull request Apr 5, 2022
Not closing a remoteSite causes a continuous retry to init the cache
on the remote auth client. Not only does this cause log spam but is
a waste of resources.

We now stop tracking and close a remoteSite when its heartBeat fails
and no active tunnels are established for the site.

Fixes #11197

(cherry picked from commit 3d5928f)
rosstimothy added a commit that referenced this pull request Apr 5, 2022
Not closing a remoteSite causes a continuous retry to init the cache
on the remote auth client. Not only does this cause log spam but is
a waste of resources.

We now stop tracking and close a remoteSite when its heartBeat fails
and no active tunnels are established for the site.

Fixes #11197

(cherry picked from commit 3d5928f)
@webvictim webvictim mentioned this pull request Apr 19, 2022
@webvictim webvictim mentioned this pull request Jun 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database-access Database access related issues and PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Losing all reverse tunnels to a remote cluster should stop its matching remoteSite
3 participants