[jira] [Commented] (CASSANDRA-6764) Using Batch commitlog_sync is slow and doesn't actually batch writes

2014-02-24 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911203#comment-13911203
 ] 

Michael Harris commented on CASSANDRA-6764:
---

Carrino, does this change have the potential to cause any problems during 
rolling upgrades?  It looks like you're modifying an existing codepath to use a 
new type that gets serialized to other nodes.  That could be very...explosive.  
Am I missing something?  Rolling upgrades are pretty common for minor version 
upgrades (correct me if I'm wrong Jonathan), so this is actually kind of scary.

 Using Batch commitlog_sync is slow and doesn't actually batch writes
 

 Key: CASSANDRA-6764
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6764
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: John Carrino
 Fix For: 1.2.16

 Attachments: cassandra_6764_v2.patch


 The assumption behind batch commit mode is that the client does it's own 
 batching and wants to wait until the write is durable before returning.  The 
 problem is that the queue that cassandra uses under the covers only allows 
 for a single ROW (RowMutation) per thread (concurrent_writes).  This means 
 that commitlog_sync_batch_window_in_ms should really be called sleep_between 
 each_concurrent_writes_rows_in_ms.
 I assume the reason this slipped by for so long is that no one uses batch 
 mode, probably because people say it's slow.  We need durability so this 
 isn't an option.
 However it doesn't need to be this slow.
 Also, if you write a row that is larger than the commit log size it silently 
 (warn) fails to put it in the commit log.  This is not ideal for batch mode.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (CASSANDRA-4952) Add blocking force compaction (and anything else) calls to NodeProbe

2013-08-26 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750645#comment-13750645
 ] 

Michael Harris commented on CASSANDRA-4952:
---

yep, looks totally fine to me

 Add blocking force compaction (and anything else) calls to NodeProbe
 

 Key: CASSANDRA-4952
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4952
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.1.6
Reporter: Michael Harris
Assignee: Jonathan Ellis
Priority: Minor
  Labels: lhf
 Attachments: 4952.txt


 There are times when I'd like to get feedback about when compactions 
 complete.  For example, if I'm deleting data from cassandra and want to know 
 when it is 100% removed from cassandra (tombstones collected and all).  This 
 is completely trivial to implement based on the existing code (the method 
 called by the non-blocking version returns a future, so you could just wait 
 on that, potentially with a timeout).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4952) Add blocking force compaction (and anything else) calls to NodeProbe

2013-08-21 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13746544#comment-13746544
 ] 

Michael Harris commented on CASSANDRA-4952:
---

It doesn't look like user defined compaction has this property, however.  
Unless 1.2 does and I'm still looking at 1.1 code.

 Add blocking force compaction (and anything else) calls to NodeProbe
 

 Key: CASSANDRA-4952
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4952
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.1.6
Reporter: Michael Harris
Priority: Minor
  Labels: lhf

 There are times when I'd like to get feedback about when compactions 
 complete.  For example, if I'm deleting data from cassandra and want to know 
 when it is 100% removed from cassandra (tombstones collected and all).  This 
 is completely trivial to implement based on the existing code (the method 
 called by the non-blocking version returns a future, so you could just wait 
 on that, potentially with a timeout).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4952) Add blocking force compaction (and anything else) calls to NodeProbe

2013-08-16 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742833#comment-13742833
 ] 

Michael Harris commented on CASSANDRA-4952:
---

it might even be better to expose the timeout as a parameter to the compaction 
(with a reasonable default, sure).  I'd love to be able to specify a very high 
timeout because I might be compacting a 100GB+ collection of column families, 
which could take a while.

 Add blocking force compaction (and anything else) calls to NodeProbe
 

 Key: CASSANDRA-4952
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4952
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.1.6
Reporter: Michael Harris
Priority: Minor
  Labels: lhf

 There are times when I'd like to get feedback about when compactions 
 complete.  For example, if I'm deleting data from cassandra and want to know 
 when it is 100% removed from cassandra (tombstones collected and all).  This 
 is completely trivial to implement based on the existing code (the method 
 called by the non-blocking version returns a future, so you could just wait 
 on that, potentially with a timeout).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5186) Schema NPEs in 1.1.6. Upgrading to 1.1.9 causes IllegalArgumentException loading Schema

