[jira] [Commented] (CASSANDRA-15598) cassandra-stress in user profile mode fails on handling set> columns
[ https://issues.apache.org/jira/browse/CASSANDRA-15598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724314#comment-17724314 ] Dmitry Kropachev commented on CASSANDRA-15598: -- [~smiklosovic] , it was dangling for 2 years, not sure it is still actual > cassandra-stress in user profile mode fails on handling set> columns > - > > Key: CASSANDRA-15598 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15598 > Project: Cassandra > Issue Type: Bug > Components: Tool/stress >Reporter: Dmitry Kropachev >Priority: Normal > Fix For: 5.x > > Attachments: cs_no_mv_basic_profile.zip > > Time Spent: 10m > Remaining Estimate: 0h > > Reason: > c-s reads metadata from database, and build column generator from it. > But this logic is build in a way so that it does not support generator > recursion, which is necessary to support embedded collections. > Fix: > This fix is simple exclude this type of columns from being processed. > Steps to reproduce: > # docker run -d --name cassandra cassandra:latest > # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' > cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate > threads=2 -node 172.17.0.2 > # docker exec -ti cassandra cqlsh -e 'ALTER TABLE mview.users ADD ( > asdasdasd set>);' > # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' > cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate > threads=2 -node 172.17.0.2 > Result: > Extra Schema Definitions: null > Generator Configs: > password: Size: Fixed: key=80; > last_name: Size: Uniform: min=1,max=32; > id: Size: Uniform: min=1,max=10; > first_name: Size: Fixed: key=16; > email: Size: Uniform: min=16,max=50; > username: Size: Uniform: min=10,max=30; > Query Definitions: > read1: CQL:select * from mview.users where id = ? LIMIT 10;Fields:samerow; > Token Range Queries: > Insert Settings: > partitions: fixed(1) > batchtype: UNLOGGED > Connected to cluster: , max pending requests per connection 128, max > connections per host 8 > Datacenter: datacenter1; Host: /172.17.0.2:9042; Rack: rack1 > Created schema. Sleeping 1s for propagation. > java.lang.NullPointerException > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:760) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:755) > at > org.apache.cassandra.stress.StressProfile$GeneratorFactory.get(StressProfile.java:733) > at > org.apache.cassandra.stress.StressProfile$GeneratorFactory.newGenerator(StressProfile.java:726) > at > org.apache.cassandra.stress.StressProfile.newGenerator(StressProfile.java:696) > at > org.apache.cassandra.stress.StressProfile.printSettings(StressProfile.java:126) > at > org.apache.cassandra.stress.settings.StressSettings.lambda$printSettings$1(StressSettings.java:311) > at java.util.LinkedHashMap.forEach(LinkedHashMap.java:684) > at > org.apache.cassandra.stress.settings.StressSettings.printSettings(StressSettings.java:311) > at org.apache.cassandra.stress.Stress.run(Stress.java:95) > at org.apache.cassandra.stress.Stress.main(Stress.java:62) -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15034) cassandra-stress fails to retry user profile insert and query operations
[
https://issues.apache.org/jira/browse/CASSANDRA-15034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090329#comment-17090329
]
Dmitry Kropachev commented on CASSANDRA-15034:
--
[~djoshi], It does exactly the same under ccm. in this particular case it does
not matter since all we need is to get metadata read and get an error on CQL
operation from driver level or below.
I'am not trying to hide legitimate exception/error.
With the fix you will still see only "legitamate error", i.e.:
All host(s) tried for query failed (tried: /172.17.0.3:9042
(com.datastax.driver.core.exceptions.UnavailableException: Not enough replicas
available for query at consistency QUORUM (2 required but only 1 alive)))
And what you will not see is tons of these guys:
java.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementException
java.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementException
java.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementException
java.io.IOException: Operation x10 on key(s) [347f2f5b27831048d6f5]: Error
executing: (NoSuchElementException)
at org.apache.cassandra.stress.Operation.error(Operation.java:127)
at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105)
at
org.apache.cassandra.stress.operations.userdefined.SchemaQuery.run(SchemaQuery.java:108)
at org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:466)
These messages are purely internal thing, there is no point to show them to the
people, it is just signaling that there is no records in the partition and it
needs to be reiterated, and it is reiterated but with clumsy error message that
does not tell you anything.
This fix is making these reiterations silent.
And the reason why you would need to hide these meaningless messages is that
when you run c-s in curcumstances of unstable network you can endup with
hundreds of megabytes of output 9/10 of which is totally useless.
Also there are cases when IO error happens once, and operation is silently
retrying, but on the next retry you can hit empty partition case and becasue of
this issue c-s will return -1 at the end, as result of the bug.
This fix fixes this problem to, just making reiteration on empty partition
silently.
> cassandra-stress fails to retry user profile insert and query operations
> -
>
> Key: CASSANDRA-15034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15034
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/stress
>Reporter: Shlomi Livne
>Assignee: Dinesh Joshi
>Priority: Normal
> Attachments: 0001-Fix-retry-of-userdefined-operations.patch,
> stress.yaml
>
>
> cassandra-stress that is run with a user profile against a cluster will fail
> to try operations when a node is killed.
> To reproduce:
> # Create a 3 ndoe cluster with ccm
> {code:java}
> ccm create cas-3 --vnodes -n 1 --version=3.11.3``{code}
> # start the cluster
> {code:java}
> ccm start{code}
> # run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(insert=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> or run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(simple=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> # while the stress is progressing kill a node
> {code:java}
> ccm node1 stop --not-gently{code}
> # wait for cassandra-stress to end
> for the insert case check
> {code:java}
> ccm node2 cqlsh -e " select count(*) FROM stresscql.tb ;"{code}
> we are missing rows
> for the query case (simple) the following errors will be reported
> {code:java}
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.io.IOException: Operation x10 on key(s) [49a26f35297303469236]: Error
> executing: (NoSuchElementException)
> at
> org.apache.cassandra.stress.Operation.error(Operation.java:127)java.util.NoSuchElementException
> at
> org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105)com.datastax.driver.core.exceptions.TransportException:
> [/127.0.0.1:9042] Connection has been closed
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException{code}
> profile: stress.yaml[^stress.yaml]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15034) cassandra-stress fails to retry user profile insert and query operations
[ https://issues.apache.org/jira/browse/CASSANDRA-15034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087675#comment-17087675 ] Dmitry Kropachev commented on CASSANDRA-15034: -- Dinesh, This issue exists in all c-s versions, it is not possible it is being enviromental. Please follow following recepy: 1. docker run --name cassandra cassandra:latest 2. cassandra-stress user profile=stress.yaml n=10 'ops(simple=1)' no-warmup cl=QUORUM -node 172.17.0.3 -rate threads=10 You will get: at org.apache.cassandra.stress.Operation.error(Operation.java:127) at org.apache.cassandra.stress.Operation.error(Operation.java:127) at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) at org.apache.cassandra.stress.operations.userdefined.SchemaQuery.run(SchemaQuery.java:108) at org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:466)java.io.IOException: Operation x10 on key(s) [0bf1ffced038d586fe38]: Error executing: (NoSuchElementException) at org.apache.cassandra.stress.Operation.error(Operation.java:127) at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) at org.apache.cassandra.stress.operations.userdefined.SchemaQuery.run(SchemaQuery.java:108) at org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:466)com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /172.17.0.3:9042 (com.datastax.driver.core.exceptions.UnavailableException: Not enough replicas available for query at consistency QUORUM (2 required but only 1 alive)))java.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.io.IOException: Operation x10 on key(s) [347f2f5b27831048d6f5]: Error executing: (NoSuchElementException) at org.apache.cassandra.stress.Operation.error(Operation.java:127) at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) at org.apache.cassandra.stress.operations.userdefined.SchemaQuery.run(SchemaQuery.java:108) at org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:466)com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /172.17.0.3:9042 (com.datastax.driver.core.exceptions.UnavailableException: Not enough replicas available for query at consistency QUORUM (2 required but only 1 alive)))java.util.NoSuchElementExceptioncom.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /172.17.0.3:9042 (com.datastax.driver.core.exceptions.UnavailableException: Not enough replicas available for query at consistency QUORUM (2 required but only 1 alive)))java.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.util.NoSuchElementExceptionjava.io.IOException: Operation x10 on key(s) [e52ea483e772a62404b5]: Error executing: (NoSuchElementException) at org.apache.cassandra.stress.Operation.error(Operation.java:127) at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) at org.apache.cassandra.stress.operations.userdefined.SchemaQuery.run(SchemaQuery.java:108) at org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:466)java.io.IOException: Operation x10 on key(s) [9ec3a2b7383babcf9d70]: Error executing: (NoSuchElementException) at org.apache.cassandra.stress.Operation.error(Operation.java:127) at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105) at org.apache.cassandra.stress.operations.userdefined.SchemaQuery.run(SchemaQuery.java:108) at org.apache.cassandra.stress.StressAction$Consumer.run(StressAction.java:466) > cassandra-stress fails to retry user profile insert and query operations > - > > Key: CASSANDRA-15034 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15034 > Project: Cassandra > Issue Type: Bug > Components: Tool/stress >Reporter: Shlomi Livne >Assignee: Dinesh Joshi >Priority: Normal > Attachments: 0001-Fix-retry-of-userdefined-operations.patch, > stress.yaml > > > cassandra-stress that is run with a
[jira] [Updated] (CASSANDRA-15735) Add serial consistency option and regular and serial consistency into profile yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-15735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Kropachev updated CASSANDRA-15735: - Description: Needed to be done in order to be able to control serial consistency and regular consistency levels separately. For instance, it was not possible to set serial consistency to LOCAL_SERIAL and regular consistency to QUORUM. We have following code handling it all over the place: if (cl.isSerialConsistency()) statement.setSerialConsistencyLevel(JavaDriverClient.from(cl)); else statement.setConsistencyLevel(JavaDriverClient.from(cl)); With the fix it beacome possible to set serial and regular consistency separately, also it is possible to specify consistency in yaml file per query, in case you want to stress with dirrefent consistency levels, in following manner: lwt_update_one_column: cql: update blogposts set lwt_ind = 1001 where domain = ? and published_date = ? if lwt_ind < 0 fields: samerow consistencyLevel: QUORUM serialConsistencyLevel: LOCAL_SERIAL Fix: [https://github.com/apache/cassandra/pull/540] was: Needed to be done in order to be able to control serial consistency and regular consistency levels separately. For instance, it was not possible to set serial consistency to LOCAL_SERIAL and regular consistency to QUORUM. We have following code handling it all over the place: if (cl.isSerialConsistency()) statement.setSerialConsistencyLevel(JavaDriverClient.from(cl)); else statement.setConsistencyLevel(JavaDriverClient.from(cl)); With the fix it beacome possible to set serial and regular consistency separately, also it is possible to specify consistency in yaml file per query, in case you want to stress with dirrefent consistency levels, in following manner: lwt_update_one_column: cql: update blogposts set lwt_ind = 1001 where domain = ? and published_date = ? if lwt_ind < 0 fields: samerow consistencyLevel: QUORUM serialConsistencyLevel: LOCAL_SERIAL > Add serial consistency option and regular and serial consistency into profile > yaml > -- > > Key: CASSANDRA-15735 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15735 > Project: Cassandra > Issue Type: Bug > Components: Tool/stress >Reporter: Dmitry Kropachev >Priority: Normal > Fix For: 4.x > > Attachments: profile.yaml > > > Needed to be done in order to be able to control serial consistency and > regular consistency levels separately. > For instance, it was not possible to set serial consistency to LOCAL_SERIAL > and regular consistency to QUORUM. > We have following code handling it all over the place: > if (cl.isSerialConsistency()) > statement.setSerialConsistencyLevel(JavaDriverClient.from(cl)); else > statement.setConsistencyLevel(JavaDriverClient.from(cl)); > With the fix it beacome possible to set serial and regular consistency > separately, also it is possible to specify consistency in yaml file per > query, in case you want to stress with dirrefent consistency levels, in > following manner: > lwt_update_one_column: > cql: update blogposts set lwt_ind = 1001 where domain = ? and > published_date = ? if lwt_ind < 0 > fields: samerow > consistencyLevel: QUORUM > serialConsistencyLevel: LOCAL_SERIAL > > Fix: [https://github.com/apache/cassandra/pull/540] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15735) Add serial consistency option and regular and serial consistency into profile yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-15735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Kropachev updated CASSANDRA-15735: - Bug Category: Parent values: Correctness(12982)Level 1 values: API / Semantic Implementation(12988) Complexity: Low Hanging Fruit Discovered By: User Report Fix Version/s: 4.x Severity: Normal > Add serial consistency option and regular and serial consistency into profile > yaml > -- > > Key: CASSANDRA-15735 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15735 > Project: Cassandra > Issue Type: Bug > Components: Tool/stress >Reporter: Dmitry Kropachev >Priority: Normal > Fix For: 4.x > > Attachments: profile.yaml > > > Needed to be done in order to be able to control serial consistency and > regular consistency levels separately. > For instance, it was not possible to set serial consistency to LOCAL_SERIAL > and regular consistency to QUORUM. > We have following code handling it all over the place: > if (cl.isSerialConsistency()) > statement.setSerialConsistencyLevel(JavaDriverClient.from(cl)); else > statement.setConsistencyLevel(JavaDriverClient.from(cl)); > With the fix it beacome possible to set serial and regular consistency > separately, also it is possible to specify consistency in yaml file per > query, in case you want to stress with dirrefent consistency levels, in > following manner: > lwt_update_one_column: > cql: update blogposts set lwt_ind = 1001 where domain = ? and > published_date = ? if lwt_ind < 0 > fields: samerow > consistencyLevel: QUORUM > serialConsistencyLevel: LOCAL_SERIAL > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15735) Add serial consistency option and regular and serial consistency into profile yaml
Dmitry Kropachev created CASSANDRA-15735: Summary: Add serial consistency option and regular and serial consistency into profile yaml Key: CASSANDRA-15735 URL: https://issues.apache.org/jira/browse/CASSANDRA-15735 Project: Cassandra Issue Type: Bug Components: Tool/stress Reporter: Dmitry Kropachev Attachments: profile.yaml Needed to be done in order to be able to control serial consistency and regular consistency levels separately. For instance, it was not possible to set serial consistency to LOCAL_SERIAL and regular consistency to QUORUM. We have following code handling it all over the place: if (cl.isSerialConsistency()) statement.setSerialConsistencyLevel(JavaDriverClient.from(cl)); else statement.setConsistencyLevel(JavaDriverClient.from(cl)); With the fix it beacome possible to set serial and regular consistency separately, also it is possible to specify consistency in yaml file per query, in case you want to stress with dirrefent consistency levels, in following manner: lwt_update_one_column: cql: update blogposts set lwt_ind = 1001 where domain = ? and published_date = ? if lwt_ind < 0 fields: samerow consistencyLevel: QUORUM serialConsistencyLevel: LOCAL_SERIAL -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15034) cassandra-stress fails to retry user profile insert and query operations
[
https://issues.apache.org/jira/browse/CASSANDRA-15034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Kropachev updated CASSANDRA-15034:
-
Reviewers: Dinesh Joshi, Dmitry Kropachev (was: Dinesh Joshi)
Status: Review In Progress (was: Patch Available)
Hello Dinesh,
Could you please take a look at the fix, it is 10 lines of code:
[https://github.com/apache/cassandra/pull/443/files]
> cassandra-stress fails to retry user profile insert and query operations
> -
>
> Key: CASSANDRA-15034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15034
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/stress
>Reporter: Shlomi Livne
>Assignee: Dinesh Joshi
>Priority: Normal
> Attachments: 0001-Fix-retry-of-userdefined-operations.patch,
> stress.yaml
>
>
> cassandra-stress that is run with a user profile against a cluster will fail
> to try operations when a node is killed.
> To reproduce:
> # Create a 3 ndoe cluster with ccm
> {code:java}
> ccm create cas-3 --vnodes -n 1 --version=3.11.3``{code}
> # start the cluster
> {code:java}
> ccm start{code}
> # run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(insert=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> or run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(simple=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> # while the stress is progressing kill a node
> {code:java}
> ccm node1 stop --not-gently{code}
> # wait for cassandra-stress to end
> for the insert case check
> {code:java}
> ccm node2 cqlsh -e " select count(*) FROM stresscql.tb ;"{code}
> we are missing rows
> for the query case (simple) the following errors will be reported
> {code:java}
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.io.IOException: Operation x10 on key(s) [49a26f35297303469236]: Error
> executing: (NoSuchElementException)
> at
> org.apache.cassandra.stress.Operation.error(Operation.java:127)java.util.NoSuchElementException
> at
> org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105)com.datastax.driver.core.exceptions.TransportException:
> [/127.0.0.1:9042] Connection has been closed
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException{code}
> profile: stress.yaml[^stress.yaml]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15598) cassandra-stress in user profile mode fails on handling set> columns
[ https://issues.apache.org/jira/browse/CASSANDRA-15598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17065770#comment-17065770 ] Dmitry Kropachev commented on CASSANDRA-15598: -- Hello Jordan, Please take a look at the patch: https://github.com/apache/cassandra/pull/451/files > cassandra-stress in user profile mode fails on handling set> columns > - > > Key: CASSANDRA-15598 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15598 > Project: Cassandra > Issue Type: Bug > Components: Tool/stress >Reporter: Dmitry Kropachev >Priority: Normal > Fix For: 4.x > > Attachments: cs_no_mv_basic_profile.zip > > > Reason: > c-s reads metadata from database, and build column generator from it. > But this logic is build in a way so that it does not support generator > recursion, which is necessary to support embedded collections. > Fix: > This fix is simple exclude this type of columns from being processed. > Steps to reproduce: > # docker run -d --name cassandra cassandra:latest > # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' > cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate > threads=2 -node 172.17.0.2 > # docker exec -ti cassandra cqlsh -e 'ALTER TABLE mview.users ADD ( > asdasdasd set>);' > # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' > cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate > threads=2 -node 172.17.0.2 > Result: > Extra Schema Definitions: null > Generator Configs: > password: Size: Fixed: key=80; > last_name: Size: Uniform: min=1,max=32; > id: Size: Uniform: min=1,max=10; > first_name: Size: Fixed: key=16; > email: Size: Uniform: min=16,max=50; > username: Size: Uniform: min=10,max=30; > Query Definitions: > read1: CQL:select * from mview.users where id = ? LIMIT 10;Fields:samerow; > Token Range Queries: > Insert Settings: > partitions: fixed(1) > batchtype: UNLOGGED > Connected to cluster: , max pending requests per connection 128, max > connections per host 8 > Datacenter: datacenter1; Host: /172.17.0.2:9042; Rack: rack1 > Created schema. Sleeping 1s for propagation. > java.lang.NullPointerException > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:760) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:755) > at > org.apache.cassandra.stress.StressProfile$GeneratorFactory.get(StressProfile.java:733) > at > org.apache.cassandra.stress.StressProfile$GeneratorFactory.newGenerator(StressProfile.java:726) > at > org.apache.cassandra.stress.StressProfile.newGenerator(StressProfile.java:696) > at > org.apache.cassandra.stress.StressProfile.printSettings(StressProfile.java:126) > at > org.apache.cassandra.stress.settings.StressSettings.lambda$printSettings$1(StressSettings.java:311) > at java.util.LinkedHashMap.forEach(LinkedHashMap.java:684) > at > org.apache.cassandra.stress.settings.StressSettings.printSettings(StressSettings.java:311) > at org.apache.cassandra.stress.Stress.run(Stress.java:95) > at org.apache.cassandra.stress.Stress.main(Stress.java:62) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15598) cassandra-stress in user profile mode fails on handling set> columns
[ https://issues.apache.org/jira/browse/CASSANDRA-15598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Kropachev reassigned CASSANDRA-15598: Assignee: Aleksey Yeschenko > cassandra-stress in user profile mode fails on handling set> columns > - > > Key: CASSANDRA-15598 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15598 > Project: Cassandra > Issue Type: Bug >Reporter: Dmitry Kropachev >Assignee: Aleksey Yeschenko >Priority: Normal > Attachments: cs_no_mv_basic_profile.zip > > > Reason: > c-s reads metadata from database, and build column generator from it. > But this logic is build in a way so that it does not support generator > recursion, which is necessary to support embedded collections. > Fix: > This fix is simple exclude this type of columns from being processed. > Steps to reproduce: > # docker run -d --name cassandra cassandra:latest > # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' > cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate > threads=2 -node 172.17.0.2 > # docker exec -ti cassandra cqlsh -e 'ALTER TABLE mview.users ADD ( > asdasdasd set>);' > # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' > cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate > threads=2 -node 172.17.0.2 > Result: > Extra Schema Definitions: null > Generator Configs: > password: Size: Fixed: key=80; > last_name: Size: Uniform: min=1,max=32; > id: Size: Uniform: min=1,max=10; > first_name: Size: Fixed: key=16; > email: Size: Uniform: min=16,max=50; > username: Size: Uniform: min=10,max=30; > Query Definitions: > read1: CQL:select * from mview.users where id = ? LIMIT 10;Fields:samerow; > Token Range Queries: > Insert Settings: > partitions: fixed(1) > batchtype: UNLOGGED > Connected to cluster: , max pending requests per connection 128, max > connections per host 8 > Datacenter: datacenter1; Host: /172.17.0.2:9042; Rack: rack1 > Created schema. Sleeping 1s for propagation. > java.lang.NullPointerException > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:760) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:755) > at > org.apache.cassandra.stress.StressProfile$GeneratorFactory.get(StressProfile.java:733) > at > org.apache.cassandra.stress.StressProfile$GeneratorFactory.newGenerator(StressProfile.java:726) > at > org.apache.cassandra.stress.StressProfile.newGenerator(StressProfile.java:696) > at > org.apache.cassandra.stress.StressProfile.printSettings(StressProfile.java:126) > at > org.apache.cassandra.stress.settings.StressSettings.lambda$printSettings$1(StressSettings.java:311) > at java.util.LinkedHashMap.forEach(LinkedHashMap.java:684) > at > org.apache.cassandra.stress.settings.StressSettings.printSettings(StressSettings.java:311) > at org.apache.cassandra.stress.Stress.run(Stress.java:95) > at org.apache.cassandra.stress.Stress.main(Stress.java:62) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15598) cassandra-stress in user profile mode fails on handling set> columns
[ https://issues.apache.org/jira/browse/CASSANDRA-15598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Kropachev updated CASSANDRA-15598: - Description: Reason: c-s reads metadata from database, and build column generator from it. But this logic is build in a way so that it does not support generator recursion, which is necessary to support embedded collections. Fix: This fix is simple exclude this type of columns from being processed. Steps to reproduce: # docker run -d --name cassandra cassandra:latest # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate threads=2 -node 172.17.0.2 # docker exec -ti cassandra cqlsh -e 'ALTER TABLE mview.users ADD ( asdasdasd set>);' # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate threads=2 -node 172.17.0.2 Result: Extra Schema Definitions: null Generator Configs: password: Size: Fixed: key=80; last_name: Size: Uniform: min=1,max=32; id: Size: Uniform: min=1,max=10; first_name: Size: Fixed: key=16; email: Size: Uniform: min=16,max=50; username: Size: Uniform: min=10,max=30; Query Definitions: read1: CQL:select * from mview.users where id = ? LIMIT 10;Fields:samerow; Token Range Queries: Insert Settings: partitions: fixed(1) batchtype: UNLOGGED Connected to cluster: , max pending requests per connection 128, max connections per host 8 Datacenter: datacenter1; Host: /172.17.0.2:9042; Rack: rack1 Created schema. Sleeping 1s for propagation. java.lang.NullPointerException at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:760) at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:755) at org.apache.cassandra.stress.StressProfile$GeneratorFactory.get(StressProfile.java:733) at org.apache.cassandra.stress.StressProfile$GeneratorFactory.newGenerator(StressProfile.java:726) at org.apache.cassandra.stress.StressProfile.newGenerator(StressProfile.java:696) at org.apache.cassandra.stress.StressProfile.printSettings(StressProfile.java:126) at org.apache.cassandra.stress.settings.StressSettings.lambda$printSettings$1(StressSettings.java:311) at java.util.LinkedHashMap.forEach(LinkedHashMap.java:684) at org.apache.cassandra.stress.settings.StressSettings.printSettings(StressSettings.java:311) at org.apache.cassandra.stress.Stress.run(Stress.java:95) at org.apache.cassandra.stress.Stress.main(Stress.java:62) was: Reason: c-s reads metadata from database, and build column generator from it. But this logic is build in a way so that it does not support generator recursion, which is necessary to support embedded collections. Fix: This fix is simple exclude this type of columns from being generated. Steps to reproduce: # docker run -d --name cassandra cassandra:latest # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate threads=2 -node 172.17.0.2 # docker exec -ti cassandra cqlsh -e 'ALTER TABLE mview.users ADD ( asdasdasd set>);' # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate threads=2 -node 172.17.0.2 Result: Extra Schema Definitions: null Generator Configs: password: Size: Fixed: key=80; last_name: Size: Uniform: min=1,max=32; id: Size: Uniform: min=1,max=10; first_name: Size: Fixed: key=16; email: Size: Uniform: min=16,max=50; username: Size: Uniform: min=10,max=30; Query Definitions: read1: CQL:select * from mview.users where id = ? LIMIT 10;Fields:samerow; Token Range Queries: Insert Settings: partitions: fixed(1) batchtype: UNLOGGED Connected to cluster: , max pending requests per connection 128, max connections per host 8 Datacenter: datacenter1; Host: /172.17.0.2:9042; Rack: rack1 Created schema. Sleeping 1s for propagation. java.lang.NullPointerException at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:760) at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:755) at org.apache.cassandra.stress.StressProfile$GeneratorFactory.get(StressProfile.java:733) at org.apache.cassandra.stress.StressProfile$GeneratorFactory.newGenerator(StressProfile.java:726) at org.apache.cassandra.stress.StressProfile.newGenerator(StressProfile.java:696)
[jira] [Updated] (CASSANDRA-15598) cassandra-stress in user profile mode fails on handling set> columns
[ https://issues.apache.org/jira/browse/CASSANDRA-15598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Kropachev updated CASSANDRA-15598: - Attachment: cs_no_mv_basic_profile.zip > cassandra-stress in user profile mode fails on handling set> columns > - > > Key: CASSANDRA-15598 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15598 > Project: Cassandra > Issue Type: Bug >Reporter: Dmitry Kropachev >Priority: Normal > Attachments: cs_no_mv_basic_profile.zip > > > Reason: > c-s reads metadata from database, and build column generator from it. > But this logic is build in a way so that it does not support generator > recursion, which is necessary to support embedded collections. > Fix: > This fix is simple exclude this type of columns from being generated. > Steps to reproduce: > # docker run -d --name cassandra cassandra:latest > # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' > cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate > threads=2 -node 172.17.0.2 > # docker exec -ti cassandra cqlsh -e 'ALTER TABLE mview.users ADD ( > asdasdasd set>);' > # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' > cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate > threads=2 -node 172.17.0.2 > Result: > Extra Schema Definitions: null > Generator Configs: > password: Size: Fixed: key=80; > last_name: Size: Uniform: min=1,max=32; > id: Size: Uniform: min=1,max=10; > first_name: Size: Fixed: key=16; > email: Size: Uniform: min=16,max=50; > username: Size: Uniform: min=10,max=30; > Query Definitions: > read1: CQL:select * from mview.users where id = ? LIMIT 10;Fields:samerow; > Token Range Queries: > Insert Settings: > partitions: fixed(1) > batchtype: UNLOGGED > Connected to cluster: , max pending requests per connection 128, max > connections per host 8 > Datacenter: datacenter1; Host: /172.17.0.2:9042; Rack: rack1 > Created schema. Sleeping 1s for propagation. > java.lang.NullPointerException > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:760) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) > at > org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:755) > at > org.apache.cassandra.stress.StressProfile$GeneratorFactory.get(StressProfile.java:733) > at > org.apache.cassandra.stress.StressProfile$GeneratorFactory.newGenerator(StressProfile.java:726) > at > org.apache.cassandra.stress.StressProfile.newGenerator(StressProfile.java:696) > at > org.apache.cassandra.stress.StressProfile.printSettings(StressProfile.java:126) > at > org.apache.cassandra.stress.settings.StressSettings.lambda$printSettings$1(StressSettings.java:311) > at java.util.LinkedHashMap.forEach(LinkedHashMap.java:684) > at > org.apache.cassandra.stress.settings.StressSettings.printSettings(StressSettings.java:311) > at org.apache.cassandra.stress.Stress.run(Stress.java:95) > at org.apache.cassandra.stress.Stress.main(Stress.java:62) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15598) cassandra-stress in user profile mode fails on handling set> columns
Dmitry Kropachev created CASSANDRA-15598: Summary: cassandra-stress in user profile mode fails on handling set> columns Key: CASSANDRA-15598 URL: https://issues.apache.org/jira/browse/CASSANDRA-15598 Project: Cassandra Issue Type: Bug Reporter: Dmitry Kropachev Reason: c-s reads metadata from database, and build column generator from it. But this logic is build in a way so that it does not support generator recursion, which is necessary to support embedded collections. Fix: This fix is simple exclude this type of columns from being generated. Steps to reproduce: # docker run -d --name cassandra cassandra:latest # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate threads=2 -node 172.17.0.2 # docker exec -ti cassandra cqlsh -e 'ALTER TABLE mview.users ADD ( asdasdasd set>);' # cassandra-stress user profile=cs_no_mv_basic_profile.yaml ops'(insert=1)' cl=ONE n=20 -pop seq=1..1000 -port jmx=6868 -mode cql3 native -rate threads=2 -node 172.17.0.2 Result: Extra Schema Definitions: null Generator Configs: password: Size: Fixed: key=80; last_name: Size: Uniform: min=1,max=32; id: Size: Uniform: min=1,max=10; first_name: Size: Fixed: key=16; email: Size: Uniform: min=16,max=50; username: Size: Uniform: min=10,max=30; Query Definitions: read1: CQL:select * from mview.users where id = ? LIMIT 10;Fields:samerow; Token Range Queries: Insert Settings: partitions: fixed(1) batchtype: UNLOGGED Connected to cluster: , max pending requests per connection 128, max connections per host 8 Datacenter: datacenter1; Host: /172.17.0.2:9042; Rack: rack1 Created schema. Sleeping 1s for propagation. java.lang.NullPointerException at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:760) at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:800) at org.apache.cassandra.stress.StressProfile$ColumnInfo.getGenerator(StressProfile.java:755) at org.apache.cassandra.stress.StressProfile$GeneratorFactory.get(StressProfile.java:733) at org.apache.cassandra.stress.StressProfile$GeneratorFactory.newGenerator(StressProfile.java:726) at org.apache.cassandra.stress.StressProfile.newGenerator(StressProfile.java:696) at org.apache.cassandra.stress.StressProfile.printSettings(StressProfile.java:126) at org.apache.cassandra.stress.settings.StressSettings.lambda$printSettings$1(StressSettings.java:311) at java.util.LinkedHashMap.forEach(LinkedHashMap.java:684) at org.apache.cassandra.stress.settings.StressSettings.printSettings(StressSettings.java:311) at org.apache.cassandra.stress.Stress.run(Stress.java:95) at org.apache.cassandra.stress.Stress.main(Stress.java:62) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15034) cassandra-stress fails to retry user profile insert and query operations
[
https://issues.apache.org/jira/browse/CASSANDRA-15034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Kropachev reassigned CASSANDRA-15034:
Assignee: Dinesh Joshi (was: Shlomi Livne)
> cassandra-stress fails to retry user profile insert and query operations
> -
>
> Key: CASSANDRA-15034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15034
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/stress
>Reporter: Shlomi Livne
>Assignee: Dinesh Joshi
>Priority: Normal
> Attachments: 0001-Fix-retry-of-userdefined-operations.patch,
> stress.yaml
>
>
> cassandra-stress that is run with a user profile against a cluster will fail
> to trey operations when a node is killed.
> To reproduce:
> # Create a 3 ndoe cluster with ccm
> {code:java}
> ccm create cas-3 --vnodes -n 1 --version=3.11.3``{code}
> # start the cluster
> {code:java}
> ccm start{code}
> # run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(insert=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> or run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(simple=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> # while the stress is progressing kill a node
> {code:java}
> ccm node1 stop --not-gently{code}
> # wait for cassandra-stress to end
> for the insert case check
> {code:java}
> ccm node2 cqlsh -e " select count(*) FROM stresscql.tb ;"{code}
> we are missing rows
> for the query case (simple) the following errors will be reported
> {code:java}
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.io.IOException: Operation x10 on key(s) [49a26f35297303469236]: Error
> executing: (NoSuchElementException)
> at
> org.apache.cassandra.stress.Operation.error(Operation.java:127)java.util.NoSuchElementException
> at
> org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105)com.datastax.driver.core.exceptions.TransportException:
> [/127.0.0.1:9042] Connection has been closed
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException{code}
> profile: stress.yaml[^stress.yaml]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15034) cassandra-stress fails to retry user profile insert and query operations
[
https://issues.apache.org/jira/browse/CASSANDRA-15034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033517#comment-17033517
]
Dmitry Kropachev commented on CASSANDRA-15034:
--
Fix proposed by Shlomi fixes only one particular case, while this issue can
happen with other type of statements.
Please take a look at more general fix here:
[https://github.com/apache/cassandra/pull/443/files]
> cassandra-stress fails to retry user profile insert and query operations
> -
>
> Key: CASSANDRA-15034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15034
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/stress
>Reporter: Shlomi Livne
>Assignee: Shlomi Livne
>Priority: Normal
> Attachments: 0001-Fix-retry-of-userdefined-operations.patch,
> stress.yaml
>
>
> cassandra-stress that is run with a user profile against a cluster will fail
> to trey operations when a node is killed.
> To reproduce:
> # Create a 3 ndoe cluster with ccm
> {code:java}
> ccm create cas-3 --vnodes -n 1 --version=3.11.3``{code}
> # start the cluster
> {code:java}
> ccm start{code}
> # run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(insert=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> or run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(simple=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> # while the stress is progressing kill a node
> {code:java}
> ccm node1 stop --not-gently{code}
> # wait for cassandra-stress to end
> for the insert case check
> {code:java}
> ccm node2 cqlsh -e " select count(*) FROM stresscql.tb ;"{code}
> we are missing rows
> for the query case (simple) the following errors will be reported
> {code:java}
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.io.IOException: Operation x10 on key(s) [49a26f35297303469236]: Error
> executing: (NoSuchElementException)
> at
> org.apache.cassandra.stress.Operation.error(Operation.java:127)java.util.NoSuchElementException
> at
> org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105)com.datastax.driver.core.exceptions.TransportException:
> [/127.0.0.1:9042] Connection has been closed
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException{code}
> profile: stress.yaml[^stress.yaml]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15034) cassandra-stress fails to retry user profile insert and query operations
[
https://issues.apache.org/jira/browse/CASSANDRA-15034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029596#comment-17029596
]
Dmitry Kropachev edited comment on CASSANDRA-15034 at 2/4/20 6:21 AM:
--
[~djoshi] , could you please look into it, this issue is really annoying.
was (Author: dkropachev):
Dinesh Joshi, could you please look into it, this issue is really annoying.
> cassandra-stress fails to retry user profile insert and query operations
> -
>
> Key: CASSANDRA-15034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15034
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/stress
>Reporter: Shlomi Livne
>Assignee: Shlomi Livne
>Priority: Normal
> Attachments: 0001-Fix-retry-of-userdefined-operations.patch,
> stress.yaml
>
>
> cassandra-stress that is run with a user profile against a cluster will fail
> to trey operations when a node is killed.
> To reproduce:
> # Create a 3 ndoe cluster with ccm
> {code:java}
> ccm create cas-3 --vnodes -n 1 --version=3.11.3``{code}
> # start the cluster
> {code:java}
> ccm start{code}
> # run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(insert=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> or run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(simple=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> # while the stress is progressing kill a node
> {code:java}
> ccm node1 stop --not-gently{code}
> # wait for cassandra-stress to end
> for the insert case check
> {code:java}
> ccm node2 cqlsh -e " select count(*) FROM stresscql.tb ;"{code}
> we are missing rows
> for the query case (simple) the following errors will be reported
> {code:java}
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.io.IOException: Operation x10 on key(s) [49a26f35297303469236]: Error
> executing: (NoSuchElementException)
> at
> org.apache.cassandra.stress.Operation.error(Operation.java:127)java.util.NoSuchElementException
> at
> org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105)com.datastax.driver.core.exceptions.TransportException:
> [/127.0.0.1:9042] Connection has been closed
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException{code}
> profile: stress.yaml[^stress.yaml]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15034) cassandra-stress fails to retry user profile insert and query operations
[
https://issues.apache.org/jira/browse/CASSANDRA-15034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029596#comment-17029596
]
Dmitry Kropachev commented on CASSANDRA-15034:
--
Dinesh Joshi, could you please look into it, this issue is really annoying.
> cassandra-stress fails to retry user profile insert and query operations
> -
>
> Key: CASSANDRA-15034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15034
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/stress
>Reporter: Shlomi Livne
>Assignee: Shlomi Livne
>Priority: Normal
> Attachments: 0001-Fix-retry-of-userdefined-operations.patch,
> stress.yaml
>
>
> cassandra-stress that is run with a user profile against a cluster will fail
> to trey operations when a node is killed.
> To reproduce:
> # Create a 3 ndoe cluster with ccm
> {code:java}
> ccm create cas-3 --vnodes -n 1 --version=3.11.3``{code}
> # start the cluster
> {code:java}
> ccm start{code}
> # run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(insert=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> or run
> {code:java}
> tools/bin/cassandra-stress user profile=stress.yaml n=10 ops(simple=1)
> no-warmup cl=QUORUM -node 127.0.0.2 -rate threads=10{code}
> # while the stress is progressing kill a node
> {code:java}
> ccm node1 stop --not-gently{code}
> # wait for cassandra-stress to end
> for the insert case check
> {code:java}
> ccm node2 cqlsh -e " select count(*) FROM stresscql.tb ;"{code}
> we are missing rows
> for the query case (simple) the following errors will be reported
> {code:java}
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.io.IOException: Operation x10 on key(s) [49a26f35297303469236]: Error
> executing: (NoSuchElementException)
> at
> org.apache.cassandra.stress.Operation.error(Operation.java:127)java.util.NoSuchElementException
> at
> org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:105)com.datastax.driver.core.exceptions.TransportException:
> [/127.0.0.1:9042] Connection has been closed
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException
> java.util.NoSuchElementException{code}
> profile: stress.yaml[^stress.yaml]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
