This repository has been archived by the owner on Nov 14, 2024. It is now read-only.
Simplify Cassandra server in thread names #6092
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goals (and why):
Avoid including set of Cassandra proxy addresses in thread names as seen in example:
Atlas getRowsColumnRange 1 rows from namespace.table on CassandraServer{cassandraHostName=cassandra-123.foo.bar, reachableProxyIps=[cassandra-123.foo.bar/127.0.0.1:9160]} worker task-1234 calling cassandra host cassandra-123.foo.bar/127.0.0.1:9160 started at 2022-06-17T12:00:00.123456789Z - 1234567890
Additional follow on to #6076
==COMMIT_MSG==
Simplify Cassandra server in thread names
Avoid including set of Cassandra proxy addresses in thread names
==COMMIT_MSG==
Implementation Description (bullets):
Include only
CassandraServer
hostname and remove proxy IPs from generatedImmutableCassandraServer#toString()
Testing (What was existing testing like? What have you done to improve it?):
Concerns (what feedback would you like?):
Where should we start reviewing?:
Priority (whenever / two weeks / yesterday):