2013-02-05 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571808#comment-13571808
 ] 

Michael Harris commented on CASSANDRA-5186:
---

so, do you want us to apply this patch and get back to you with the exception?  
I'm not exactly sure how that's going to help you debug this, but we can do it 
if you want.

 Schema NPEs in 1.1.6.  Upgrading to 1.1.9 causes IllegalArgumentException 
 loading Schema
 

 Key: CASSANDRA-5186
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5186
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
Reporter: Michael Harris
Priority: Critical
 Attachments: 5186.patch


 We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
 were told to upgrade to 1.1.9.  Now the schema fails to load with the 
 following error:
 java.lang.IllegalArgumentException: value already present: 1105
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
 at 
 com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112)
 at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
 at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
 at org.apache.cassandra.config.Schema.load(Schema.java:399)
 at org.apache.cassandra.config.Schema.load(Schema.java:120)
 at org.apache.cassandra.config.Schema.load(Schema.java:105)
 at 
 org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:534)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:183)
 at 
 com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaemon.setup(PTCassandraServer.java:64)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:389)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5186) Schema NPEs in 1.1.6. Upgrading to 1.1.9 causes IllegalArgumentException loading Schema

2013-02-05 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571940#comment-13571940
 ] 

Michael Harris commented on CASSANDRA-5186:
---

Got it, thanks for the info Jonathan.  Anything you want on our end regarding 
this (any plans to fix in a 1.1.10 or something), or is the right solution just 
to upgrade to 1.2?  I'm fine with doing the latter in a month or so when 1.2 
gets ironed out further.

 Schema NPEs in 1.1.6.  Upgrading to 1.1.9 causes IllegalArgumentException 
 loading Schema
 

 Key: CASSANDRA-5186
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5186
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
Reporter: Michael Harris
Priority: Critical
 Attachments: 5186.patch


 We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
 were told to upgrade to 1.1.9.  Now the schema fails to load with the 
 following error:
 java.lang.IllegalArgumentException: value already present: 1105
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
 at 
 com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112)
 at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
 at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
 at org.apache.cassandra.config.Schema.load(Schema.java:399)
 at org.apache.cassandra.config.Schema.load(Schema.java:120)
 at org.apache.cassandra.config.Schema.load(Schema.java:105)
 at 
 org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:534)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:183)
 at 
 com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaemon.setup(PTCassandraServer.java:64)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:389)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-5186) Schema NPEs in 1.1.6. Upgrading to 1.1.9 causes IllegalArgumentException loading Schema

2013-02-03 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13569966#comment-13569966
 ] 

Michael Harris commented on CASSANDRA-5186:
---

We wrap cassandra in a custom web service, so yes and no?  I don't think 
that should affect this. We're only creating one cassandra service.





 Schema NPEs in 1.1.6.  Upgrading to 1.1.9 causes IllegalArgumentException 
 loading Schema
 

 Key: CASSANDRA-5186
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5186
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
Reporter: Michael Harris
Priority: Critical

 We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
 were told to upgrade to 1.1.9.  Now the schema fails to load with the 
 following error:
 java.lang.IllegalArgumentException: value already present: 1105
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
 at 
 com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112)
 at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
 at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
 at org.apache.cassandra.config.Schema.load(Schema.java:399)
 at org.apache.cassandra.config.Schema.load(Schema.java:120)
 at org.apache.cassandra.config.Schema.load(Schema.java:105)
 at 
 org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:534)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:183)
 at 
 com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaemon.setup(PTCassandraServer.java:64)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:389)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-5186) Schema NPEs in 1.1.6. Upgrading to 1.1.9 causes IllegalArgumentException loading Schema

