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

dan jatnieks reopened CASSANDRA-6777:
-------------------------------------


Re-opening as there does appear to be something to fix in stress to make it 
work with java-driver 2.0.

At the moment the 2.1 branch is using {{cassandra-driver-core-2.0.0-rc3}} but I 
think when this is updated to the release version of 2.0 this error will occur.

See my previous comment for the proposed stress fix to quote the keyspace name 
when calling java-driver {{Metadata#getReplicas}}.


> 2.1 w/java-driver 2.0 and stress write using thrift results in 
> ArithmeticException / by zero errors
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6777
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6777
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>         Environment: Mac OSX, java 1.7.0_51
>            Reporter: dan jatnieks
>            Priority: Minor
>              Labels: stress
>         Attachments: logs.tar.gz
>
>
> Running stress write (thrift) on 2.1 branch is resulting in the following.
> Note: this is after working around 
> [JAVA-276|https://datastax-oss.atlassian.net/browse/JAVA-276] causing stress 
> to fail to connect to 2.1.
> {noformat}
> $ ./tools/bin/cassandra-stress write n=5000000
> Unable to create stress keyspace: Keyspace names must be case-insensitively 
> unique ("Keyspace1" conflicts with "Keyspace1")
> Warming up WRITE with 50000 iterations...
> Connected to cluster: Test Cluster
> Datatacenter: datacenter1; Host: localhost/127.0.0.1; Rack: rack1
> java.lang.ArithmeticException: / by zero
> java.lang.ArithmeticException: / by zero
> java.lang.ArithmeticException: / by zero
> java.lang.ArithmeticException: / by zero
> ...
> java.lang.Arithmjava.io.IOException: Operation [220] x10 key 00000000DD Error 
> executing: (ArithmeticException): / by zero
> eticException: / by zero
> java.lang.ArithmeticException: / by zero
>       at org.apache.cassandra.stress.Operation.error(Operation.java:237)
> java.lang.ArithmeticException: / by zero      at 
> org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:216)
>       at 
> org.apache.cassandra.stress.operations.ThriftInserter.run(ThriftInserter.java:72)
>       at 
> org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:302)java.lang.ArithmeticException:
>  / by zero
> java.lang.ArithmeticException: / by zero
> java.io.IOException: Operation [200] x10 key 00000000C9 Error executing: 
> (ArithmeticException): / by zero
>       at org.apache.cassandra.stress.Operation.error(Operation.java:237)
> java.lang.ArithmeticException: / by zero      at 
> org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:216)
> java.lang.ArithmeticException: / by zero      at 
> org.apache.cassandra.stress.operations.ThriftInserter.run(ThriftInserter.java:72)
>       at 
> org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:302)
> ...
> {noformat}
> Seems to be just a thrift issue, as running stress write using the native 
> protocol works:
> {noformat}
> $ ./tools/bin/cassandra-stress write n=5000000 -mode native cql3
> Unable to create stress keyspace: Keyspace names must be case-insensitively 
> unique ("Keyspace1" conflicts with "Keyspace1")
> Warming up WRITE with 50000 iterations...
> Connected to cluster: Test Cluster
> Datatacenter: datacenter1; Host: localhost/127.0.0.1; Rack: rack1
> Sleeping 2s...
> Running WRITE with 50 threads  for 5000000 iterations
> ops       ,    op/s,adj op/s,   key/s,    mean,     med,     .95,     .99,    
> .999,     max,   time,   stderr
> 29342     ,   29340,   30903,   29340,     1.7,     1.4,     3.1,     5.7,    
> 51.5,    54.4,    1.0,  0.00000
> 56353     ,   26968,   28523,   26968,     1.8,     1.5,     3.6,     7.0,    
> 56.5,    57.2,    2.0,  0.00000
> ...
> 5000000   ,   29358,   29358,   29358,     1.7,     1.3,     3.6,     8.4,    
> 10.1,    11.6,  168.8,  0.00828
> Results:
> real op rate              : 29620
> adjusted op rate          : 29629
> adjusted op rate stderr   : 0
> key rate                  : 29620
> latency mean              : 1.7
> latency median            : 1.4
> latency 95th percentile   : 3.0
> latency 99th percentile   : 5.4
> latency 99.9th percentile : 56.5
> latency max               : 305.7
> Total operation time      : 00:02:48
> END
> {noformat}
> Attaching stress write and system logs as well.



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

Reply via email to