[jira] [Comment Edited] (CASSANDRA-10587) sstablemetadata NPE on cassandra 2.2

2016-02-16 Thread Roman Skvazh (JIRA)

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

Roman Skvazh edited comment on CASSANDRA-10587 at 2/16/16 4:47 PM:
---

Same problem here on 2.2.5 after upgrading from 2.1.13 on all nodes on new 
upgraded "short-named"-files.
{noformat}
Exception in thread "main" java.lang.NullPointerException
at 
org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:271)
at 
org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:172)
at 
org.apache.cassandra.tools.SSTableMetadataViewer.main(SSTableMetadataViewer.java:52)
{noformat}


was (Author: rskvazh):
Same problem here on 2.2.5 after upgrading from 2.1.13 on all nodes.
{noformat}
Exception in thread "main" java.lang.NullPointerException
at 
org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:271)
at 
org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:172)
at 
org.apache.cassandra.tools.SSTableMetadataViewer.main(SSTableMetadataViewer.java:52)
{noformat}

> 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)


[jira] [Comment Edited] (CASSANDRA-10587) sstablemetadata NPE on cassandra 2.2

2015-11-19 Thread Tiago Batista (JIRA)

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

Tiago Batista edited comment on CASSANDRA-10587 at 11/20/15 6:17 AM:
-

Sorry, I was interrupted right after sending you the email, before composing a 
proper set of instructions on how I reproduced this, I may be doing something 
very wrong here!

{code}
[root@node-1 cass-test]# tar -axf /var/lib/cassandra/data/OpsCenter?.tar.gz
[root@node-1 cass-test]# cd OpsCenter/events-14c5005086d111e5ad19ebe38da2fed2/
[root@node-1 events-14c5005086d111e5ad19ebe38da2fed2]# sstablemetadata 
la-1-big-Data.db 
WARN  06:05:11 Only 51918 MB free across all data volumes. Consider adding more 
capacity to your cluster or removing obsolete snapshots
Exception in thread "main" java.lang.NullPointerException
at 
org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:271)
at 
org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:172)
at 
org.apache.cassandra.tools.SSTableMetadataViewer.main(SSTableMetadataViewer.java:52)
{code}

also relevant, I am doing this on centos 7, here is the md5 of the file if you 
wan to try to match it to any build.

{code}
[root@node-1 OpsCenter]# md5sum /usr/bin/sstablemetadata
eed137bd146688499d06acd838313e90  /usr/bin/sstablemetadata
{code}


was (Author: tsbatista):
Sorry, I was interrupted right after sending you the email, before composing a 
proper set of instructions on how I reproduced this, I may be doing something 
very wrong here!

{code}
[root@node-1 cass-test]# tar -axf /var/lib/cassandra/data/OpsCenter?.tar.gz
[root@node-1 cass-test]# cd OpsCenter/events-14c5005086d111e5ad19ebe38da2fed2/
[root@node-1 events-14c5005086d111e5ad19ebe38da2fed2]# sstablemetadata 
la-1-big-Data.db 
WARN  06:05:11 Only 51918 MB free across all data volumes. Consider adding more 
capacity to your cluster or removing obsolete snapshots
Exception in thread "main" java.lang.NullPointerException
at 
org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:271)
at 
org.apache.cassandra.io.sstable.Descriptor.fromFilename(Descriptor.java:172)
at 
org.apache.cassandra.tools.SSTableMetadataViewer.main(SSTableMetadataViewer.java:52)
{code}


> 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)