2013-01-25 Thread Michael Harris (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Harris updated CASSANDRA-5186:
--

Description: 
We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
were told to upgrade to 1.1.9.  Now the schema fails to load with the following 
error:

java.lang.IllegalArgumentException: value already present: 1105
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
at com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112)
at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
at org.apache.cassandra.config.Schema.load(Schema.java:399)
at org.apache.cassandra.config.Schema.load(Schema.java:120)
at org.apache.cassandra.config.Schema.load(Schema.java:105)
at 
org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:534)
at 
org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:183)
at 
com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaemon.setup(PTCassandraServer.java:64)
at 
org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:389)

  was:
We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
were told to upgrade to 1.1.9.  Now the schema fails to load with the following 
error:

java.lang.IllegalArgumentException: value already present: 1105
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
at com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112
)
at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
at org.apache.cassandra.config.Schema.load(Schema.java:399)
at org.apache.cassandra.config.Schema.load(Schema.java:120)
at org.apache.cassandra.config.Schema.load(Schema.java:105)
at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescripto
r.java:534)
at org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandra
Daemon.java:183)
at com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaem
on.setup(PTCassandraServer.java:64)
at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassan
draDaemon.java:389)


 Schema NPEs in 1.1.6.  Upgrading to 1.1.9 causes IllegalArgumentException 
 loading Schema
 

 Key: CASSANDRA-5186
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5186
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
Reporter: Michael Harris
Priority: Critical

 We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
 were told to upgrade to 1.1.9.  Now the schema fails to load with the 
 following error:
 java.lang.IllegalArgumentException: value already present: 1105
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
 at 
 com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112)
 at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
 at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
 at org.apache.cassandra.config.Schema.load(Schema.java:399)
 at org.apache.cassandra.config.Schema.load(Schema.java:120)
 at org.apache.cassandra.config.Schema.load(Schema.java:105)
 at 
 org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescriptor.java:534)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:183)
 at 
 com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaemon.setup(PTCassandraServer.java:64)
 at 
 org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:389)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CASSANDRA-5186) Schema NPEs in 1.1.6. Upgrading to 1.1.9 causes IllegalArgumentException loading Schema

2013-01-25 Thread Michael Harris (JIRA) 
Michael Harris created CASSANDRA-5186:
-

 Summary: Schema NPEs in 1.1.6.  Upgrading to 1.1.9 causes 
IllegalArgumentException loading Schema
 Key: CASSANDRA-5186
 URL: https://issues.apache.org/jira/browse/CASSANDRA-5186
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.9
Reporter: Michael Harris
Priority: Critical


We experienced the problems described in CASSANDRA-4219 in version 1.1.6.  We 
were told to upgrade to 1.1.9.  Now the schema fails to load with the following 
error:

java.lang.IllegalArgumentException: value already present: 1105
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115)
at com.google.common.collect.AbstractBiMap.putInBothMaps(AbstractBiMap.java:112
)
at com.google.common.collect.AbstractBiMap.put(AbstractBiMap.java:96)
at com.google.common.collect.HashBiMap.put(HashBiMap.java:85)
at org.apache.cassandra.config.Schema.load(Schema.java:399)
at org.apache.cassandra.config.Schema.load(Schema.java:120)
at org.apache.cassandra.config.Schema.load(Schema.java:105)
at org.apache.cassandra.config.DatabaseDescriptor.loadSchemas(DatabaseDescripto
r.java:534)
at org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandra
Daemon.java:183)
at com.palantir.phoenix.datastore.cass.server.PTCassandraServer$PTCassandraDaem
on.setup(PTCassandraServer.java:64)
at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassan
draDaemon.java:389)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4786) NPE in migration stage after creating an index

2013-01-23 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561222#comment-13561222
 ] 

Michael Harris commented on CASSANDRA-4786:
---

