[
https://issues.apache.org/jira/browse/CASSANDRA-21004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-21004:
----------------------------------------
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/ec7794f20fc0cd07a37901a43f07f4e65517cb08
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Potential NPE when meta keyspace placements are empty before CMS is
> initialized
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-21004
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21004
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 6.x
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> During an upgrade to trunk there is a window before the CMS is initialized
> where the {{system_cluster_metadata}} keyspace exists but is not replicated
> by any peers. At this time, if a JMX client invokes {{getRangeToEndpointMap}}
> on the {{org.apache.cassandra.db:type=StorageService}} mbean for this
> keyspace, it will trigger an NPE on the server.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
