[jira] [Updated] (CASSANDRA-17307) Test Failure: org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV30Test.testAvailability
[
https://issues.apache.org/jira/browse/CASSANDRA-17307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-17307:
Status: Ready to Commit (was: Review In Progress)
> Test Failure:
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV30Test.testAvailability
>
>
> Key: CASSANDRA-17307
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17307
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Josh McKenzie
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 4.1-beta, 4.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> No known failures. Flakiness 0%, Stability 100%
> Error Message
> Unexpected error while reading in case write-read consistency QUORUM-QUORUM
> with not upgraded coordinator and 1 nodes down
> {code}
> Stacktrace
> junit.framework.AssertionFailedError: Unexpected error while reading in case
> write-read consistency QUORUM-QUORUM with not upgraded coordinator and 1
> nodes down
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.test(MixedModeAvailabilityTestBase.java:142)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$2(MixedModeAvailabilityTestBase.java:91)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:231)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:93)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:62)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:56)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV30Test.testAvailability(MixedModeAvailabilityV30Test.java:33)
> Caused by: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses.
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.waitOn(IsolatedExecutor.java:218)
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.lambda$sync$5(IsolatedExecutor.java:109)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeWithResult(Coordinator.java:69)
> at
> org.apache.cassandra.distributed.api.ICoordinator.execute(ICoordinator.java:32)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.lambda$test$1(MixedModeAvailabilityTestBase.java:135)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.maybeFail(MixedModeAvailabilityTestBase.java:155)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.test(MixedModeAvailabilityTestBase.java:134)
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation
> timed out - received only 1 responses.
> at
> org.apache.cassandra.service.ReadCallback.awaitResults(ReadCallback.java:136)
> at org.apache.cassandra.service.ReadCallback.get(ReadCallback.java:142)
> at
> org.apache.cassandra.service.AbstractReadExecutor.get(AbstractReadExecutor.java:145)
> at
> org.apache.cassandra.service.StorageProxy$SinglePartitionReadLifecycle.awaitResultsAndRetryOnDigestMismatch(StorageProxy.java:1833)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:1782)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1720)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1629)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1166)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:302)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:263)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:115)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeInternal(Coordinator.java:107)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:69)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
>
[jira] [Commented] (CASSANDRA-17307) Test Failure: org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV30Test.testAvailability
[
https://issues.apache.org/jira/browse/CASSANDRA-17307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562373#comment-17562373
]
Berenguer Blasi commented on CASSANDRA-17307:
-
LGTM +1
> Test Failure:
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV30Test.testAvailability
>
>
> Key: CASSANDRA-17307
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17307
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Josh McKenzie
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 4.1-beta, 4.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> No known failures. Flakiness 0%, Stability 100%
> Error Message
> Unexpected error while reading in case write-read consistency QUORUM-QUORUM
> with not upgraded coordinator and 1 nodes down
> {code}
> Stacktrace
> junit.framework.AssertionFailedError: Unexpected error while reading in case
> write-read consistency QUORUM-QUORUM with not upgraded coordinator and 1
> nodes down
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.test(MixedModeAvailabilityTestBase.java:142)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$2(MixedModeAvailabilityTestBase.java:91)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:231)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:93)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:62)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:56)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV30Test.testAvailability(MixedModeAvailabilityV30Test.java:33)
> Caused by: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses.
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.waitOn(IsolatedExecutor.java:218)
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.lambda$sync$5(IsolatedExecutor.java:109)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeWithResult(Coordinator.java:69)
> at
> org.apache.cassandra.distributed.api.ICoordinator.execute(ICoordinator.java:32)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.lambda$test$1(MixedModeAvailabilityTestBase.java:135)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.maybeFail(MixedModeAvailabilityTestBase.java:155)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.test(MixedModeAvailabilityTestBase.java:134)
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation
> timed out - received only 1 responses.
> at
> org.apache.cassandra.service.ReadCallback.awaitResults(ReadCallback.java:136)
> at org.apache.cassandra.service.ReadCallback.get(ReadCallback.java:142)
> at
> org.apache.cassandra.service.AbstractReadExecutor.get(AbstractReadExecutor.java:145)
> at
> org.apache.cassandra.service.StorageProxy$SinglePartitionReadLifecycle.awaitResultsAndRetryOnDigestMismatch(StorageProxy.java:1833)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:1782)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1720)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1629)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1166)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:302)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:263)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:115)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeInternal(Coordinator.java:107)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:69)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
>
[jira] [Comment Edited] (CASSANDRA-17729) Raise test timeouts
[ https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562364#comment-17562364 ] Berenguer Blasi edited comment on CASSANDRA-17729 at 7/5/22 4:39 AM: - ||Branch||Jenkins||Circle|| |[4.1 branch|http://example.com]|[CI jenkins|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch/1822/]|[CI circle|https://app.circleci.com/pipelines/github/bereng/cassandra/694/workflows/c08784ea-a9c8-49d5-abd9-0339f2338280]| was (Author: bereng): ||Branch 1||Jenkins||Circle|| |[4.1 branch|http://example.com]|[CI jenkins|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch/1822/]|[CI circle|https://app.circleci.com/pipelines/github/bereng/cassandra/694/workflows/c08784ea-a9c8-49d5-abd9-0339f2338280]| > Raise test timeouts > --- > > Key: CASSANDRA-17729 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17729 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.1-beta > > > We have seen for some time now junits timeout frequently on jenkins. This is > probably down to it being a very loaded env. On circle we don't observe that > behavior probably bc it's not so loaded. > The question is whether it is time to raise timeouts as they might be hiding > legit failures. As en experiment I raised timeouts in a branch and ran > jenkins against it. What I see is that the last 4.1 run had 14 failures out > of which 12 were timeouts. Increasing timeouts reveals what looks to be 9 > legit failures where 2 are timeouts that probably need to be investigated. -- 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-17729) Raise test timeouts
[ https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562364#comment-17562364 ] Berenguer Blasi commented on CASSANDRA-17729: - ||Branch 1||Jenkins||Circle|| |[4.1 branch|http://example.com]|[CI jenkins|https://ci-cassandra.apache.org/view/all/job/Cassandra-devbranch/1822/]|[CI circle|https://app.circleci.com/pipelines/github/bereng/cassandra/694/workflows/c08784ea-a9c8-49d5-abd9-0339f2338280]| > Raise test timeouts > --- > > Key: CASSANDRA-17729 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17729 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.1-beta > > > We have seen for some time now junits timeout frequently on jenkins. This is > probably down to it being a very loaded env. On circle we don't observe that > behavior probably bc it's not so loaded. > The question is whether it is time to raise timeouts as they might be hiding > legit failures. As en experiment I raised timeouts in a branch and ran > jenkins against it. What I see is that the last 4.1 run had 14 failures out > of which 12 were timeouts. Increasing timeouts reveals what looks to be 9 > legit failures where 2 are timeouts that probably need to be investigated. -- 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] [Updated] (CASSANDRA-17729) Raise test timeouts
[ https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-17729: Bug Category: Parent values: Degradation(12984) Complexity: Normal Discovered By: Unit Test Fix Version/s: 4.1-beta Severity: Normal Status: Open (was: Triage Needed) > Raise test timeouts > --- > > Key: CASSANDRA-17729 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17729 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.1-beta > > > We have seen for some time now junits timeout frequently on jenkins. This is > probably down to it being a very loaded env. On circle we don't observe that > behavior probably bc it's not so loaded. > The question is whether it is time to raise timeouts as they might be hiding > legit failures. As en experiment I raised timeouts in a branch and ran > jenkins against it. What I see is that the last 4.1 run had 14 failures out > of which 12 were timeouts. Increasing timeouts reveals what looks to be 9 > legit failures where 2 are timeouts that probably need to be investigated. -- 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] [Created] (CASSANDRA-17729) Raise test timeouts
Berenguer Blasi created CASSANDRA-17729: --- Summary: Raise test timeouts Key: CASSANDRA-17729 URL: https://issues.apache.org/jira/browse/CASSANDRA-17729 Project: Cassandra Issue Type: Bug Components: Test/unit Reporter: Berenguer Blasi Assignee: Berenguer Blasi We have seen for some time now junits timeout frequently on jenkins. This is probably down to it being a very loaded env. On circle we don't observe that behavior probably bc it's not so loaded. The question is whether it is time to raise timeouts as they might be hiding legit failures. As en experiment I raised timeouts in a branch and ran jenkins against it. What I see is that the last 4.1 run had 14 failures out of which 12 were timeouts. Increasing timeouts reveals what looks to be 9 legit failures where 2 are timeouts that probably need to be investigated. -- 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-16911) Remove ephemeral snapshot marker file and introduce a flag to SnapshotManifest
[ https://issues.apache.org/jira/browse/CASSANDRA-16911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562187#comment-17562187 ] Stefan Miklosovic commented on CASSANDRA-16911: --- I have incorporated feedback from the review, I have added tests as well as requested. I went with different approach though. I made ephemeral column hidden when "-e" is not specified. [~paulo] would you please take a look? CI https://app.circleci.com/pipelines/github/instaclustr/cassandra/1120/workflows/742a28c3-fdc8-4868-8d81-d25d946c53a1 > Remove ephemeral snapshot marker file and introduce a flag to SnapshotManifest > -- > > Key: CASSANDRA-16911 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16911 > Project: Cassandra > Issue Type: Improvement > Components: Local/Snapshots >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.2 > > Time Spent: 4h 40m > Remaining Estimate: 0h > > While creating an ephemeral snapshot, a marker file is created at disk in a > respective snapshot directory. This is not necessary anymore as we have > introduced SnapshotManifest in CASSANDRA-16789 so we can move this flag > there. By putting the information if a snapshot is ephemeral or not into > SnapshotManifest, we simplify and "clean up" the snapshotting process and > related codebase. -- 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] [Updated] (CASSANDRA-17728) cassandra.service: main process exited, code=killed, status=11/SEGV
[
https://issues.apache.org/jira/browse/CASSANDRA-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17728:
-
Resolution: Invalid
Status: Resolved (was: Triage Needed)
This jira is for the development of Apache Cassandra and makes a poor vehicle
for support. I recommend contacting the community on slack or the ML for
better assistance: https://cassandra.apache.org/_/community.html
> cassandra.service: main process exited, code=killed, status=11/SEGV
> ---
>
> Key: CASSANDRA-17728
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17728
> Project: Cassandra
> Issue Type: Bug
>Reporter: dingguoxing
>Priority: Normal
>
> env:
> apache-cassandra-4.0.0
> jdk-11.0.12
> ZGC
>
> jvm:
> -Xms31G
> -Xmx31G
>
> host:
> 16core 128G
>
> message log:
> {code:java}
> Jul 4 13:57:10 iZ2zec1q29sosy4bdv893qZ systemd-logind: Removed session 277.
> Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO
> [CompactionExecutor:4] 2022-07-04 13:57:12,074 CompactionTask.java:245 -
> Compacted (24af5250-fb5e-11ec-aa2a-6b96728ba428)
> 4 sstables to
> [/data/cassandra/data/data/spaceport/xm_coupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6494-big,]
> to level=0. 27.414MiB to 27.412MiB (~99% of original) i
> n 1,812ms. Read Throughput = 15.127MiB/s, Write Throughput = 15.126MiB/s,
> Row Throughput = ~123,625/s. 32,718 total partitions merged to 32,689.
> Partition merge counts were {1:
> 32663, 2:23, 3:3, }
> Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
> 2022-07-04 13:57:12,083 SSTable.java:111 - Deleting sstable:
> /data/cassandra/data/data/spaceport/xm_c
> oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6490-big
> Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
> 2022-07-04 13:57:12,084 SSTable.java:111 - Deleting sstable:
> /data/cassandra/data/data/spaceport/xm_c
> oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6493-big
> Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
> 2022-07-04 13:57:12,085 SSTable.java:111 - Deleting sstable:
> /data/cassandra/data/data/spaceport/xm_c
> oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6491-big
> Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
> 2022-07-04 13:57:12,085 SSTable.java:111 - Deleting sstable:
> /data/cassandra/data/data/spaceport/xm_c
> oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6492-big
> Jul 4 14:00:01 iZ2zec1q29sosy4bdv893qZ systemd: Started Session 293 of user
> root.
> Jul 4 14:01:01 iZ2zec1q29sosy4bdv893qZ systemd: Started Session 294 of user
> root.
> Jul 4 14:01:59 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service: main
> process exited, code=killed, status=11/SEGV
> Jul 4 14:02:00 iZ2zec1q29sosy4bdv893qZ systemd: Unit cassandra.service
> entered failed state.
> Jul 4 14:02:00 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service failed.
> Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service holdoff
> time over, scheduling restart.
> Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: Stopped Cassandra Server
> Service.
> Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: Started Cassandra Server
> Service.
> Jul 4 14:02:55 iZ2zec1q29sosy4bdv893qZ cassandra: CompileCommand: dontinline
> org/apache/cassandra/db/Columns$Serializer.deserializeLargeSubset(Lorg/apache/cassandra/io/util/DataI
> nputPlus;Lorg/apache/cassandra/db/Columns;I)Lorg/apache/cassandra/db/Columns;
> {code}
--
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] [Updated] (CASSANDRA-17728) cassandra.service: main process exited, code=killed, status=11/SEGV
[
https://issues.apache.org/jira/browse/CASSANDRA-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17728:
-
Epic Link: (was: CASSANDRA-17089)
> cassandra.service: main process exited, code=killed, status=11/SEGV
> ---
>
> Key: CASSANDRA-17728
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17728
> Project: Cassandra
> Issue Type: Bug
>Reporter: dingguoxing
>Priority: Normal
>
> env:
> apache-cassandra-4.0.0
> jdk-11.0.12
> ZGC
>
> jvm:
> -Xms31G
> -Xmx31G
>
> host:
> 16core 128G
>
> message log:
> {code:java}
> Jul 4 13:57:10 iZ2zec1q29sosy4bdv893qZ systemd-logind: Removed session 277.
> Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO
> [CompactionExecutor:4] 2022-07-04 13:57:12,074 CompactionTask.java:245 -
> Compacted (24af5250-fb5e-11ec-aa2a-6b96728ba428)
> 4 sstables to
> [/data/cassandra/data/data/spaceport/xm_coupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6494-big,]
> to level=0. 27.414MiB to 27.412MiB (~99% of original) i
> n 1,812ms. Read Throughput = 15.127MiB/s, Write Throughput = 15.126MiB/s,
> Row Throughput = ~123,625/s. 32,718 total partitions merged to 32,689.
> Partition merge counts were {1:
> 32663, 2:23, 3:3, }
> Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
> 2022-07-04 13:57:12,083 SSTable.java:111 - Deleting sstable:
> /data/cassandra/data/data/spaceport/xm_c
> oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6490-big
> Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
> 2022-07-04 13:57:12,084 SSTable.java:111 - Deleting sstable:
> /data/cassandra/data/data/spaceport/xm_c
> oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6493-big
> Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
> 2022-07-04 13:57:12,085 SSTable.java:111 - Deleting sstable:
> /data/cassandra/data/data/spaceport/xm_c
> oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6491-big
> Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
> 2022-07-04 13:57:12,085 SSTable.java:111 - Deleting sstable:
> /data/cassandra/data/data/spaceport/xm_c
> oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6492-big
> Jul 4 14:00:01 iZ2zec1q29sosy4bdv893qZ systemd: Started Session 293 of user
> root.
> Jul 4 14:01:01 iZ2zec1q29sosy4bdv893qZ systemd: Started Session 294 of user
> root.
> Jul 4 14:01:59 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service: main
> process exited, code=killed, status=11/SEGV
> Jul 4 14:02:00 iZ2zec1q29sosy4bdv893qZ systemd: Unit cassandra.service
> entered failed state.
> Jul 4 14:02:00 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service failed.
> Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service holdoff
> time over, scheduling restart.
> Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: Stopped Cassandra Server
> Service.
> Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: Started Cassandra Server
> Service.
> Jul 4 14:02:55 iZ2zec1q29sosy4bdv893qZ cassandra: CompileCommand: dontinline
> org/apache/cassandra/db/Columns$Serializer.deserializeLargeSubset(Lorg/apache/cassandra/io/util/DataI
> nputPlus;Lorg/apache/cassandra/db/Columns;I)Lorg/apache/cassandra/db/Columns;
> {code}
--
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-17232) org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562105#comment-17562105
]
Berenguer Blasi commented on CASSANDRA-17232:
-
Ok so all failures now are on the commit log not having stopped so we can see
we were dealing with side effects and a common root. Let me dig a bit more why
it won't stop even in 5 minutes...
> org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
> ---
>
> Key: CASSANDRA-17232
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17232
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> I saw
> [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3_/]
> and
> [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/881/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3__compression_3/]
> the same assertion failure:
>
> {code:java}
> org.apache.cassandra.db.commitlog.GroupCommitLogTest.replayWithDiscard[3]
> Error Message
> expected:<204> but was:<0>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<204> but was:<0> at
> org.apache.cassandra.db.commitlog.CommitLogTest.replayWithDiscard(CommitLogTest.java:883)
> {code}
>
> Then I find that there are many other tests from GroupCommitLogTest failing
> with No such file found.
> Example:
> https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/
--
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-17232) org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562093#comment-17562093
]
Berenguer Blasi commented on CASSANDRA-17232:
-
I am going to do [1
run|https://app.circleci.com/pipelines/github/bereng/cassandra/695/workflows/7170244e-3d61-43de-ad62-2c8c840cc976]
failing if {{awaitTermination}} doesn't succeed so we can know if these 2 diff
errors are related or not.
> org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
> ---
>
> Key: CASSANDRA-17232
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17232
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> I saw
> [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3_/]
> and
> [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/881/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3__compression_3/]
> the same assertion failure:
>
> {code:java}
> org.apache.cassandra.db.commitlog.GroupCommitLogTest.replayWithDiscard[3]
> Error Message
> expected:<204> but was:<0>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<204> but was:<0> at
> org.apache.cassandra.db.commitlog.CommitLogTest.replayWithDiscard(CommitLogTest.java:883)
> {code}
>
> Then I find that there are many other tests from GroupCommitLogTest failing
> with No such file found.
> Example:
> https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/
--
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] [Created] (CASSANDRA-17728) cassandra.service: main process exited, code=killed, status=11/SEGV
dingguoxing created CASSANDRA-17728:
---
Summary: cassandra.service: main process exited, code=killed,
status=11/SEGV
Key: CASSANDRA-17728
URL: https://issues.apache.org/jira/browse/CASSANDRA-17728
Project: Cassandra
Issue Type: Bug
Reporter: dingguoxing
env:
apache-cassandra-4.0.0
jdk-11.0.12
ZGC
jvm:
-Xms31G
-Xmx31G
host:
16core 128G
message log:
{code:java}
Jul 4 13:57:10 iZ2zec1q29sosy4bdv893qZ systemd-logind: Removed session 277.
Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [CompactionExecutor:4]
2022-07-04 13:57:12,074 CompactionTask.java:245 - Compacted
(24af5250-fb5e-11ec-aa2a-6b96728ba428)
4 sstables to
[/data/cassandra/data/data/spaceport/xm_coupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6494-big,]
to level=0. 27.414MiB to 27.412MiB (~99% of original) i
n 1,812ms. Read Throughput = 15.127MiB/s, Write Throughput = 15.126MiB/s, Row
Throughput = ~123,625/s. 32,718 total partitions merged to 32,689. Partition
merge counts were {1:
32663, 2:23, 3:3, }
Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
2022-07-04 13:57:12,083 SSTable.java:111 - Deleting sstable:
/data/cassandra/data/data/spaceport/xm_c
oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6490-big
Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
2022-07-04 13:57:12,084 SSTable.java:111 - Deleting sstable:
/data/cassandra/data/data/spaceport/xm_c
oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6493-big
Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
2022-07-04 13:57:12,085 SSTable.java:111 - Deleting sstable:
/data/cassandra/data/data/spaceport/xm_c
oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6491-big
Jul 4 13:57:12 iZ2zec1q29sosy4bdv893qZ cassandra: INFO [NonPeriodicTasks:1]
2022-07-04 13:57:12,085 SSTable.java:111 - Deleting sstable:
/data/cassandra/data/data/spaceport/xm_c
oupon_code_realtime1-d77e7f10ebcc11ecae252faeea3c28c4/nb-6492-big
Jul 4 14:00:01 iZ2zec1q29sosy4bdv893qZ systemd: Started Session 293 of user
root.
Jul 4 14:01:01 iZ2zec1q29sosy4bdv893qZ systemd: Started Session 294 of user
root.
Jul 4 14:01:59 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service: main
process exited, code=killed, status=11/SEGV
Jul 4 14:02:00 iZ2zec1q29sosy4bdv893qZ systemd: Unit cassandra.service entered
failed state.
Jul 4 14:02:00 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service failed.
Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: cassandra.service holdoff time
over, scheduling restart.
Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: Stopped Cassandra Server
Service.
Jul 4 14:02:05 iZ2zec1q29sosy4bdv893qZ systemd: Started Cassandra Server
Service.
Jul 4 14:02:55 iZ2zec1q29sosy4bdv893qZ cassandra: CompileCommand: dontinline
org/apache/cassandra/db/Columns$Serializer.deserializeLargeSubset(Lorg/apache/cassandra/io/util/DataI
nputPlus;Lorg/apache/cassandra/db/Columns;I)Lorg/apache/cassandra/db/Columns;
{code}
--
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-16911) Remove ephemeral snapshot marker file and introduce a flag to SnapshotManifest
[ https://issues.apache.org/jira/browse/CASSANDRA-16911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562033#comment-17562033 ] Stefan Miklosovic commented on CASSANDRA-16911: --- If we want to control whether we want to display that column or not, I think that is technically possible to do as we would just "drop displaying the last column while constructing the output" for nodetool however keep in mind that when it comes to what JMX returns, it will contain that information too. We would just somehow not display it by default. Anyway, what qualifies for the output to be "too long"? Do we follow some measurable policy here? Everybody has screens of a different width and I do not know what consitues the output to be "too wide". There is not one answer to that. We might indeed stick to "80 chars" as that is kind of default on the terminal but I think we already passed this limit and the measurement is more or less just subjective here. > Remove ephemeral snapshot marker file and introduce a flag to SnapshotManifest > -- > > Key: CASSANDRA-16911 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16911 > Project: Cassandra > Issue Type: Improvement > Components: Local/Snapshots >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.2 > > Time Spent: 4.5h > Remaining Estimate: 0h > > While creating an ephemeral snapshot, a marker file is created at disk in a > respective snapshot directory. This is not necessary anymore as we have > introduced SnapshotManifest in CASSANDRA-16789 so we can move this flag > there. By putting the information if a snapshot is ephemeral or not into > SnapshotManifest, we simplify and "clean up" the snapshotting process and > related codebase. -- 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] [Updated] (CASSANDRA-17723) Add support for big endian architecture (s390x)
[ https://issues.apache.org/jira/browse/CASSANDRA-17723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shahid Shaikh updated CASSANDRA-17723: -- Component/s: Legacy/Observability Legacy/Testing (was: Test/unit) > Add support for big endian architecture (s390x) > --- > > Key: CASSANDRA-17723 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17723 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Observability, Legacy/Testing >Reporter: Shahid Shaikh >Priority: Normal > Fix For: 4.x > > Attachments: cassandra_patch_file.patch > > > Noticed that some of the Cassandra tests are failing on big endian > architectures (s390x). Please find the attached code patch which corrects the > data handling for big endian architecture. It also corrects the byte ordering > when dealing with sun.misc.Unsafe methods. After the patch following tests > are passing for s390x which were failing earlier: > TTLTest > ScrubTest > LegacySSTableTest > SSTableExportSchemaLoadingTest > SSTableMetadataViewerTest > StandaloneUpgraderOnSStablesTest > StandaloneVerifierOnSSTablesTest > The code change ensures that Cassandra for little endian architectures remain > unaffected. > -- 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-17310) Test Failure: org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV3XTest.testAvailability
[
https://issues.apache.org/jira/browse/CASSANDRA-17310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17562020#comment-17562020
]
Berenguer Blasi commented on CASSANDRA-17310:
-
Having started the review of CASSANDRA-17307 I agree they are the same root
cause and this one is a dup.
> Test Failure:
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV3XTest.testAvailability
>
>
> Key: CASSANDRA-17310
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17310
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Josh McKenzie
>Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> https://ci-cassandra.apache.org/job/Cassandra-4.0/312/testReport/org.apache.cassandra.distributed.upgrade/MixedModeAvailabilityV3XTest/testAvailability/
> Failed 1 times in the last 5 runs. Flakiness: 25%, Stability: 80%
> Error Message
> Unexpected error while reading in case write-read consistency ONE-ALL with
> upgraded coordinator and 2 nodes down
> {code}
> Stacktrace
> junit.framework.AssertionFailedError: Unexpected error while reading in case
> write-read consistency ONE-ALL with upgraded coordinator and 2 nodes down
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.test(MixedModeAvailabilityTestBase.java:142)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$2(MixedModeAvailabilityTestBase.java:91)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:231)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:93)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:61)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:56)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV3XTest.testAvailability(MixedModeAvailabilityV3XTest.java:33)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.maybeFail(MixedModeAvailabilityTestBase.java:166)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.test(MixedModeAvailabilityTestBase.java:134)
> {code}
--
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] [Updated] (CASSANDRA-17307) Test Failure: org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV30Test.testAvailability
[
https://issues.apache.org/jira/browse/CASSANDRA-17307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-17307:
Reviewers: Berenguer Blasi, Berenguer Blasi
Berenguer Blasi, Berenguer Blasi (was: Berenguer Blasi,
Berenguer Blasi)
Status: Review In Progress (was: Patch Available)
> Test Failure:
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV30Test.testAvailability
>
>
> Key: CASSANDRA-17307
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17307
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Josh McKenzie
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 4.1-beta, 4.x
>
>
> No known failures. Flakiness 0%, Stability 100%
> Error Message
> Unexpected error while reading in case write-read consistency QUORUM-QUORUM
> with not upgraded coordinator and 1 nodes down
> {code}
> Stacktrace
> junit.framework.AssertionFailedError: Unexpected error while reading in case
> write-read consistency QUORUM-QUORUM with not upgraded coordinator and 1
> nodes down
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.test(MixedModeAvailabilityTestBase.java:142)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.lambda$testAvailability$2(MixedModeAvailabilityTestBase.java:91)
> at
> org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.run(UpgradeTestBase.java:231)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:93)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:62)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase.testAvailability(MixedModeAvailabilityTestBase.java:56)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityV30Test.testAvailability(MixedModeAvailabilityV30Test.java:33)
> Caused by: java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out -
> received only 1 responses.
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.waitOn(IsolatedExecutor.java:218)
> at
> org.apache.cassandra.distributed.impl.IsolatedExecutor.lambda$sync$5(IsolatedExecutor.java:109)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeWithResult(Coordinator.java:69)
> at
> org.apache.cassandra.distributed.api.ICoordinator.execute(ICoordinator.java:32)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.lambda$test$1(MixedModeAvailabilityTestBase.java:135)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.maybeFail(MixedModeAvailabilityTestBase.java:155)
> at
> org.apache.cassandra.distributed.upgrade.MixedModeAvailabilityTestBase$Tester.test(MixedModeAvailabilityTestBase.java:134)
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation
> timed out - received only 1 responses.
> at
> org.apache.cassandra.service.ReadCallback.awaitResults(ReadCallback.java:136)
> at org.apache.cassandra.service.ReadCallback.get(ReadCallback.java:142)
> at
> org.apache.cassandra.service.AbstractReadExecutor.get(AbstractReadExecutor.java:145)
> at
> org.apache.cassandra.service.StorageProxy$SinglePartitionReadLifecycle.awaitResultsAndRetryOnDigestMismatch(StorageProxy.java:1833)
> at
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:1782)
> at
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1720)
> at
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1629)
> at
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:1166)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:302)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:263)
> at
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:115)
> at
> org.apache.cassandra.distributed.impl.Coordinator.executeInternal(Coordinator.java:107)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:69)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
>