Do you guys know what version this bug was introduced in?  This is affecting 
us, but we're hesitant to move to 1.2 so soon after release.  Do you have a 
recommendation for a version of cassandra to use that would not be affected by 
this?

 NPE in migration stage after creating an index
 --

 Key: CASSANDRA-4786
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4786
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Brandon Williams
Assignee: Sylvain Lebresne
 Fix For: 1.2.0 beta 2

 Attachments: 4786.txt


 The dtests are generating this error after trying to create an index in cql2:
 {noformat}
 ERROR [MigrationStage:1] 2012-10-09 20:54:12,796 CassandraDaemon.java (line 
 132) Exception in thread Thread[MigrationStage:1,5,main]
 java.lang.NullPointerException
 at 
 org.apache.cassandra.db.ColumnFamilyStore.reload(ColumnFamilyStore.java:162)
 at 
 org.apache.cassandra.db.DefsTable.updateColumnFamily(DefsTable.java:549)
 at 
 org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:479)
 at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:344)
 at 
 org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:256)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 ERROR [Thrift:1] 2012-10-09 20:54:12,797 CustomTThreadPoolServer.java (line 
 214) Error occurred during processing of message.
 java.lang.RuntimeException: java.util.concurrent.ExecutionException: 
 java.lang.NullPointerException
 at 
 org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:348)
 at 
 org.apache.cassandra.service.MigrationManager.announce(MigrationManager.java:238)
 at 
 org.apache.cassandra.service.MigrationManager.announceColumnFamilyUpdate(MigrationManager.java:209)
 at 
 org.apache.cassandra.cql.QueryProcessor.processStatement(QueryProcessor.java:714)
 at 
 org.apache.cassandra.cql.QueryProcessor.process(QueryProcessor.java:816)
 at 
 org.apache.cassandra.thrift.CassandraServer.execute_cql_query(CassandraServer.java:1656)
 at 
 org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3721)
 at 
 org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3709)
 at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
 at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
 at 
 org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:196)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: java.util.concurrent.ExecutionException: 
 java.lang.NullPointerException
 at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
 at java.util.concurrent.FutureTask.get(FutureTask.java:83)
 at 
 org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:344)
 ... 13 more
 Caused by: java.lang.NullPointerException
 at 
 org.apache.cassandra.db.ColumnFamilyStore.reload(ColumnFamilyStore.java:162)
 at 
 org.apache.cassandra.db.DefsTable.updateColumnFamily(DefsTable.java:549)
 at 
 org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:479)
 at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:344)
 at 
 org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:256)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 ... 3 more
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4786) NPE in migration stage after creating an index

2013-01-23 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561266#comment-13561266
 ] 

Michael Harris commented on CASSANDRA-4786:
---

Weird, we're seeing this on 1.1.6.  Do you know of a fix we could try for this 
on that version?  We saw a similar bug had been fixed for 1.1.1, so it's 
surprising to see it again in 1.1.6.  I'll double check our deployment setup, 
but I'm pretty sure that's the case.



 NPE in migration stage after creating an index
 --

 Key: CASSANDRA-4786
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4786
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.0 beta 1
Reporter: Brandon Williams
Assignee: Sylvain Lebresne
 Fix For: 1.2.0 beta 2

 Attachments: 4786.txt


 The dtests are generating this error after trying to create an index in cql2:
 {noformat}
 ERROR [MigrationStage:1] 2012-10-09 20:54:12,796 CassandraDaemon.java (line 
 132) Exception in thread Thread[MigrationStage:1,5,main]
 java.lang.NullPointerException
 at 
 org.apache.cassandra.db.ColumnFamilyStore.reload(ColumnFamilyStore.java:162)
 at 
 org.apache.cassandra.db.DefsTable.updateColumnFamily(DefsTable.java:549)
 at 
 org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:479)
 at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:344)
 at 
 org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:256)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 ERROR [Thrift:1] 2012-10-09 20:54:12,797 CustomTThreadPoolServer.java (line 
 214) Error occurred during processing of message.
 java.lang.RuntimeException: java.util.concurrent.ExecutionException: 
 java.lang.NullPointerException
 at 
 org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:348)
 at 
 org.apache.cassandra.service.MigrationManager.announce(MigrationManager.java:238)
 at 
 org.apache.cassandra.service.MigrationManager.announceColumnFamilyUpdate(MigrationManager.java:209)
 at 
 org.apache.cassandra.cql.QueryProcessor.processStatement(QueryProcessor.java:714)
 at 
 org.apache.cassandra.cql.QueryProcessor.process(QueryProcessor.java:816)
 at 
 org.apache.cassandra.thrift.CassandraServer.execute_cql_query(CassandraServer.java:1656)
 at 
 org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3721)
 at 
 org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3709)
 at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
 at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
 at 
 org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:196)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: java.util.concurrent.ExecutionException: 
 java.lang.NullPointerException
 at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
 at java.util.concurrent.FutureTask.get(FutureTask.java:83)
 at 
 org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:344)
 ... 13 more
 Caused by: java.lang.NullPointerException
 at 
 org.apache.cassandra.db.ColumnFamilyStore.reload(ColumnFamilyStore.java:162)
 at 
 org.apache.cassandra.db.DefsTable.updateColumnFamily(DefsTable.java:549)
 at 
 org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:479)
 at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:344)
 at 
 org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:256)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 ... 3 more
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4786) NPE in migration stage after creating an index

