[CASSANDRASC-83] Require gossip to be enabled for ring and token ranges mapping endpoints

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.0
• Component/s: Rest API
• Labels: pull-request-available
• Change Category: Semantic
• Complexity: Normal

Source Control Link

https://github.com/apache/cassandra-sidecar/commit/c1a6225dac62db94fd3faee92513e84ba3b9b3b7

Test and Documentation Plan

Added test to ensure the expected response is returned when gossip is disabled for the ring endpoint and the token ranges mapping endpoint.

• Assignee: Francisco Guerrero
• Reporter: Francisco Guerrero

Reviewers

Dinesh Joshi, Josh McKenzie, Yifan Cai

• Created: 07/Nov/23 18:52
• Updated: 28/Nov/23 16:06
• Resolved: 28/Nov/23 16:06

Description

The ring and token ranges mapping endpoints leverage JMX to produce the payload. Ring and token ranges mapping information is derived from gossip information available to the Cassandra instance. If gossip has been disabled, the information might provide an inconsistent view of the cluster which is undesirable. We should instead return a 503 (Service Unavailable) to the client whenever the client tries to access these endpoints and gossip has been disabled.

Issue Links

• links to: GitHub Pull Request #77