It is a bug that may happen on MV lock contention and fixed by https://issues.apache.org/jira/browse/CASSANDRA-12689
2016-12-15 7:58 GMT+01:00 안정아 <jungah....@samsung.com>: > Hi, All. > > > > *Issue on MaterializedViews Inserting > > > > environment) 6-cassandra servers 1cluster Version 3.7 JAVA version 1.8 > cassandra java driver 3.1.0 > > data modiling ) column name : ex] A, B, C.... BaseTable((A, B), C), > MV1((A, B), D, E), MV2((A, B), F, G), MV3((A, B), H, I) > > > > details ) I just executed 'insert'(using LWT .ifNotExists()) stress test > on the BaseTable through grinder. > > After 1~2 hours later, (Executed Tests :15,746,227) a cassandra on one > server goes down. > > (It did not go down when I perform the same test with only the BaseTable > without Materialized views) > > The System.log(from the dead cassandra server) prints out the message > below when the server starts going unstable(when the performance starts > jittering). > > It might be similar issue with https://issues.apache.org/ > jira/browse/CASSANDRA-11290 > > But I'm not sure, and the issue is still open. > > > > [ WARN [SharedPool-Worker-92] 2016-12-13 18:21:58,439 > AbstractLocalAwareExecutorService.java:169 - Uncaught exception on thread > Thread[SharedPool-Worker-92,5,main]: {} java.lang.NullPointerException: > null at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:541) > ~[apache-cassandra-3.7.0.jar:3.7.0] at org.apache.cassandra.db. > Keyspace.lambda$apply$74(Keyspace.java:469) > ~[apache-cassandra-3.7.0.jar:3.7.0] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_65] at org.apache.cassandra.concurrent. > AbstractLocalAwareExecutorService$FutureTask.run( > AbstractLocalAwareExecutorService.java:164) > ~[apache-cassandra-3.7.0.jar:3.7.0] > at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) > [apache-cassandra-3.7.0.jar:3.7.0] at java.lang.Thread.run(Thread.java:745) > [na:1.8.0_65] WARN [SharedPool-Worker-12] 2016-12-13 18:21:58,440 > AbstractLocalAwareExecutorService.java:169 - Uncaught exception on thread > Thread[SharedPool-Worker-12,5,main]: {} > org.apache.cassandra.exceptions.WriteTimeoutException: > Operation timed out - received only 0 responses. at org.apache.cassandra.db. > Keyspace.apply(Keyspace.java:460) ~[apache-cassandra-3.7.0.jar:3.7.0] at > org.apache.cassandra.db.Keyspace.lambda$apply$74(Keyspace.java:469) > ~[apache-cassandra-3.7.0.jar:3.7.0] at java.util.concurrent. > Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_65] at > org.apache.cassandra.concurrent.AbstractLocalAwareExecutorServ > ice$FutureTask.run(AbstractLocalAwareExecutorService.java:164) > ~[apache-cassandra-3.7.0.jar:3.7.0] at org.apache.cassandra. > concurrent.SEPWorker.run(SEPWorker.java:105) > [apache-cassandra-3.7.0.jar:3.7.0] at java.lang.Thread.run(Thread.java:745) > [na:1.8.0_65] ] > > > > > > Could this be a bug from MV? or LWT? or both? Thanks! > > > > > > > > > > > > > -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880-6 · Fax +49 7161 304880-1 AG Ulm · HRB 731058 · Managing Director: Jens Kammerer