2013-01-23 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561345#comment-13561345
 ] 

Michael Harris commented on CASSANDRA-4786:
---

Apologies, I think I was barking up the wrong tree here.  The stack trace I'm 
seeing actually matches CASSANDRA-4219, which looks similar but isn't quite the 
same thing, so I'll start being obnoxious on that thread instead.

 NPE in migration stage after creating an index
 --

 Key: CASSANDRA-4786
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4786
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.2.0 beta 1
Reporter: Brandon Williams
Assignee: Sylvain Lebresne
 Fix For: 1.2.0 beta 2

 Attachments: 4786.txt


 The dtests are generating this error after trying to create an index in cql2:
 {noformat}
 ERROR [MigrationStage:1] 2012-10-09 20:54:12,796 CassandraDaemon.java (line 
 132) Exception in thread Thread[MigrationStage:1,5,main]
 java.lang.NullPointerException
 at 
 org.apache.cassandra.db.ColumnFamilyStore.reload(ColumnFamilyStore.java:162)
 at 
 org.apache.cassandra.db.DefsTable.updateColumnFamily(DefsTable.java:549)
 at 
 org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:479)
 at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:344)
 at 
 org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:256)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 ERROR [Thrift:1] 2012-10-09 20:54:12,797 CustomTThreadPoolServer.java (line 
 214) Error occurred during processing of message.
 java.lang.RuntimeException: java.util.concurrent.ExecutionException: 
 java.lang.NullPointerException
 at 
 org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:348)
 at 
 org.apache.cassandra.service.MigrationManager.announce(MigrationManager.java:238)
 at 
 org.apache.cassandra.service.MigrationManager.announceColumnFamilyUpdate(MigrationManager.java:209)
 at 
 org.apache.cassandra.cql.QueryProcessor.processStatement(QueryProcessor.java:714)
 at 
 org.apache.cassandra.cql.QueryProcessor.process(QueryProcessor.java:816)
 at 
 org.apache.cassandra.thrift.CassandraServer.execute_cql_query(CassandraServer.java:1656)
 at 
 org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3721)
 at 
 org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3709)
 at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
 at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
 at 
 org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:196)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: java.util.concurrent.ExecutionException: 
 java.lang.NullPointerException
 at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
 at java.util.concurrent.FutureTask.get(FutureTask.java:83)
 at 
 org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:344)
 ... 13 more
 Caused by: java.lang.NullPointerException
 at 
 org.apache.cassandra.db.ColumnFamilyStore.reload(ColumnFamilyStore.java:162)
 at 
 org.apache.cassandra.db.DefsTable.updateColumnFamily(DefsTable.java:549)
 at 
 org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:479)
 at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:344)
 at 
 org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:256)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 ... 3 more
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4219) Problem with creating keyspace after drop

