[jira] [Commented] (CASSANDRA-6450) sstable2json hangs if keyspace uses authentication
[ https://issues.apache.org/jira/browse/CASSANDRA-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955669#comment-13955669 ] Josh Dzielak commented on CASSANDRA-6450: - Agreed, it looks like it isn't not related to auth. I just tried an SSTable that I know is healthy and it worked fine. It must have been something with the data that caused the hang. > sstable2json hangs if keyspace uses authentication > -- > > Key: CASSANDRA-6450 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6450 > Project: Cassandra > Issue Type: Bug > Environment: Ubuntu 12 >Reporter: Josh Dzielak >Priority: Minor > Labels: lhf > > Running sstable2json against an authenticated keyspace hangs indefinitely. > True for other utilities based on SSTableExport as well. > Running sstable2json against other unauthenticated keyspaces in the same > node/cluster was successful. Running against any CF in the keyspace with > password authentication on resulted in a hang. > It looks like it gets about to: > Table table = Table.open(descriptor.ksname); or > table.getColumnFamilyStore(baseName); > in SSTableExport.java but no farther. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-6450) sstable2json hangs if keyspace uses authentication
[ https://issues.apache.org/jira/browse/CASSANDRA-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955588#comment-13955588 ] Chris Lohfink commented on CASSANDRA-6450: -- not sure if related to authentication, might be something with your data? I enabled authentication/authorization in cassandra.yaml with default cassandra/cassandra user and gave it a quick try: {code} /var/lib/cassandra/data/Keyspace1/Standard1$ sstable2json Keyspace1-Standard1-ic-1-Data.db WARN 14:43:53,224 MemoryMeter uninitialized (jamm not specified as java agent); KeyCache size in JVM Heap will not be calculated accurately. Usually this means cassandra-env.sh disabled jamm because you are using a buggy JRE; upgrade to the Sun JRE instead [ {"key": "30313236303933","columns": [["C0", ... {code} Or perhaps theres something involved in adding data after authentication enabled? Are there any other steps to help reproduce this? > sstable2json hangs if keyspace uses authentication > -- > > Key: CASSANDRA-6450 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6450 > Project: Cassandra > Issue Type: Bug > Environment: Ubuntu 12 >Reporter: Josh Dzielak >Priority: Minor > Labels: lhf > > Running sstable2json against an authenticated keyspace hangs indefinitely. > True for other utilities based on SSTableExport as well. > Running sstable2json against other unauthenticated keyspaces in the same > node/cluster was successful. Running against any CF in the keyspace with > password authentication on resulted in a hang. > It looks like it gets about to: > Table table = Table.open(descriptor.ksname); or > table.getColumnFamilyStore(baseName); > in SSTableExport.java but no farther. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-6450) sstable2json hangs if keyspace uses authentication
[ https://issues.apache.org/jira/browse/CASSANDRA-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855447#comment-13855447 ] Daniel Kador commented on CASSANDRA-6450: - Just wanted to update this to say that this is blocking us from doing some investigation into whether or not we're getting hit by a tombstone. Would love to hear if this shouldn't work and we're using the tool wrong or if it should and it's a bug. Thanks! > sstable2json hangs if keyspace uses authentication > -- > > Key: CASSANDRA-6450 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6450 > Project: Cassandra > Issue Type: Bug > Environment: Ubuntu 12 >Reporter: Josh Dzielak >Priority: Minor > > Running sstable2json against an authenticated keyspace hangs indefinitely. > True for other utilities based on SSTableExport as well. > Running sstable2json against other unauthenticated keyspaces in the same > node/cluster was successful. Running against any CF in the keyspace with > password authentication on resulted in a hang. > It looks like it gets about to: > Table table = Table.open(descriptor.ksname); or > table.getColumnFamilyStore(baseName); > in SSTableExport.java but no farther. -- This message was sent by Atlassian JIRA (v6.1.5#6160)