[ https://issues.apache.org/jira/browse/CASSANDRA-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013122#comment-15013122 ]
Tiago Batista commented on CASSANDRA-10587: ------------------------------------------- Yes, I ran upgradesstables. This cluster is hard to reproduce as it has been in production for so long, but I was just able to reproduce it on a two node cluster on centos7. 1. Install cassandra on both nodes and configure the cluster 2. Install opscenter community editon 3. After a few days, run a repair (I did not try the sstablemetadata command before, i forgot) 4. Reproduced! Is there any way to send you a private message? I can send you a link to the whole OpsCenter keyspace files, it is still doable for this new cluster! I will not attach the files as they may contain sensitive information about other keyspaces. > sstablemetadata NPE on cassandra 2.2 > ------------------------------------ > > Key: CASSANDRA-10587 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10587 > Project: Cassandra > Issue Type: Bug > Components: Tools > Reporter: Tiago Batista > Assignee: Ariel Weisberg > Fix For: 2.2.x, 3.x > > > I have recently upgraded my cassandra cluster to 2.2, currently running > 2.2.3. After running the first repair, cassandra renames the sstables to the > new naming schema that does not contain the keyspace name. > This causes sstablemetadata to fail with the following stack trace: > {noformat} > Exception in thread "main" java.lang.NullPointerException > at > org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:275) > at > org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:172) > at > org.apache.cassandra.tools.SSTableMetadataViewer.main(SSTableMetadataViewer.java:52) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)