2013-01-23 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561375#comment-13561375
 ] 

Michael Harris commented on CASSANDRA-4219:
---

I am seeing this issue on version 1.1.6 as well upon dropping and recreating a 
keyspace.  Any idea whether there might have been a regression between the fix 
of this issue and the release of 1.1.6?

java.lang.RuntimeException: java.util.concurrent.ExecutionException: 
java.lang.NullPointerException
at 
org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:373)
at 
org.apache.cassandra.service.MigrationManager.announce(MigrationManager.java:194)
at 
org.apache.cassandra.service.MigrationManager.announceNewKeyspace(MigrationManager.java:127)
at 
org.apache.cassandra.thrift.CassandraServer.system_add_keyspace(CassandraServer.java:992)
... (redacted)
Caused by: java.util.concurrent.ExecutionException: 
java.lang.NullPointerException
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at 
org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:369)
... 64 more
Caused by: java.lang.NullPointerException
at org.apache.cassandra.db.DefsTable.updateKeyspace(DefsTable.java:518)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:415)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:345)
at 
org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:217)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
... 3 more

 Problem with creating keyspace after drop
 -

 Key: CASSANDRA-4219
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4219
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.0
 Environment: Debian 6.0.4 x64
Reporter: Jeff Williams
Assignee: Pavel Yaskevich
 Fix For: 1.1.1

 Attachments: 0001-Add-debug-logs.txt, CASSANDRA-4219.patch, 
 system-91.223.192.26.log.gz, system-debug.log.gz, system.log.gz, 
 system-startup-debug.log.gz


 Hi,
 I'm doing testing and wanted to drop a keyspace (with a column family) to 
 re-add it with a different strategy. So I ran in cqlsh:
 DROP KEYSPACE PlayLog;
 CREATE KEYSPACE PlayLog WITH strategy_class = 'SimpleStrategy'
  AND strategy_options:replication_factor = 2;
 And everything seemed to be fine. I ran some inserts, which also seemed to go 
 fine, but then selecting them gave me:
 cqlsh:PlayLog select count(*) from playlog;
 TSocket read 0 bytes
 I wasn't sure what was wrong, so I tried dropping and creating again, and now 
 when I try to create I get:
 cqlsh CREATE KEYSPACE PlayLog WITH strategy_class = 'SimpleStrategy'
   ...   AND strategy_options:replication_factor = 2;
 TSocket read 0 bytes
 And the keyspace doesn't get created. In the log it shows:
 ERROR [Thrift:4] 2012-05-03 18:23:05,124 CustomTThreadPoolServer.java (line 
 204) Error occurred during processing of message.
 java.lang.RuntimeException: java.util.concurrent.ExecutionException: 
 java.lang.AssertionError
at 
 org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:372)
at 
 org.apache.cassandra.service.MigrationManager.announce(MigrationManager.java:191)
at 
 org.apache.cassandra.service.MigrationManager.announceNewKeyspace(MigrationManager.java:129)
at 
 org.apache.cassandra.cql.QueryProcessor.processStatement(QueryProcessor.java:701)
at 
 org.apache.cassandra.cql.QueryProcessor.process(QueryProcessor.java:875)
at 
 org.apache.cassandra.thrift.CassandraServer.execute_cql_query(CassandraServer.java:1235)
at 
 org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3458)
at 
 org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3446)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
at 
 org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:186)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
 Caused by: java.util.concurrent.ExecutionException: java.lang.AssertionError
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at

[jira] [Commented] (CASSANDRA-4219) Problem with creating keyspace after drop

2013-01-23 Thread Michael Harris (JIRA) 

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561391#comment-13561391
 ] 

Michael Harris commented on CASSANDRA-4219:
---

