Skip to content

Conversation

dapc11
Copy link

@dapc11 dapc11 commented Apr 19, 2021

When Cassandra has not yet started up and /metrics is called, then FBUtilities.getlocalBroadcastAddress is called and sets variables which causes faulty address to be set for the local broadcast address.

Using the same logic as FBUtilities, but not assigning any variable that Cassandra server itself is using elsewhere.

When Cassandra has not yet started up and /metrics is called, then
FBUtilities.getlocalBroadcastAddress is called and sets variables
which causes faulty address to be set for the local broadcast address.

Using the same logic as FBUtilities, but not assigning any variable
that Cassandra server itself is using elsewhere.
@dapc11
Copy link
Author

dapc11 commented Apr 19, 2021

This is a fix for when doing metrics scraping at an early stage of Cassandra startup. When calling FBUtillities.getlocalBroadcastAddress the field is set, resulting in that it's not assigned to the proper address when Cassandra has started up.

Related to #42, not fixing the stacktrace in log, but fixing so that StorageService can populate the broadcast address properly.

@johndelcastillo johndelcastillo force-pushed the master branch 2 times, most recently from 3b88272 to 84cb7cd Compare October 19, 2023 03:44
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.

1 participant