cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10587) sstablemetadata NPE on cassandra 2.2
Date Tue, 16 Feb 2016 17:34:18 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148956#comment-15148956
] 

Yuki Morishita commented on CASSANDRA-10587:
--------------------------------------------

This is caused by invoking {{sstablemetadata}} with relative path like {{$ sstablemetadata
la-1-big-Data.db}}.
You can workaround by giving absolute path.
I will attach patches for fix.

> 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: Paulo Motta
>             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)

Mime
View raw message