Your bug-tracking system isn't the right place to report that a bug that was 
supposed to be fixed might have a regression in a later version...?  Ok, I'll 
mail the list then...

 Problem with creating keyspace after drop
 -

 Key: CASSANDRA-4219
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4219
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.0
 Environment: Debian 6.0.4 x64
Reporter: Jeff Williams
Assignee: Pavel Yaskevich
 Fix For: 1.1.1

 Attachments: 0001-Add-debug-logs.txt, CASSANDRA-4219.patch, 
 system-91.223.192.26.log.gz, system-debug.log.gz, system.log.gz, 
 system-startup-debug.log.gz


 Hi,
 I'm doing testing and wanted to drop a keyspace (with a column family) to 
 re-add it with a different strategy. So I ran in cqlsh:
 DROP KEYSPACE PlayLog;
 CREATE KEYSPACE PlayLog WITH strategy_class = 'SimpleStrategy'
  AND strategy_options:replication_factor = 2;
 And everything seemed to be fine. I ran some inserts, which also seemed to go 
 fine, but then selecting them gave me:
 cqlsh:PlayLog select count(*) from playlog;
 TSocket read 0 bytes
 I wasn't sure what was wrong, so I tried dropping and creating again, and now 
 when I try to create I get:
 cqlsh CREATE KEYSPACE PlayLog WITH strategy_class = 'SimpleStrategy'
   ...   AND strategy_options:replication_factor = 2;
 TSocket read 0 bytes
 And the keyspace doesn't get created. In the log it shows:
 ERROR [Thrift:4] 2012-05-03 18:23:05,124 CustomTThreadPoolServer.java (line 
 204) Error occurred during processing of message.
 java.lang.RuntimeException: java.util.concurrent.ExecutionException: 
 java.lang.AssertionError
at 
 org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:372)
at 
 org.apache.cassandra.service.MigrationManager.announce(MigrationManager.java:191)
at 
 org.apache.cassandra.service.MigrationManager.announceNewKeyspace(MigrationManager.java:129)
at 
 org.apache.cassandra.cql.QueryProcessor.processStatement(QueryProcessor.java:701)
at 
 org.apache.cassandra.cql.QueryProcessor.process(QueryProcessor.java:875)
at 
 org.apache.cassandra.thrift.CassandraServer.execute_cql_query(CassandraServer.java:1235)
at 
 org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3458)
at 
 org.apache.cassandra.thrift.Cassandra$Processor$execute_cql_query.getResult(Cassandra.java:3446)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
at 
 org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:186)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
 Caused by: java.util.concurrent.ExecutionException: java.lang.AssertionError
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at 
 org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:368)
... 13 more
 Caused by: java.lang.AssertionError
at org.apache.cassandra.db.DefsTable.updateKeyspace(DefsTable.java:441)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:339)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:269)
at 
 org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:214)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
... 3 more
 ERROR [MigrationStage:1] 2012-05-03 18:23:05,124 AbstractCassandraDaemon.java 
 (line 134) Exception in thread Thread[MigrationStage:1,5,main]
 java.lang.AssertionError
at org.apache.cassandra.db.DefsTable.updateKeyspace(DefsTable.java:441)
at org.apache.cassandra.db.DefsTable.mergeKeyspaces(DefsTable.java:339)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:269)
at 
 org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:214)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at

[jira] [Created] (CASSANDRA-4952) Add blocking force compaction (and anything else) calls to NodeProbe

2012-11-12 Thread Michael Harris (JIRA) 
Michael Harris created CASSANDRA-4952:
-

 Summary: Add blocking force compaction (and anything else) calls 
to NodeProbe
 Key: CASSANDRA-4952
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4952
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Affects Versions: 1.1.6
Reporter: Michael Harris


There are times when I'd like to get feedback about when compactions complete.  
For example, if I'm deleting data from cassandra and want to know when it is 
100% removed from cassandra (tombstones collected and all).  This is completely 
trivial to implement based on the existing code (the method called by the 
non-blocking version returns a future, so you could just wait on that, 
potentially with a timeout).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira