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

backport-2.1: gossip: Don't include gossip connectivity in periodic status logs #30329

Merged
merged 1 commit into from
Sep 18, 2018

Conversation

a-robinson
Copy link
Contributor

Backport 1/1 commits from #30285.

/cc @cockroachdb/release


As discussed on #30088. It can be absolutely massive on large clusters,
and isn't needed because we still log the connectivity info whenever it
changes.

Release note: None

I still think that logging on every change in connectivity is going to be a mess in large clusters during rolling restarts even if gossip is otherwise perfectly stable, but this is useful regardless of whether we do anything about that.

As discussed on cockroachdb#30088. It can be absolutely massive on large clusters,
and isn't needed because we still log the connectivity info whenever it
changes.

Release note: None
@a-robinson a-robinson requested review from petermattis and a team September 17, 2018 21:42
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Collaborator

@petermattis petermattis left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (and 1 stale)

@a-robinson a-robinson merged commit b4074c9 into cockroachdb:release-2.1 Sep 18, 2018
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.

3 participants