[jira] [Commented] (CASSANDRA-17005) Fix test dtest.repair_tests.incremental_repair_test.TestIncRepair.test_multiple_repair
[
https://issues.apache.org/jira/browse/CASSANDRA-17005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609818#comment-17609818
]
Berenguer Blasi commented on CASSANDRA-17005:
-
Added to the CASSANDRA-17321 bucket list for starters. Do you guys think we
should reopen it or is that 'enough'?
> Fix test
> dtest.repair_tests.incremental_repair_test.TestIncRepair.test_multiple_repair
> --
>
> Key: CASSANDRA-17005
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17005
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.0.x, 4.1
>
>
> [dtest.repair_tests.incremental_repair_test.TestIncRepair.test_multiple_repair|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1143/testReport/junit/dtest.repair_tests.incremental_repair_test/TestIncRepair/test_multiple_repair/]
> is flaky:
> h3.
> {code:java}
> Error Message
> cassandra.OperationTimedOut: errors={'127.0.0.2:9042': 'Client request
> timeout. See Session.execute[_async](timeout)'}, last_host=127.0.0.2:9042
> Stacktrace
> self = 0x7ff52f4f4fd0> def test_multiple_repair(self): """ * Launch a three node
> cluster * Create a keyspace with RF 3 and a table * Insert 49 rows * Stop
> node3 * Insert 50 more rows * Restart node3 * Issue an incremental repair on
> node3 * Stop node2 * Insert a final50 rows * Restart node2 * Issue an
> incremental repair on node2 * Replace node3 with a new node * Verify data
> integrity # TODO: Several more verifications of data need to be interspersed
> throughout the test. The final assertion is insufficient. @jira_ticket
> CASSANDRA-10644 """ cluster = self.cluster cluster.populate(3).start() node1,
> node2, node3 = cluster.nodelist() session =
> self.patient_cql_connection(node1) create_ks(session, 'ks', 3) if
> cluster.version() < '4.0': create_cf(session, 'cf', read_repair=0.0,
> columns={'c1': 'text', 'c2': 'text'}) else: create_cf(session, 'cf',
> columns={'c1': 'text', 'c2': 'text'}) logger.debug("insert data")
> insert_c1c2(session, keys=list(range(1, 50)),
> consistency=ConsistencyLevel.ALL) node1.flush() logger.debug("bringing down
> node 3") node3.flush() node3.stop(gently=False) logger.debug("inserting
> additional data into node 1 and 2") insert_c1c2(session, keys=list(range(50,
> 100)), consistency=ConsistencyLevel.TWO) node1.flush() node2.flush()
> logger.debug("restarting and repairing node 3")
> node3.start(wait_for_binary_proto=True) if cluster.version() >= "2.2":
> node3.repair() else: node3.nodetool("repair -par -inc") # wait stream
> handlers to be closed on windows # after session is finished (See
> CASSANDRA-10644) if is_win: time.sleep(2) logger.debug("stopping node 2")
> node2.stop(gently=False) logger.debug("inserting data in nodes 1 and 3")
> insert_c1c2(session, keys=list(range(100, 150)),
> consistency=ConsistencyLevel.TWO) node1.flush() node3.flush()
> logger.debug("start and repair node 2")
> node2.start(wait_for_binary_proto=True) if cluster.version() >= "2.2":
> node2.repair() else: node2.nodetool("repair -par -inc") logger.debug("replace
> node and check data integrity") node3.stop(gently=False) node5 =
> Node('node5', cluster, True, ('127.0.0.5', 9160), ('127.0.0.5', 7000),
> '7500', '0', None, ('127.0.0.5', 9042)) cluster.add(node5, False,
> data_center="dc1") node5.start(replace_address='127.0.0.3') >
> assert_one(session, "SELECT COUNT(*) FROM ks.cf LIMIT 200", [149])
> repair_tests/incremental_repair_test.py:300: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ tools/assertions.py:130: in
> assert_one res = session.execute(simple_query)
> ../venv/src/cassandra-driver/cassandra/cluster.py:2618: in execute return
> self.execute_async(query, parameters, trace, custom_payload, timeout,
> execution_profile, paging_state, host, execute_as).result() _ _ _ _ _ _ _ _ _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self =
> See Session.execute[_async](timeout)'}, last_host=127.0.0.2:9042
> coordinator_host=None> def result(self): """ Return the final result or raise
> an Exception if errors were encountered. If the final result or error has not
> been set yet, this method will block until it is set, or the timeout set for
> the request expires. Timeout is specified in the Session request execution
> functions. If the timeout is exceeded, an :exc:`cassandra.OperationTimedOut`
> will be raised. This is a client-side timeout. For more information about
> server-side coordinator timeouts, see :class:`.policies.RetryPolicy`. Example
> usage:: >>> future = session.execute_async("SELECT * FROM mycf") >>> # do
> other
[jira] [Commented] (CASSANDRA-17321) Investigate large number of test timeouts on specific build runs
[ https://issues.apache.org/jira/browse/CASSANDRA-17321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609817#comment-17609817 ] Berenguer Blasi commented on CASSANDRA-17321: - Adding CASSANDRA-17005 here > Investigate large number of test timeouts on specific build runs > > > Key: CASSANDRA-17321 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17321 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Josh McKenzie >Priority: Normal > > We have a selection of new test failures on CI run 323 on 4.0 and 923 on > trunk that appear to have a variety of teardown errors or timeouts. We should > look into if there's any kind of theme, commonality, etc that we can make > changes w/respect to to prevent this kind of "dud job" from occurring in the > future. > 323 4.0: https://ci-cassandra.apache.org/job/Cassandra-4.0/323/testReport/ > 923 trunk: https://ci-cassandra.apache.org/job/Cassandra-trunk/923/ > Failures on 4.0: > https://ci-cassandra.apache.org/job/Cassandra-4.0/323/testReport/dtest-novnode.materialized_views_test/TestMaterializedViewsConsistency/test_multi_partition_consistent_reads_after_write/ > https://ci-cassandra.apache.org/job/Cassandra-4.0/323/testReport/dtest-novnode.transient_replication_test/TestTransientReplication/test_cheap_quorums/ > https://ci-cassandra.apache.org/job/Cassandra-4.0/323/testReport/dtest-novnode.client_request_metrics_test/TestClientRequestMetrics/test_client_request_metrics/ > https://ci-cassandra.apache.org/job/Cassandra-4.0/323/testReport/dtest-novnode.repair_tests.repair_test/TestRepair/test_multiple_ranges_repair/ > https://ci-cassandra.apache.org/job/Cassandra-4.0/323/testReport/org.apache.cassandra.net/ProxyHandlerConnectionsTest/testExpireSome/ > Notably, trunk build 923 appears to have the same pattern of a slew of > untraced timeouts on tests: > https://ci-cassandra.apache.org/job/Cassandra-trunk/923/testReport/org.apache.cassandra.distributed.upgrade/CompactStorageUpgradeTest/compactStorageHiddenColumnTest/ > https://ci-cassandra.apache.org/job/Cassandra-trunk/923/testReport/org.apache.cassandra.transport/CQLConnectionTest/handleCorruptionOfLargeMessageFrame_compression_2/ > https://ci-cassandra.apache.org/job/Cassandra-trunk/923/testReport/org.apache.cassandra.distributed.test/NetstatsRepairStreamingTest/testWithCompressionEnabled/ > https://ci-cassandra.apache.org/job/Cassandra-trunk/923/testReport/org.apache.cassandra.distributed.test/NetstatsBootstrapWithEntireSSTablesCompressionStreamingTest/testWithStreamingEntireSSTablesWithoutCompressionWithoutThrottling_4/ > https://ci-cassandra.apache.org/job/Cassandra-trunk/923/testReport/org.apache.cassandra.net/ProxyHandlerConnectionsTest/testExpireSome_compression/ > https://ci-cassandra.apache.org/job/Cassandra-trunk/923/testReport/dtest-novnode.transient_replication_test/TestTransientReplication/test_transient_write/ > https://ci-cassandra.apache.org/job/Cassandra-trunk/923/testReport/dtest-novnode.read_repair_test/TestSpeculativeReadRepair/test_quorum_requirement_on_speculated_read/ -- 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] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609788#comment-17609788 ] Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 9/27/22 2:42 AM: -- Short update: * CircleCI POC link expired. I rebased on trunk and posted branch here - [https://github.com/ekaterinadimitrova2/cassandra/tree/16895-trunk-sept] ; New CI run initiated here: [jdk17|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1949/workflows/aeac69a7-7132-483f-90c2-31d3200f2499] and [jdk11|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1949/workflows/2c4c1108-06c0-40ac-a591-57bfee60964d] There were more tests failing due to some merge issues as we had soon some reorganization of the pom files. Fixed some of them in the last commit and rerun some of the affected tests successfully. Overall current trunk didn't change too much from when I tested in late March * In order to be able to compile with jdk17, I just commented out the scripted UDFs related code and also commented out related tests to remove the noise until proper removal happen in CASSANDRA-17281. That one will wait a bit as there were some discussions on refactoring in that area of the code. * I am revising separately current accesses we already have to JDK internals. Opening tickets and updating carefully dependencies in separate tickets. * Regarding the JDK outreach program, I contacted an Oracle representative who confirmed Cassandra will be added. So far I still have issues to access their private discussion list. I will have to ping them again... was (Author: e.dimitrova): Short update: * CircleCI POC link expired. I rebased on trunk and posted it here - [https://github.com/ekaterinadimitrova2/cassandra/tree/16895-trunk-sept] ; New CI run initiated here: [jdk17|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1949/workflows/aeac69a7-7132-483f-90c2-31d3200f2499] and [jdk11|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1949/workflows/2c4c1108-06c0-40ac-a591-57bfee60964d] There were more tests failing due to some merge issues as we had soon some reorganization of the pom files. Fixed some of them in the last commit and rerun some of the affected tests successfully. Overall current trunk didn't change too much from when I tested in late March * In order to be able to compile with jdk17, I just commented out the scripted UDFs related code and also commented out related tests to remove the noise until proper removal happen in CASSANDRA-17281. That one will wait a bit as there were some discussions on refactoring in that area of the code. * I am revising separately current accesses we already have to JDK internals. Opening tickets and updating carefully dependencies in separate tickets. * Regarding the JDK outreach program, I contacted an Oracle representative who confirmed Cassandra will be added. So far I still have issues to access their private discussion list. I will have to ping them again... > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.x > > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- 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-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609788#comment-17609788 ] Ekaterina Dimitrova commented on CASSANDRA-16895: - Short update: * CircleCI POC link expired. I rebased on trunk and posted it here - [https://github.com/ekaterinadimitrova2/cassandra/tree/16895-trunk-sept] ; New CI run initiated here: [jdk17|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1949/workflows/aeac69a7-7132-483f-90c2-31d3200f2499] and [jdk11|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1949/workflows/2c4c1108-06c0-40ac-a591-57bfee60964d] There were more tests failing due to some merge issues as we had soon some reorganization of the pom files. Fixed some of them in the last commit and rerun some of the affected tests successfully. Overall current trunk didn't change too much from when I tested in late March * In order to be able to compile with jdk17, I just commented out the scripted UDFs related code and also commented out related tests to remove the noise until proper removal happen in CASSANDRA-17281. That one will wait a bit as there were some discussions on refactoring in that area of the code. * I am revising separately current accesses we already have to JDK internals. Opening tickets and updating carefully dependencies in separate tickets. * Regarding the JDK outreach program, I contacted an Oracle representative who confirmed Cassandra will be added. So far I still have issues to access their private discussion list. I will have to ping them again... > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.x > > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- 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-17884) Test failure: o.a.c.repair.RepairJobTest.testNoTreesRetainedAfterDifference
[
https://issues.apache.org/jira/browse/CASSANDRA-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609773#comment-17609773
]
Ekaterina Dimitrova commented on CASSANDRA-17884:
-
Confirmed, the test fails with the low resources too. Only thing is it takes
three times more time to run in a loop the test with the free tier.
> Test failure: o.a.c.repair.RepairJobTest.testNoTreesRetainedAfterDifference
> ---
>
> Key: CASSANDRA-17884
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17884
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> The unit test
> {{org.apache.cassandra.repair.RepairJobTest#testNoTreesRetainedAfterDifference}}
> seems to be slightly flaky at least in 4.0. We haven't seen it failing on
> Butler, but after [a failure on a patch
> branch|https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/281/workflows/e6094c00-b611-4772-9772-205f4c76ecba/jobs/2126/tests],
> this repeated run shows a 0.28% flakiness:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2076/workflows/8adbfe99-afb5-43af-84ad-43df2a2a86e2/jobs/20816/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2076/workflows/e550d8c2-7c35-4326-bd95-6909978d344b/jobs/20817/tests
> {code}
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> jdk.internal.platform.cgroupv1.SubSystem$MemorySubSystem
> jdk.internal.platform.cgroupv1.Metrics.memory accessible: module java.base
> does not "opens jdk.internal.platform.cgroupv1" to unnamed module @157853da
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at
> java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)
> at org.github.jamm.MemoryMeter.addFieldChildren(MemoryMeter.java:330)
> at org.github.jamm.MemoryMeter.measureDeep(MemoryMeter.java:269)
> at
> org.apache.cassandra.utils.ObjectSizes.measureDeep(ObjectSizes.java:216)
> at
> org.apache.cassandra.repair.RepairJobTest.testNoTreesRetainedAfterDifference(RepairJobTest.java:271)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is really low but the failure is clearly reproducible in j11.
--
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-17885) Add solution for CASSANDRA-17581 to older branches for tests
[ https://issues.apache.org/jira/browse/CASSANDRA-17885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609768#comment-17609768 ] Ekaterina Dimitrova commented on CASSANDRA-17885: - Unfortunately the run I pushed on Friday shows that it is still a problem - [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1946/workflow[…]56c-920183badec8/jobs/15420/parallel-runs/34?filterBy=FAILED|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1946/workflows/3d91582f-17ea-4007-856c-920183badec8/jobs/15420/parallel-runs/34?filterBy=FAILED] I can take a look more in detail tomorrow afternoon. > Add solution for CASSANDRA-17581 to older branches for tests > > > Key: CASSANDRA-17885 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17885 > Project: Cassandra > Issue Type: Bug > Components: Tool/nodetool >Reporter: Brandon Williams >Assignee: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x > > > Some of our tests use old branches for the purposes of testing upgrades and > behavior in mixed versions, but those lacking CASSANDRA-17581 will fail on > nodetool with a modern JDK. We can port this fix to those branches and > adjust the tests to use the newest version of them to solve this going > forward. -- 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-17884) Test failure: o.a.c.repair.RepairJobTest.testNoTreesRetainedAfterDifference
[
https://issues.apache.org/jira/browse/CASSANDRA-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609760#comment-17609760
]
Ekaterina Dimitrova commented on CASSANDRA-17884:
-
I hit the issue with the MID resources in CircleCI but I suspect we should be
able to hit it also without raising resources.
Started a run here:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1951/workflows/843b1c08-b7c8-4da1-8ca9-a6df17e5b0f8]
To be able to start that job we need to point CircleCI to the test we want to
cover.
In this case I did it by running the following command from the main cassandra
folder, 4.0-based branch:
{code:java}
.circleci/generate.sh -l -e REPEATED_UTEST_TARGET=test-jvm-dtest-some -e
REPEATED_UTEST_COUNT=1
-e REPEATED_UTEST_CLASS=org.apache.cassandra.repair.RepairJobTest -e
REPEATED_UTEST_METHODS=testNoTreesRetainedAfterDifference{code}
This resulted in the following commit -
[https://github.com/ekaterinadimitrova2/cassandra/commit/597198f1c8043c4df043d17dfe85752de7227688]
As those are low resources the tests are still running. I will check the
results tomorrow morning.
> Test failure: o.a.c.repair.RepairJobTest.testNoTreesRetainedAfterDifference
> ---
>
> Key: CASSANDRA-17884
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17884
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> The unit test
> {{org.apache.cassandra.repair.RepairJobTest#testNoTreesRetainedAfterDifference}}
> seems to be slightly flaky at least in 4.0. We haven't seen it failing on
> Butler, but after [a failure on a patch
> branch|https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/281/workflows/e6094c00-b611-4772-9772-205f4c76ecba/jobs/2126/tests],
> this repeated run shows a 0.28% flakiness:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2076/workflows/8adbfe99-afb5-43af-84ad-43df2a2a86e2/jobs/20816/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2076/workflows/e550d8c2-7c35-4326-bd95-6909978d344b/jobs/20817/tests
> {code}
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> jdk.internal.platform.cgroupv1.SubSystem$MemorySubSystem
> jdk.internal.platform.cgroupv1.Metrics.memory accessible: module java.base
> does not "opens jdk.internal.platform.cgroupv1" to unnamed module @157853da
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at
> java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)
> at org.github.jamm.MemoryMeter.addFieldChildren(MemoryMeter.java:330)
> at org.github.jamm.MemoryMeter.measureDeep(MemoryMeter.java:269)
> at
> org.apache.cassandra.utils.ObjectSizes.measureDeep(ObjectSizes.java:216)
> at
> org.apache.cassandra.repair.RepairJobTest.testNoTreesRetainedAfterDifference(RepairJobTest.java:271)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is really low but the failure is clearly reproducible in j11.
--
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
[cassandra-website] branch asf-staging updated (490178642 -> f18980b52)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 490178642 generate docs for 2db0aea2 new f18980b52 generate docs for 2db0aea2 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (490178642) \ N -- N -- N refs/heads/asf-staging (f18980b52) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17923) Mixed mode support for internode authentication during TLS upgrades
[ https://issues.apache.org/jira/browse/CASSANDRA-17923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jyothsna Konisa updated CASSANDRA-17923: Summary: Mixed mode support for internode authentication during TLS upgrades (was: Mixed mode support for internode authentication during mTLS upgrades) > Mixed mode support for internode authentication during TLS upgrades > --- > > Key: CASSANDRA-17923 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17923 > Project: Cassandra > Issue Type: New Feature >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > > During upgrades from "non-ssl -> ssl" or "ssl-mTLS" the cluster should be > able to function in mixed mode with some nodes supporting "non-ssl" > authentication and the new nodes supporting "mTLS" authentication. Currently > we do not have this supported and because of which upgrades are not possible > for upgrading internode authentication strategies. > If a node is configured in optional mode for internode connections, retry > with other SSL strategies If the node is not able to connect to other nodes > due to authentication problems. -- 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
[cassandra] branch trunk updated (26ba82f6a2 -> 526f41899a)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 26ba82f6a2 Merge branch 'cassandra-4.1' into trunk add 5d9d93ea08 Prepare debian changelog for 4.1-beta1 new 526f41899a Merge branch 'cassandra-4.1' into trunk The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated (65c9875b39 -> 5d9d93ea08)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 65c9875b39 increment version to 4.1-beta1 add 5d9d93ea08 Prepare debian changelog for 4.1-beta1 No new revisions were added by this update. Summary of changes: debian/changelog | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 526f41899a7273d262ff3bd86047e6d0d6f85d91 Merge: 26ba82f6a2 5d9d93ea08 Author: Mick Semb Wever AuthorDate: Tue Sep 27 00:52:57 2022 +0200 Merge branch 'cassandra-4.1' into trunk * cassandra-4.1: Prepare debian changelog for 4.1-beta1 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r57013 - in /dev/cassandra/4.1-beta1/redhat: ./ noboolean/ noboolean/repodata/ repodata/
Author: mck Date: Mon Sep 26 22:51:24 2022 New Revision: 57013 Log: staging cassandra rpm packages for 4.1-beta1 Added: dev/cassandra/4.1-beta1/redhat/ dev/cassandra/4.1-beta1/redhat/cassandra-4.1~beta1-1.noarch.rpm (with props) dev/cassandra/4.1-beta1/redhat/cassandra-4.1~beta1-1.src.rpm (with props) dev/cassandra/4.1-beta1/redhat/cassandra-tools-4.1~beta1-1.noarch.rpm (with props) dev/cassandra/4.1-beta1/redhat/noboolean/ dev/cassandra/4.1-beta1/redhat/noboolean/cassandra-4.1~beta1-1.noarch.rpm (with props) dev/cassandra/4.1-beta1/redhat/noboolean/cassandra-4.1~beta1-1.src.rpm (with props) dev/cassandra/4.1-beta1/redhat/noboolean/cassandra-tools-4.1~beta1-1.noarch.rpm (with props) dev/cassandra/4.1-beta1/redhat/noboolean/repodata/ dev/cassandra/4.1-beta1/redhat/noboolean/repodata/4f6de412735231642337a30739ff4908e0cdaa796431236edeab110d0ea7be24-other.xml.gz (with props) dev/cassandra/4.1-beta1/redhat/noboolean/repodata/4f6de412735231642337a30739ff4908e0cdaa796431236edeab110d0ea7be24-other.xml.gz.asc dev/cassandra/4.1-beta1/redhat/noboolean/repodata/a1cbd1cd95db85f5380493139fe1e5cc79c505ab9f758d73a5106f99840df9ac-primary.xml.gz (with props) dev/cassandra/4.1-beta1/redhat/noboolean/repodata/a1cbd1cd95db85f5380493139fe1e5cc79c505ab9f758d73a5106f99840df9ac-primary.xml.gz.asc dev/cassandra/4.1-beta1/redhat/noboolean/repodata/a5db3d3558043ee9a5463bcf8b10d7e54fd45e4beb9866112d9f606ae9566b8e-other.sqlite.bz2 (with props) dev/cassandra/4.1-beta1/redhat/noboolean/repodata/a5db3d3558043ee9a5463bcf8b10d7e54fd45e4beb9866112d9f606ae9566b8e-other.sqlite.bz2.asc dev/cassandra/4.1-beta1/redhat/noboolean/repodata/b66654c11aa68b934521098aafe5d874a54584f3f3b567e49505231935206074-filelists.xml.gz (with props) dev/cassandra/4.1-beta1/redhat/noboolean/repodata/b66654c11aa68b934521098aafe5d874a54584f3f3b567e49505231935206074-filelists.xml.gz.asc dev/cassandra/4.1-beta1/redhat/noboolean/repodata/df98d81c4b49c8c51af113929cab293e5f0c3cd1000140eb7ff9a37f12d9c7b5-primary.sqlite.bz2 (with props) dev/cassandra/4.1-beta1/redhat/noboolean/repodata/df98d81c4b49c8c51af113929cab293e5f0c3cd1000140eb7ff9a37f12d9c7b5-primary.sqlite.bz2.asc dev/cassandra/4.1-beta1/redhat/noboolean/repodata/f61ee014b106d82c26a37a819fc0e96d86e91b12b3daa90f87d466c93d350f0e-filelists.sqlite.bz2 (with props) dev/cassandra/4.1-beta1/redhat/noboolean/repodata/f61ee014b106d82c26a37a819fc0e96d86e91b12b3daa90f87d466c93d350f0e-filelists.sqlite.bz2.asc dev/cassandra/4.1-beta1/redhat/noboolean/repodata/repomd.xml dev/cassandra/4.1-beta1/redhat/noboolean/repodata/repomd.xml.asc dev/cassandra/4.1-beta1/redhat/repodata/ dev/cassandra/4.1-beta1/redhat/repodata/6c2a95de36d5f6d3a1cd806fbff2b398f2c9b328932db558d2e8de156844701d-primary.xml.gz (with props) dev/cassandra/4.1-beta1/redhat/repodata/6c2a95de36d5f6d3a1cd806fbff2b398f2c9b328932db558d2e8de156844701d-primary.xml.gz.asc dev/cassandra/4.1-beta1/redhat/repodata/8133fd35fc7b364da8ce04809eeb13144fec74a2d2cf59173ba0cf8b0266e3f4-other.sqlite.bz2 (with props) dev/cassandra/4.1-beta1/redhat/repodata/8133fd35fc7b364da8ce04809eeb13144fec74a2d2cf59173ba0cf8b0266e3f4-other.sqlite.bz2.asc dev/cassandra/4.1-beta1/redhat/repodata/8a8d981104f2857ac65aa8b0bec781be2ae9c73d8dde6fbe88ef717a998c4a87-filelists.xml.gz (with props) dev/cassandra/4.1-beta1/redhat/repodata/8a8d981104f2857ac65aa8b0bec781be2ae9c73d8dde6fbe88ef717a998c4a87-filelists.xml.gz.asc dev/cassandra/4.1-beta1/redhat/repodata/d13d825370af343d0cfa38773d88860bad8b4b83a7cda34e71b5928395efe6d1-other.xml.gz (with props) dev/cassandra/4.1-beta1/redhat/repodata/d13d825370af343d0cfa38773d88860bad8b4b83a7cda34e71b5928395efe6d1-other.xml.gz.asc dev/cassandra/4.1-beta1/redhat/repodata/d18be08dad054d76549abc98ac76f03713df89000aecadccd3062bf59c14ef21-filelists.sqlite.bz2 (with props) dev/cassandra/4.1-beta1/redhat/repodata/d18be08dad054d76549abc98ac76f03713df89000aecadccd3062bf59c14ef21-filelists.sqlite.bz2.asc dev/cassandra/4.1-beta1/redhat/repodata/f3f3faa7935dd8b5e9583080cd7f2e058c898b71d9489c005b414952f32b2dbc-primary.sqlite.bz2 (with props) dev/cassandra/4.1-beta1/redhat/repodata/f3f3faa7935dd8b5e9583080cd7f2e058c898b71d9489c005b414952f32b2dbc-primary.sqlite.bz2.asc dev/cassandra/4.1-beta1/redhat/repodata/repomd.xml dev/cassandra/4.1-beta1/redhat/repodata/repomd.xml.asc Added: dev/cassandra/4.1-beta1/redhat/cassandra-4.1~beta1-1.noarch.rpm == Binary file - no diff available. Propchange: dev/cassandra/4.1-beta1/redhat/cassandra-4.1~beta1-1.noarch.rpm -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.1-beta1/redhat/cassandra-4.1~beta1-1.src.rpm
[jira] [Updated] (CASSANDRA-17924) WEBSITE - Add doc about checkstyle for contributors
[ https://issues.apache.org/jira/browse/CASSANDRA-17924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17924: -- Summary: WEBSITE - Add doc about checkstyle for contributors (was: WEBSITE - Add doc about checkstyle and its properties into code_style) > WEBSITE - Add doc about checkstyle for contributors > --- > > Key: CASSANDRA-17924 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17924 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: NA > > > Add doc about checkstyle and its properties into code_style for > CASSANDRA-17876. -- 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-17924) WEBSITE - Add doc about checkstyle and its properties into code_style
[
https://issues.apache.org/jira/browse/CASSANDRA-17924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17924:
--
Test and Documentation Plan: Stage updates and verify the page renders
correctly
Status: Patch Available (was: Open)
Patch:
||Branch||PR||
|{{trunk}}|[#174|https://github.com/apache/cassandra-website/pull/174]|
> WEBSITE - Add doc about checkstyle and its properties into code_style
> -
>
> Key: CASSANDRA-17924
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17924
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: NA
>
>
> Add doc about checkstyle and its properties into code_style for
> CASSANDRA-17876.
--
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-17924) WEBSITE - Add doc about checkstyle and its properties into code_style
[ https://issues.apache.org/jira/browse/CASSANDRA-17924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17924: -- Change Category: Semantic Complexity: Normal Fix Version/s: NA Reviewers: Erick Ramirez Status: Open (was: Triage Needed) > WEBSITE - Add doc about checkstyle and its properties into code_style > - > > Key: CASSANDRA-17924 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17924 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: NA > > > Add doc about checkstyle and its properties into code_style for > CASSANDRA-17876. -- 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-17924) WEBSITE - Add doc about checkstyle and its properties into code_style
Erick Ramirez created CASSANDRA-17924: - Summary: WEBSITE - Add doc about checkstyle and its properties into code_style Key: CASSANDRA-17924 URL: https://issues.apache.org/jira/browse/CASSANDRA-17924 Project: Cassandra Issue Type: Task Components: Documentation/Website Reporter: Erick Ramirez Assignee: Stefan Miklosovic Add doc about checkstyle and its properties into code_style for CASSANDRA-17876. -- 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
svn commit: r57012 - in /dev/cassandra/4.1-beta1/debian: ./ dists/ dists/41x/ dists/41x/main/ dists/41x/main/binary-amd64/ dists/41x/main/binary-arm64/ dists/41x/main/binary-i386/ dists/41x/main/sourc
Author: mck Date: Mon Sep 26 22:32:27 2022 New Revision: 57012 Log: staging cassandra debian packages for 4.1-beta1 Added: dev/cassandra/4.1-beta1/debian/ dev/cassandra/4.1-beta1/debian/cassandra-tools_4.1~beta1_all.deb (with props) dev/cassandra/4.1-beta1/debian/cassandra_4.1~beta1.dsc dev/cassandra/4.1-beta1/debian/cassandra_4.1~beta1.tar.gz (with props) dev/cassandra/4.1-beta1/debian/cassandra_4.1~beta1_all.deb (with props) dev/cassandra/4.1-beta1/debian/cassandra_4.1~beta1_amd64.buildinfo dev/cassandra/4.1-beta1/debian/cassandra_4.1~beta1_amd64.changes dev/cassandra/4.1-beta1/debian/dists/ dev/cassandra/4.1-beta1/debian/dists/41x/ dev/cassandra/4.1-beta1/debian/dists/41x/InRelease dev/cassandra/4.1-beta1/debian/dists/41x/Release dev/cassandra/4.1-beta1/debian/dists/41x/Release.gpg dev/cassandra/4.1-beta1/debian/dists/41x/main/ dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-amd64/ dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-amd64/Packages dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-amd64/Packages.gz (with props) dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-amd64/Release dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-arm64/ dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-arm64/Packages dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-arm64/Packages.gz (with props) dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-arm64/Release dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-i386/ dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-i386/Packages dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-i386/Packages.gz (with props) dev/cassandra/4.1-beta1/debian/dists/41x/main/binary-i386/Release dev/cassandra/4.1-beta1/debian/dists/41x/main/source/ dev/cassandra/4.1-beta1/debian/dists/41x/main/source/Release dev/cassandra/4.1-beta1/debian/dists/41x/main/source/Sources.gz (with props) dev/cassandra/4.1-beta1/debian/pool/ dev/cassandra/4.1-beta1/debian/pool/main/ dev/cassandra/4.1-beta1/debian/pool/main/c/ dev/cassandra/4.1-beta1/debian/pool/main/c/cassandra/ dev/cassandra/4.1-beta1/debian/pool/main/c/cassandra/cassandra-tools_4.1~beta1_all.deb (with props) dev/cassandra/4.1-beta1/debian/pool/main/c/cassandra/cassandra_4.1~beta1.dsc dev/cassandra/4.1-beta1/debian/pool/main/c/cassandra/cassandra_4.1~beta1.tar.gz (with props) dev/cassandra/4.1-beta1/debian/pool/main/c/cassandra/cassandra_4.1~beta1_all.deb (with props) Added: dev/cassandra/4.1-beta1/debian/cassandra-tools_4.1~beta1_all.deb == Binary file - no diff available. Propchange: dev/cassandra/4.1-beta1/debian/cassandra-tools_4.1~beta1_all.deb -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.1-beta1/debian/cassandra_4.1~beta1.dsc == --- dev/cassandra/4.1-beta1/debian/cassandra_4.1~beta1.dsc (added) +++ dev/cassandra/4.1-beta1/debian/cassandra_4.1~beta1.dsc Mon Sep 26 22:32:27 2022 @@ -0,0 +1,41 @@ +-BEGIN PGP SIGNED MESSAGE- +Hash: SHA512 + +Format: 1.0 +Source: cassandra +Binary: cassandra, cassandra-tools +Architecture: all +Version: 4.1~beta1 +Maintainer: Eric Evans +Uploaders: Sylvain Lebresne +Homepage: http://cassandra.apache.org +Standards-Version: 3.8.3 +Vcs-Browser: https://gitbox.apache.org/repos/asf?p=cassandra.git +Vcs-Git: https://gitbox.apache.org/repos/asf/cassandra.git +Build-Depends: debhelper (>= 11), openjdk-8-jdk | java8-jdk | openjdk-11-jdk | java11-jdk, ant (>= 1.9), ant-optional (>= 1.9), dh-python, python3-dev (>= 3.6), quilt, bash-completion +Package-List: + cassandra deb misc extra arch=all + cassandra-tools deb misc extra arch=all +Checksums-Sha1: + fa43b33f0116e0cbabfcf99f819b37b9d80d2426 240523633 cassandra_4.1~beta1.tar.gz +Checksums-Sha256: + d1a2e79ec7bc441c2b0d456308e0568e0e03f2284d3dd0c22d14705c4863639a 240523633 cassandra_4.1~beta1.tar.gz +Files: + 078b623ce10f4f04e7fe0823c338cdb7 240523633 cassandra_4.1~beta1.tar.gz + +-BEGIN PGP SIGNATURE- + +iQIzBAEBCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmMyJ78ACgkQ6RM1134+ +h8t5MQ/9Gex/UsYpILQOni3PvsblhRRAfubh5R3cszTmqu8bSWvzdNVqeWk8gMWF +JroTIE+fios8jkWf6AlvBiDcZvZA8rDhH7TBScl+nov+3c+CI0uNe4r81sUgQpvW +meeI/MmaficDm1uPNa0o03dYaoLIjdIkCv7j5tn4R7wEboajoyNE8jpvMecMAirP +wXa0d3lrnV2YmBMDvJsPQLDyXDHIFYkQ5lS2FTJNH4br6VbGXvh7tdnbEbIMXWGu +A5k9UMpy7/XUmZmpmaOBGbqAVvUzvKYrr7GbFWecAI4PTL1E9DEVeuwb+w0B5bse +M8DPfLgKc7EJWIoeIZjgSdL4CUQ7uhnDObBGMZxXrCIfOY/W6eH8B7s98XIcM2ix +M57gZARNl5LGaJyyiWZbI7Dfi5C0mFkxyyTQBxqwpZ59URi5PPNyVnk6ofsKPvFX +9rtQiI4zvL9rLrsTssqO/4jN1Wb1zOWJXpw0FtHDu6n0HgyiDMB/bsKVhpGoDYBy +H2eVHlZULJFcpZ2ugr7U1fNL8yhWI9VBbqpM5tVBgcZSR6Z9N1s+RKAT7l0bjO4g
svn commit: r57011 - /dev/cassandra/4.1-beta1/
Author: mck Date: Mon Sep 26 22:18:45 2022 New Revision: 57011 Log: staging cassandra 4.1-beta1 Added: dev/cassandra/4.1-beta1/ dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz (with props) dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.asc dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.sha256 dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.sha512 dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-src.tar.gz (with props) dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-src.tar.gz.asc dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-src.tar.gz.sha256 dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-src.tar.gz.sha512 Added: dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.asc == --- dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.asc (added) +++ dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.asc Mon Sep 26 22:18:45 2022 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmMyJJ0ACgkQ6RM1134+ +h8uIxw//cDvoNvLhRiMts43U66gf1cXFO6gECYogLO5ijGRPiQBAUv8sU5JnVxuT +hOIg/Bk+gCBgCQm68dVFgVGp56dTlmF8qdcdN3x3HerVXx+hVtplUbj8WSiCaEUS +vA7y6dCsVk3mBhMFLoovn/oKfr4H0ERzkjKjwdNaiPBg4uvIHuIyEN3ImVDX5xem +8uPwuW6v7WxG+CWXFc1X/ANS1DVTPT6L+L46LrpoA7rMXxT7T+X/K5ji9KMdY6Xr +bnsl3MGF46AH8a7n5hIDwI0JPC9atG8ilALcJCpK+WSKkaH3rkMXNkkT0wNH0maO +3aRDnbU+5Nl5uZ6Hd6mlvmDoOXXCQRL+OTpT4SHkJh9kDQf23/1IWBhVjNFe7gBk +K/62/R79/kWh0VsqWxI3aZR61+QBqBs1sm8ue1ypFjNek2PI8MIU/v/xA4RVVSzY +sF8+UrCeky3lQtsPe7IwE/eQHDkonqUlrJ0aITF1DRWJdTF9w6lwu6khySo407Km +SNW0xKTg9YsoWj/vW2Oa1m0DgmoDZ8J4O+XkIJMd/IF3TBnujHXfAvZ9jktc6k4m +NRwqEr2f94zvimjnsb5otvcm3uW8qzUwPXTmUQYx4ZkMPv5xj9UKtf62X9uJ37Nj +omI5tZOQzW3CyQb6ETfj28qFpCIk2TInsdUFoyBinU4pTcS5dus= +=YY0Z +-END PGP SIGNATURE- Added: dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.sha256 == --- dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.sha256 (added) +++ dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.sha256 Mon Sep 26 22:18:45 2022 @@ -0,0 +1 @@ +dc5543466faaba9c6a34eeb95e75384a42626d1bcc1626b1a915475ec942a42c Added: dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.sha512 == --- dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.sha512 (added) +++ dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-bin.tar.gz.sha512 Mon Sep 26 22:18:45 2022 @@ -0,0 +1 @@ +40f1b6877b1fcccdc5c6b6895e1c919bb4f17f119256bb600c4c749f9b6ca4f1e53341fde4bac9ddefc516d429b1d0909f359a87c5382dd0f3b3440ae3139084 Added: dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-src.tar.gz == Binary file - no diff available. Propchange: dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-src.tar.gz -- svn:mime-type = application/octet-stream Added: dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-src.tar.gz.asc == --- dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-src.tar.gz.asc (added) +++ dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-src.tar.gz.asc Mon Sep 26 22:18:45 2022 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCgAdFiEEpMRl/qDFUlYaOSph6RM1134+h8sFAmMyJKEACgkQ6RM1134+ +h8vGpA//YIBM/HUt80EPp2hrTls0MOkd/h/+ES0BSnLqcdBiMfQPmNvGXJ8XYmqI +0Kj5C9SMQHUswxu1SQfn+mBv8y5WQ048E41ykddj7jUFDViGogJMb6qc7p4vpl9s +MNV59lltiGGKzKmSx4B7GcvMtuNslm7SYPuxtWmrwxbYjXw6s3aHo404vZecIAwO +tUCEcUX4p1HGw5+ZVTmKpK4l1jTaXIEDeftzCuYWZFN4OwrXHCGjpdDN8CxcVQJ6 +rXmbt5RgpvJuDJd5xsKcfKqa4fcWFnyo7+GKeXPJRT9eUfNz21CAlRf9rHY4yfYW +WR0z2nxeglXEqxbVuUadjypMOXHRiO3K0x3FrYecsKUfEEVHcGGlWiEezs019JvZ +OLOAKcT71C8BOg75ZqDSqD5CFx/ezQcsRGzECtd87u+qjrCxUJgflD1apbv7DVp+ +b9mI0grLlFL5LJq24TGEyaA8mjQKVgq4NNDA1uspcX4r7aEiS21G0Lra8QGSj9MI +WTTBaJAp0Z6aWDzq5KqYkEr1NJWI5rltHpX7fpOoKgr6d3LFSfkKzIU2U59C4Ytc +Nqd66AfOZQ/LGX6TN3RwfCQQ+ffWSwfmMwxBUDBAmHWNJvW6JVd0GIDO/SSw7xx4 +T9TBVRtbk/Hl7C6MeY54Ssz2GmcXyIuYe9lLSttTkl4cPMnKah8= +=gdJ1 +-END PGP SIGNATURE- Added: dev/cassandra/4.1-beta1/apache-cassandra-4.1-beta1-src.tar.gz.sha256 == ---
[cassandra] 01/01: Prepare debian changelog for 4.1-beta1
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to tag 4.1-beta1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 5d9d93ea08d9c76402aa1d14bad54bf9ec875686 Author: Mick Semb Wever AuthorDate: Tue Sep 27 00:08:43 2022 +0200 Prepare debian changelog for 4.1-beta1 --- debian/changelog | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index af8d52000c..72efb11bd8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,8 @@ -cassandra (4.1~beta1) UNRELEASED; urgency=medium +cassandra (4.1~beta1) unstable; urgency=medium * New release - -- Mick Semb Wever Fri, 20 May 2022 22:02:50 +0200 + -- Mick Semb Wever Tue, 27 Sep 2022 00:08:07 +0200 cassandra (4.1~alpha1) unstable; urgency=medium - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] tag 4.1-beta1-tentative created (now 5d9d93ea08)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to tag 4.1-beta1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git at 5d9d93ea08 (commit) This tag includes the following new commits: new 5d9d93ea08 Prepare debian changelog for 4.1-beta1 The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17923) Mixed mode support for internode authentication during mTLS upgrades
[ https://issues.apache.org/jira/browse/CASSANDRA-17923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jyothsna Konisa updated CASSANDRA-17923: Summary: Mixed mode support for internode authentication during mTLS upgrades (was: Mixed mode support internode authentication during mTLS upgrades) > Mixed mode support for internode authentication during mTLS upgrades > > > Key: CASSANDRA-17923 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17923 > Project: Cassandra > Issue Type: New Feature >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > > During upgrades from "non-ssl -> ssl" or "ssl-mTLS" the cluster should be > able to function in mixed mode with some nodes supporting "non-ssl" > authentication and the new nodes supporting "mTLS" authentication. Currently > we do not have this supported and because of which upgrades are not possible > for upgrading internode authentication strategies. > If a node is configured in optional mode for internode connections, retry > with other SSL strategies If the node is not able to connect to other nodes > due to authentication problems. -- 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-17923) Mixed mode support internode authentication during mTLS upgrades
Jyothsna Konisa created CASSANDRA-17923: --- Summary: Mixed mode support internode authentication during mTLS upgrades Key: CASSANDRA-17923 URL: https://issues.apache.org/jira/browse/CASSANDRA-17923 Project: Cassandra Issue Type: New Feature Reporter: Jyothsna Konisa During upgrades from "non-ssl -> ssl" or "ssl-mTLS" the cluster should be able to function in mixed mode with some nodes supporting "non-ssl" authentication and the new nodes supporting "mTLS" authentication. Currently we do not have this supported and because of which upgrades are not possible for upgrading internode authentication strategies. If a node is configured in optional mode for internode connections, retry with other SSL strategies If the node is not able to connect to other nodes due to authentication problems. -- 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] [Assigned] (CASSANDRA-17923) Mixed mode support internode authentication during mTLS upgrades
[ https://issues.apache.org/jira/browse/CASSANDRA-17923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jyothsna Konisa reassigned CASSANDRA-17923: --- Assignee: Jyothsna Konisa > Mixed mode support internode authentication during mTLS upgrades > > > Key: CASSANDRA-17923 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17923 > Project: Cassandra > Issue Type: New Feature >Reporter: Jyothsna Konisa >Assignee: Jyothsna Konisa >Priority: Normal > > During upgrades from "non-ssl -> ssl" or "ssl-mTLS" the cluster should be > able to function in mixed mode with some nodes supporting "non-ssl" > authentication and the new nodes supporting "mTLS" authentication. Currently > we do not have this supported and because of which upgrades are not possible > for upgrading internode authentication strategies. > If a node is configured in optional mode for internode connections, retry > with other SSL strategies If the node is not able to connect to other nodes > due to authentication problems. -- 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
[cassandra-website] branch asf-staging updated (a312f5508 -> 490178642)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard a312f5508 generate docs for 2db0aea2 new 490178642 generate docs for 2db0aea2 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (a312f5508) \ N -- N -- N refs/heads/asf-staging (490178642) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated: increment version to 4.1-beta1
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-4.1 by this push: new 65c9875b39 increment version to 4.1-beta1 65c9875b39 is described below commit 65c9875b3964d6f7bd533c6a3a55ce371a1d69bf Author: Mick Semb Wever AuthorDate: Mon Sep 26 20:55:03 2022 +0200 increment version to 4.1-beta1 ref: https://lists.apache.org/thread/ho4r1lk2gsgs1z61ldzg64h84x3rbg4o --- CHANGES.txt | 2 +- build.xml| 2 +- debian/changelog | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/CHANGES.txt b/CHANGES.txt index 17c4a1054e..1ecd879ba6 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,4 @@ -4.1-alpha2 +4.1-beta1 * We should not emit deprecation warning on startup for `key_cache_save_period`, `row_cache_save_period`, `counter_cache_save_period` (CASSANDRA-17904) * upsert with adder support is not consistent with numbers and strings in LWT (CASSANDRA-17857) * Fix race and return after failing connections (CASSANDRA-17618) diff --git a/build.xml b/build.xml index 1800c09dc2..a0a0f196c0 100644 --- a/build.xml +++ b/build.xml @@ -33,7 +33,7 @@ - + https://gitbox.apache.org/repos/asf/cassandra.git"/> https://gitbox.apache.org/repos/asf/cassandra.git"/> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=tree"/> diff --git a/debian/changelog b/debian/changelog index 5c193b9550..af8d52000c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -cassandra (4.1~alpha2) UNRELEASED; urgency=medium +cassandra (4.1~beta1) UNRELEASED; urgency=medium * New release - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 26ba82f6a2820ddeaff9eb1aae4c95d5aa521197 Merge: ff47de11d6 65c9875b39 Author: Mick Semb Wever AuthorDate: Mon Sep 26 23:45:18 2022 +0200 Merge branch 'cassandra-4.1' into trunk * cassandra-4.1: increment version to 4.1-beta1 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (ff47de11d6 -> 26ba82f6a2)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from ff47de11d6 Merge branch 'cassandra-4.1' into trunk new 65c9875b39 increment version to 4.1-beta1 new 26ba82f6a2 Merge branch 'cassandra-4.1' into trunk The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17876: -- Fix Version/s: 4.1-beta Source Control Link: https://github.com/apache/cassandra/commit/5d3c747719f01d87c9086c405c806317405a8e43 Resolution: Fixed Status: Resolved (was: Ready to Commit) > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Labels: pull-request-available > Fix For: 4.1-beta, 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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
[cassandra] branch cassandra-4.1 updated (0f9ddb8b6c -> 5d3c747719)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 0f9ddb8b6c Merge branch 'cassandra-4.0' into cassandra-4.1 add 5d3c747719 add checkstyle modules for checking redundant and unused imports in Java code No new revisions were added by this update. Summary of changes: build.xml| 6 +++--- checkstyle.xml | 3 +++ checkstyle_test.xml | 3 +++ .../org/apache/cassandra/batchlog/BatchlogManager.java | 1 - src/java/org/apache/cassandra/cache/CaffeineCache.java | 2 -- .../org/apache/cassandra/cache/SerializingCache.java | 2 -- .../org/apache/cassandra/config/EncryptionOptions.java | 5 - src/java/org/apache/cassandra/cql3/WhereClause.java | 1 - .../cql3/restrictions/SingleColumnRestriction.java | 1 - .../org/apache/cassandra/cql3/selection/MapSelector.java | 1 - .../cql3/statements/schema/AlterTableStatement.java | 1 - .../cql3/statements/schema/TableAttributes.java | 1 - src/java/org/apache/cassandra/db/ReadResponse.java | 2 -- .../apache/cassandra/db/SystemKeyspaceMigrator41.java| 1 - .../db/compaction/writers/CompactionAwareWriter.java | 2 -- .../cassandra/db/filter/ClusteringIndexFilter.java | 1 - .../cassandra/db/filter/ClusteringIndexSliceFilter.java | 1 - .../cassandra/db/marshal/AbstractTimeUUIDType.java | 1 - .../cassandra/db/memtable/SkipListMemtableFactory.java | 2 -- .../db/repair/CassandraKeyspaceRepairManager.java| 1 - .../cassandra/db/repair/CassandraValidationIterator.java | 1 - .../org/apache/cassandra/db/rows/ComplexColumnData.java | 3 --- .../cassandra/db/virtual/StreamingVirtualTable.java | 2 -- src/java/org/apache/cassandra/hints/HintsStore.java | 1 - .../org/apache/cassandra/hints/PendingHintsInfo.java | 1 - .../index/sasi/analyzer/filter/StemmerFactory.java | 2 -- .../index/sasi/analyzer/filter/StopWordFactory.java | 2 -- .../apache/cassandra/io/sstable/CQLSSTableWriter.java| 1 - .../apache/cassandra/io/util/DataIntegrityMetadata.java | 1 - .../org/apache/cassandra/io/util/RandomAccessReader.java | 1 - .../apache/cassandra/metrics/HintedHandoffMetrics.java | 2 -- .../apache/cassandra/metrics/HintsServiceMetrics.java| 1 - .../apache/cassandra/net/AsyncStreamingInputPlus.java| 1 - .../org/apache/cassandra/net/OutboundConnections.java| 1 - src/java/org/apache/cassandra/net/ParamType.java | 1 - src/java/org/apache/cassandra/net/RequestCallbacks.java | 1 - .../apache/cassandra/repair/IncrementalRepairTask.java | 1 - .../org/apache/cassandra/repair/PreviewRepairTask.java | 1 - src/java/org/apache/cassandra/repair/RepairJobDesc.java | 2 -- src/java/org/apache/cassandra/repair/RepairRunnable.java | 1 - .../org/apache/cassandra/repair/state/SessionState.java | 1 - .../apache/cassandra/schema/SchemaPullVerbHandler.java | 5 - .../apache/cassandra/schema/SchemaPushVerbHandler.java | 2 -- .../org/apache/cassandra/security/CipherFactory.java | 1 - .../org/apache/cassandra/serializers/ListSerializer.java | 1 - .../apache/cassandra/service/ActiveRepairService.java| 3 --- src/java/org/apache/cassandra/service/ClientState.java | 1 - src/java/org/apache/cassandra/service/StorageProxy.java | 1 - src/java/org/apache/cassandra/service/paxos/Paxos.java | 3 --- .../cassandra/service/paxos/PaxosCommitAndPrepare.java | 1 - .../cassandra/service/paxos/PaxosPrepareRefresh.java | 1 - .../cassandra/service/paxos/PaxosRepairHistory.java | 1 - .../cassandra/service/paxos/TablePaxosRepairHistory.java | 1 - .../paxos/cleanup/PaxosCleanupLocalCoordinator.java | 1 - .../service/paxos/cleanup/PaxosCleanupRequest.java | 1 - .../service/paxos/uncommitted/UncommittedDataFile.java | 1 - .../service/paxos/uncommitted/UncommittedTableData.java | 1 - .../service/reads/FixedSpeculativeRetryPolicy.java | 1 - .../service/reads/repair/BlockingReadRepair.java | 1 - .../apache/cassandra/transport/ExceptionHandlers.java| 1 - .../cassandra/transport/messages/BatchMessage.java | 5 - .../org/apache/cassandra/utils/CloseableIterator.java| 1 - src/java/org/apache/cassandra/utils/IntervalTree.java| 1 - src/java/org/apache/cassandra/utils/Isolated.java| 2 -- src/java/org/apache/cassandra/utils/NativeLibrary.java | 1 - src/java/org/apache/cassandra/utils/UUIDGen.java | 1 - .../cassandra/utils/concurrent/IntrusiveStack.java | 1 - src/java/org/apache/cassandra/utils/concurrent/Ref.java | 1 - .../org/apache/cassandra/distributed/Cluster.java| 1 - .../cassandra/distributed/action/GossipHelper.java
[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit ff47de11d6238ac78b796f565904c600b7a20e92 Merge: f4b69ba0e8 5d3c747719 Author: Stefan Miklosovic AuthorDate: Mon Sep 26 22:25:18 2022 +0200 Merge branch 'cassandra-4.1' into trunk build.xml| 6 +++--- checkstyle.xml | 3 +++ checkstyle_test.xml | 3 +++ .../org/apache/cassandra/batchlog/BatchlogManager.java | 1 - src/java/org/apache/cassandra/cache/CaffeineCache.java | 2 -- .../org/apache/cassandra/cache/SerializingCache.java | 2 -- src/java/org/apache/cassandra/cql3/WhereClause.java | 1 - .../cql3/restrictions/SingleColumnRestriction.java | 1 - .../cassandra/cql3/selection/ResultSetBuilder.java | 4 .../cql3/statements/schema/AlterTableStatement.java | 1 - .../cql3/statements/schema/TableAttributes.java | 1 - src/java/org/apache/cassandra/db/NativeDecoratedKey.java | 2 -- src/java/org/apache/cassandra/db/ReadResponse.java | 2 -- .../apache/cassandra/db/SnapshotDetailsTabularData.java | 1 - src/java/org/apache/cassandra/db/SystemKeyspace.java | 1 - .../apache/cassandra/db/SystemKeyspaceMigrator41.java| 1 - .../db/compaction/CompactionHistoryTabularData.java | 1 - .../cassandra/db/filter/ClusteringIndexFilter.java | 1 - .../cassandra/db/filter/ClusteringIndexSliceFilter.java | 1 - .../cassandra/db/memtable/SkipListMemtableFactory.java | 2 -- .../db/repair/CassandraKeyspaceRepairManager.java| 1 - .../cassandra/db/repair/CassandraValidationIterator.java | 1 - .../org/apache/cassandra/db/rows/ComplexColumnData.java | 3 --- .../cassandra/db/virtual/StreamingVirtualTable.java | 2 -- src/java/org/apache/cassandra/hints/HintsStore.java | 1 - .../org/apache/cassandra/hints/PendingHintsInfo.java | 1 - .../index/sasi/analyzer/filter/StemmerFactory.java | 2 -- .../index/sasi/analyzer/filter/StopWordFactory.java | 2 -- .../apache/cassandra/io/sstable/CQLSSTableWriter.java| 1 - .../apache/cassandra/io/util/DataIntegrityMetadata.java | 1 - .../org/apache/cassandra/io/util/RandomAccessReader.java | 1 - .../apache/cassandra/metrics/HintedHandoffMetrics.java | 2 -- .../apache/cassandra/metrics/HintsServiceMetrics.java| 1 - .../apache/cassandra/net/AsyncStreamingInputPlus.java| 1 - .../apache/cassandra/net/InboundConnectionSettings.java | 1 - .../org/apache/cassandra/net/OutboundConnections.java| 1 - src/java/org/apache/cassandra/net/ParamType.java | 1 - src/java/org/apache/cassandra/net/RequestCallbacks.java | 1 - .../apache/cassandra/repair/IncrementalRepairTask.java | 1 - .../org/apache/cassandra/repair/PreviewRepairTask.java | 1 - src/java/org/apache/cassandra/repair/RepairJobDesc.java | 2 -- src/java/org/apache/cassandra/repair/RepairRunnable.java | 1 - .../org/apache/cassandra/repair/state/SessionState.java | 1 - .../apache/cassandra/schema/SchemaPullVerbHandler.java | 5 - .../apache/cassandra/schema/SchemaPushVerbHandler.java | 2 -- .../org/apache/cassandra/security/CipherFactory.java | 1 - .../cassandra/service/AbstractWriteResponseHandler.java | 2 -- .../apache/cassandra/service/ActiveRepairService.java| 3 --- src/java/org/apache/cassandra/service/ClientState.java | 1 - src/java/org/apache/cassandra/service/paxos/Paxos.java | 3 --- .../cassandra/service/paxos/PaxosCommitAndPrepare.java | 1 - .../cassandra/service/paxos/PaxosPrepareRefresh.java | 1 - .../cassandra/service/paxos/PaxosRepairHistory.java | 1 - .../cassandra/service/paxos/TablePaxosRepairHistory.java | 1 - .../paxos/cleanup/PaxosCleanupLocalCoordinator.java | 1 - .../service/paxos/cleanup/PaxosCleanupRequest.java | 1 - .../service/paxos/uncommitted/UncommittedDataFile.java | 1 - .../service/paxos/uncommitted/UncommittedTableData.java | 1 - .../service/reads/FixedSpeculativeRetryPolicy.java | 1 - .../service/reads/repair/BlockingReadRepair.java | 1 - .../apache/cassandra/transport/ExceptionHandlers.java| 1 - .../cassandra/transport/messages/BatchMessage.java | 5 - .../org/apache/cassandra/utils/CloseableIterator.java| 1 - src/java/org/apache/cassandra/utils/IntervalTree.java| 1 - src/java/org/apache/cassandra/utils/Isolated.java| 2 -- src/java/org/apache/cassandra/utils/NativeLibrary.java | 1 - src/java/org/apache/cassandra/utils/UUIDGen.java | 1 - .../cassandra/utils/concurrent/IntrusiveStack.java | 1 - src/java/org/apache/cassandra/utils/concurrent/Ref.java | 1 - .../org/apache/cassandra/distributed/Cluster.java| 1 -
[cassandra] branch trunk updated (f4b69ba0e8 -> ff47de11d6)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from f4b69ba0e8 Fix "open RT bound as its last item" exception add 5d3c747719 add checkstyle modules for checking redundant and unused imports in Java code new ff47de11d6 Merge branch 'cassandra-4.1' into trunk The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: build.xml| 6 +++--- checkstyle.xml | 3 +++ checkstyle_test.xml | 3 +++ .../org/apache/cassandra/batchlog/BatchlogManager.java | 1 - src/java/org/apache/cassandra/cache/CaffeineCache.java | 2 -- .../org/apache/cassandra/cache/SerializingCache.java | 2 -- src/java/org/apache/cassandra/cql3/WhereClause.java | 1 - .../cql3/restrictions/SingleColumnRestriction.java | 1 - .../cassandra/cql3/selection/ResultSetBuilder.java | 4 .../cql3/statements/schema/AlterTableStatement.java | 1 - .../cql3/statements/schema/TableAttributes.java | 1 - src/java/org/apache/cassandra/db/NativeDecoratedKey.java | 2 -- src/java/org/apache/cassandra/db/ReadResponse.java | 2 -- .../apache/cassandra/db/SnapshotDetailsTabularData.java | 1 - src/java/org/apache/cassandra/db/SystemKeyspace.java | 1 - .../apache/cassandra/db/SystemKeyspaceMigrator41.java| 1 - .../db/compaction/CompactionHistoryTabularData.java | 1 - .../cassandra/db/filter/ClusteringIndexFilter.java | 1 - .../cassandra/db/filter/ClusteringIndexSliceFilter.java | 1 - .../cassandra/db/memtable/SkipListMemtableFactory.java | 2 -- .../db/repair/CassandraKeyspaceRepairManager.java| 1 - .../cassandra/db/repair/CassandraValidationIterator.java | 1 - .../org/apache/cassandra/db/rows/ComplexColumnData.java | 3 --- .../cassandra/db/virtual/StreamingVirtualTable.java | 2 -- src/java/org/apache/cassandra/hints/HintsStore.java | 1 - .../org/apache/cassandra/hints/PendingHintsInfo.java | 1 - .../index/sasi/analyzer/filter/StemmerFactory.java | 2 -- .../index/sasi/analyzer/filter/StopWordFactory.java | 2 -- .../apache/cassandra/io/sstable/CQLSSTableWriter.java| 1 - .../apache/cassandra/io/util/DataIntegrityMetadata.java | 1 - .../org/apache/cassandra/io/util/RandomAccessReader.java | 1 - .../apache/cassandra/metrics/HintedHandoffMetrics.java | 2 -- .../apache/cassandra/metrics/HintsServiceMetrics.java| 1 - .../apache/cassandra/net/AsyncStreamingInputPlus.java| 1 - .../apache/cassandra/net/InboundConnectionSettings.java | 1 - .../org/apache/cassandra/net/OutboundConnections.java| 1 - src/java/org/apache/cassandra/net/ParamType.java | 1 - src/java/org/apache/cassandra/net/RequestCallbacks.java | 1 - .../apache/cassandra/repair/IncrementalRepairTask.java | 1 - .../org/apache/cassandra/repair/PreviewRepairTask.java | 1 - src/java/org/apache/cassandra/repair/RepairJobDesc.java | 2 -- src/java/org/apache/cassandra/repair/RepairRunnable.java | 1 - .../org/apache/cassandra/repair/state/SessionState.java | 1 - .../apache/cassandra/schema/SchemaPullVerbHandler.java | 5 - .../apache/cassandra/schema/SchemaPushVerbHandler.java | 2 -- .../org/apache/cassandra/security/CipherFactory.java | 1 - .../cassandra/service/AbstractWriteResponseHandler.java | 2 -- .../apache/cassandra/service/ActiveRepairService.java| 3 --- src/java/org/apache/cassandra/service/ClientState.java | 1 - src/java/org/apache/cassandra/service/paxos/Paxos.java | 3 --- .../cassandra/service/paxos/PaxosCommitAndPrepare.java | 1 - .../cassandra/service/paxos/PaxosPrepareRefresh.java | 1 - .../cassandra/service/paxos/PaxosRepairHistory.java | 1 - .../cassandra/service/paxos/TablePaxosRepairHistory.java | 1 - .../paxos/cleanup/PaxosCleanupLocalCoordinator.java | 1 - .../service/paxos/cleanup/PaxosCleanupRequest.java | 1 - .../service/paxos/uncommitted/UncommittedDataFile.java | 1 - .../service/paxos/uncommitted/UncommittedTableData.java | 1 - .../service/reads/FixedSpeculativeRetryPolicy.java | 1 - .../service/reads/repair/BlockingReadRepair.java | 1 - .../apache/cassandra/transport/ExceptionHandlers.java| 1 - .../cassandra/transport/messages/BatchMessage.java | 5 - .../org/apache/cassandra/utils/CloseableIterator.java| 1 - src/java/org/apache/cassandra/utils/IntervalTree.java| 1 - src/java/org/apache/cassandra/utils/Isolated.java| 2 -- src/java/org/apache/cassandra/utils/NativeLibrary.java | 1 -
[jira] [Updated] (CASSANDRA-17892) Test Failure: dtest-novnode.transient_replication_test.TestTransientReplicationRepairLegacyStreaming.test_optimized_primary_range_repair_with_lcs
[
https://issues.apache.org/jira/browse/CASSANDRA-17892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17892:
-
Resolution: Duplicate
Status: Resolved (was: Open)
> Test Failure:
> dtest-novnode.transient_replication_test.TestTransientReplicationRepairLegacyStreaming.test_optimized_primary_range_repair_with_lcs
>
> --
>
> Key: CASSANDRA-17892
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17892
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Josh McKenzie
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> Link to failure:
> https://ci-cassandra.apache.org/job/Cassandra-4.1/162/testReport/dtest-novnode.transient_replication_test/TestTransientReplicationRepairLegacyStreaming/test_optimized_primary_range_repair_with_lcs/
> Error Message
> {code}
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.1',
> '--port', '8778', 'start', '7601')' returned non-zero exit status 1.
> Stacktrace
> if check and retcode:
> > raise CalledProcessError(retcode, process.args,
> output=stdout, stderr=stderr)
> E subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.1',
> '--port', '8778', 'start', '7601')' returned non-zero exit status 1.
> {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-17922) Jolokia agent fails to connect though port is available
[
https://issues.apache.org/jira/browse/CASSANDRA-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17922:
-
Description:
In CASSANDRA-17872 we added protection around failures similar to this, caused
by the port being in use, which is no longer the case:
{code}
subprocess.CalledProcessError: Command
'('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '{-}cp',
'/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
'org.jolokia.jvmagent.client.AgentLauncher', '{-}{-}host', '127.0.0.2',
'{-}-port', '8778', 'start', '1123')' returned non-zero exit status 1.
{code}
[https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/]
was:
In CASSANDRA-17872 we added protection around failures similar to this, caused
by the port being in use, which is no longer the case:
subprocess.CalledProcessError: Command
'('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp',
'/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.2', '--port',
'8778', 'start', '1123')' returned non-zero exit status 1.
https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/
> Jolokia agent fails to connect though port is available
> ---
>
> Key: CASSANDRA-17922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> In CASSANDRA-17872 we added protection around failures similar to this,
> caused by the port being in use, which is no longer the case:
> {code}
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '{-}cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '{-}{-}host', '127.0.0.2',
> '{-}-port', '8778', 'start', '1123')' returned non-zero exit status 1.
> {code}
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/]
--
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-17922) Jolokia agent fails to connect though port is available
[
https://issues.apache.org/jira/browse/CASSANDRA-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609671#comment-17609671
]
Brandon Williams commented on CASSANDRA-17922:
--
I think this is only happening on Jenkins now.
> Jolokia agent fails to connect though port is available
> ---
>
> Key: CASSANDRA-17922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> In CASSANDRA-17872 we added protection around failures similar to this,
> caused by the port being in use, which is no longer the case:
>
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.2',
> '--port', '8778', 'start', '1123')' returned non-zero exit status 1.
>
> https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/
--
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-17922) Jolokia agent fails to connect though port is available
[
https://issues.apache.org/jira/browse/CASSANDRA-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17922:
-
Bug Category: Parent values: Availability(12983)
Complexity: Normal
Component/s: Build
Discovered By: DTest
Fix Version/s: 4.1.x
4.x
Severity: Normal
Status: Open (was: Triage Needed)
> Jolokia agent fails to connect though port is available
> ---
>
> Key: CASSANDRA-17922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> In CASSANDRA-17872 we added protection around failures similar to this,
> caused by the port being in use, which is no longer the case:
>
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.2',
> '--port', '8778', 'start', '1123')' returned non-zero exit status 1.
>
> https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/
--
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-17922) Jolokia agent fails to connect though port is available
Brandon Williams created CASSANDRA-17922:
Summary: Jolokia agent fails to connect though port is available
Key: CASSANDRA-17922
URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
Project: Cassandra
Issue Type: Bug
Reporter: Brandon Williams
In CASSANDRA-17872 we added protection around failures similar to this, caused
by the port being in use, which is no longer the case:
subprocess.CalledProcessError: Command
'('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '-cp',
'/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
'org.jolokia.jvmagent.client.AgentLauncher', '--host', '127.0.0.2', '--port',
'8778', 'start', '1123')' returned non-zero exit status 1.
https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/
--
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-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17876: -- Fix Version/s: (was: 4.1.x) > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Labels: pull-request-available > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17876: - Fix Version/s: 4.1.x (was: 4.1-beta) > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Labels: pull-request-available > Fix For: 4.1.x, 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17876: -- Status: Ready to Commit (was: Review In Progress) > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Labels: pull-request-available > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17876: -- Fix Version/s: 4.1-beta > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Labels: pull-request-available > Fix For: 4.1-beta, 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17876: -- Reviewers: Brandon Williams Status: Review In Progress (was: Patch Available) > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Labels: pull-request-available > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17876: -- Test and Documentation Plan: ci Status: Patch Available (was: In Progress) > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Labels: pull-request-available > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609667#comment-17609667 ] Stefan Miklosovic commented on CASSANDRA-17876: --- The already existing code_style.adoc seems to be a good fit. I will merge this (1) after I commit into the Cassandra repository. (1) https://github.com/apache/cassandra-website/pull/174/files > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Labels: pull-request-available > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17921) Harden JMX by resolving beanshooter issues
[ https://issues.apache.org/jira/browse/CASSANDRA-17921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17921: --- Bug Category: Parent values: Security(12985)Level 1 values: Privilege Escalation(13000) Complexity: Normal Discovered By: User Report Reviewers: Jon Meredith, Michael Semb Wever, Sam Tunnicliffe Severity: Low Assignee: Abe Ratnofsky Status: Open (was: Triage Needed) > Harden JMX by resolving beanshooter issues > -- > > Key: CASSANDRA-17921 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17921 > Project: Cassandra > Issue Type: Bug > Components: Observability/JMX >Reporter: Michael Semb Wever >Assignee: Abe Ratnofsky >Priority: Normal > > … -- 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-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-17876: --- Labels: pull-request-available (was: ) > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Labels: pull-request-available > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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] [Created] (CASSANDRA-17921) Harden JMX by resolving beanshooter issues
Michael Semb Wever created CASSANDRA-17921: -- Summary: Harden JMX by resolving beanshooter issues Key: CASSANDRA-17921 URL: https://issues.apache.org/jira/browse/CASSANDRA-17921 Project: Cassandra Issue Type: Bug Components: Observability/JMX Reporter: Michael Semb Wever … -- 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] [Assigned] (CASSANDRA-17329) Fix failing test - dtest-upgrade.upgrade_internal_auth_test.TestAuthUpgrade.test_upgrade_legacy_tabl
[ https://issues.apache.org/jira/browse/CASSANDRA-17329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-17329: Assignee: (was: Brandon Williams) > Fix failing test - > dtest-upgrade.upgrade_internal_auth_test.TestAuthUpgrade.test_upgrade_legacy_tabl > > > Key: CASSANDRA-17329 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17329 > Project: Cassandra > Issue Type: Bug > Components: Feature/Authorization >Reporter: Brandon Williams >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > Failed 6 times in the last 16 runs. Flakiness: 60%, Stability: 62% > Error Message > ccmlib.node.TimeoutError: 26 Jan 2022 22:48:51 [node1] after 120.17/120 > seconds Missing: ['Listening for thrift clients...'] not found in system.log: > Head: INFO [main] 2022-01-26 22:46:51,840 YamlConfigura Tail: ...ing > legacy permissions data INFO [OptionalTasks:1] 2022-01-26 22:47:08,405 > CassandraAuthorizer.java:444 - Completed conversion of legacy permissions -- 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
[cassandra-website] branch asf-staging updated (a9d096e38 -> a312f5508)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard a9d096e38 generate docs for 538513bd add 2db0aea21 Sept 2022 blog "Learn How CommitLog Works in Apache Cassandra" new a312f5508 generate docs for 2db0aea2 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (a9d096e38) \ N -- N -- N refs/heads/asf-staging (a312f5508) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../blog/Allocating-and-active-segments.png| Bin 0 -> 661957 bytes .../_/_images/blog/Compressed-Segment-layout.png | Bin 0 -> 54667 bytes content/_/_images/blog/Dirty-intervals.png | Bin 0 -> 23619 bytes .../_/_images/blog/Encrypted-Segment-layout.png| Bin 0 -> 93448 bytes ...rks-in-Apache-Cassandra-unsplash-sandip-roy.jpg | Bin 0 -> 158681 bytes content/_/_images/blog/Memtables-and-CommitLog.png | Bin 0 -> 113334 bytes content/_/_images/blog/Mmaped-Segment-layout.png | Bin 0 -> 54194 bytes content/_/_images/blog/Segment layout.png | Bin 0 -> 52523 bytes content/_/blog.html| 24 + ...rn-How-CommitLog-Works-in-Apache-Cassandra.html | 481 + content/search-index.js| 2 +- .../images/blog/Allocating-and-active-segments.png | Bin 0 -> 661957 bytes .../ROOT/images/blog/Compressed-Segment-layout.png | Bin 0 -> 54667 bytes .../modules/ROOT/images/blog/Dirty-intervals.png | Bin 0 -> 23619 bytes .../ROOT/images/blog/Encrypted-Segment-layout.png | Bin 0 -> 93448 bytes ...rks-in-Apache-Cassandra-unsplash-sandip-roy.jpg | Bin 0 -> 158681 bytes .../ROOT/images/blog/Memtables-and-CommitLog.png | Bin 0 -> 113334 bytes .../ROOT/images/blog/Mmaped-Segment-layout.png | Bin 0 -> 54194 bytes .../modules/ROOT/images/blog/Segment layout.png| Bin 0 -> 52523 bytes site-content/source/modules/ROOT/pages/blog.adoc | 25 ++ ...rn-How-CommitLog-Works-in-Apache-Cassandra.adoc | 139 ++ site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 bytes 22 files changed, 670 insertions(+), 1 deletion(-) create mode 100644 content/_/_images/blog/Allocating-and-active-segments.png create mode 100644 content/_/_images/blog/Compressed-Segment-layout.png create mode 100644 content/_/_images/blog/Dirty-intervals.png create mode 100644 content/_/_images/blog/Encrypted-Segment-layout.png create mode 100644 content/_/_images/blog/Learn-How-CommitLog-Works-in-Apache-Cassandra-unsplash-sandip-roy.jpg create mode 100644 content/_/_images/blog/Memtables-and-CommitLog.png create mode 100644 content/_/_images/blog/Mmaped-Segment-layout.png create mode 100644 content/_/_images/blog/Segment layout.png create mode 100644 content/_/blog/Learn-How-CommitLog-Works-in-Apache-Cassandra.html create mode 100644 site-content/source/modules/ROOT/images/blog/Allocating-and-active-segments.png create mode 100644 site-content/source/modules/ROOT/images/blog/Compressed-Segment-layout.png create mode 100644 site-content/source/modules/ROOT/images/blog/Dirty-intervals.png create mode 100644 site-content/source/modules/ROOT/images/blog/Encrypted-Segment-layout.png create mode 100644 site-content/source/modules/ROOT/images/blog/Learn-How-CommitLog-Works-in-Apache-Cassandra-unsplash-sandip-roy.jpg create mode 100644 site-content/source/modules/ROOT/images/blog/Memtables-and-CommitLog.png create mode 100644 site-content/source/modules/ROOT/images/blog/Mmaped-Segment-layout.png create mode 100644 site-content/source/modules/ROOT/images/blog/Segment layout.png create mode 100644 site-content/source/modules/ROOT/pages/blog/Learn-How-CommitLog-Works-in-Apache-Cassandra.adoc - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609656#comment-17609656 ] Brandon Williams commented on CASSANDRA-17876: -- [ide.adoc|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/ide.adoc] covers some build targets too. > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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] [Comment Edited] (CASSANDRA-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609655#comment-17609655 ] Stefan Miklosovic edited comment on CASSANDRA-17876 at 9/26/22 6:52 PM: Thanks for the review. I was thinking about the documentation and I do not know where to actually put it. I think it should be in the website repository. There is "development" folder but no page is suitable to put the documentation in. The best way would be to create a dedicated "ant targets page" where the most important targets would be enumerated with a description what it does. Having no-javadoc and no-checkstyle options covered in that page seems to be a good idea. wdyt? edit: maybe I can put it somewhere in testing.adoc in website repo, that seems to be sufficient. was (Author: smiklosovic): Thanks for the review. I was thinking about the documentation and I do not know where to actually put it. I think it should be in the website repository. There is "development" folder but no page is suitable to put the documentation in. The best way would be to create a dedicated "ant targets page" where the most important targets would be enumerated with a description what it does. Having no-javadoc and no-checkstyle options covered in that page seems to be a good idea. wdyt? > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
[
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-17461:
---
Fix Version/s: 4.1
(was: 4.x)
> Test Failure:
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Blake Eggleston
>Priority: Normal
> Fix For: 4.1-beta, 4.1
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}}
> for trunk:
> *
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> *
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> *
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> *
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed
> out: received 1 of 2 required responses after 0 contention retries
> at
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
> at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
> at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan
> these urls:
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
> file:/home/cassandra/cassandra/build/classes/fqltool/,
> file:/home/cassandra/cassandra/build/test/classes/,
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node1_isolatedExecutor:10] node1
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging
> service to quiesce
> INFO [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node2_isolatedExecutor:8] node2 2022-03-19
> 16:21:55,222 MessagingService.java:519 - Waiting for messaging service to
> quiesce
> {code}
> Failures can also be repeatedly hit with CircleCI test multiplexer:
>
[jira] [Comment Edited] (CASSANDRA-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609655#comment-17609655 ] Stefan Miklosovic edited comment on CASSANDRA-17876 at 9/26/22 6:50 PM: Thanks for the review. I was thinking about the documentation and I do not know where to actually put it. I think it should be in the website repository. There is "development" folder but no page is suitable to put the documentation in. The best way would be to create a dedicated "ant targets page" where the most important targets would be enumerated with a description what it does. Having no-javadoc and no-checkstyle options covered in that page seems to be a good idea. wdyt? was (Author: smiklosovic): Thanks for the review. I was thinking about the documentation and I do not know where to actually put it. I think it should be in the website repository. There is "development" folder but no page is suitable to put the documentation in. The best way would be to create a dedicated "ant targets page" where the most important targets would be enumerate with a description what it does. Having no-javadoc and no-checkstyle options covered in that page seems to be a good idea. wdyt? > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609655#comment-17609655 ] Stefan Miklosovic commented on CASSANDRA-17876: --- Thanks for the review. I was thinking about the documentation and I do not know where to actually put it. I think it should be in the website repository. There is "development" folder but no page is suitable to put the documentation in. The best way would be to create a dedicated "ant targets page" where the most important targets would be enumerate with a description what it does. Having no-javadoc and no-checkstlye options covered in that page seems to be a good idea. wdyt? > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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] [Comment Edited] (CASSANDRA-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609655#comment-17609655 ] Stefan Miklosovic edited comment on CASSANDRA-17876 at 9/26/22 6:49 PM: Thanks for the review. I was thinking about the documentation and I do not know where to actually put it. I think it should be in the website repository. There is "development" folder but no page is suitable to put the documentation in. The best way would be to create a dedicated "ant targets page" where the most important targets would be enumerate with a description what it does. Having no-javadoc and no-checkstyle options covered in that page seems to be a good idea. wdyt? was (Author: smiklosovic): Thanks for the review. I was thinking about the documentation and I do not know where to actually put it. I think it should be in the website repository. There is "development" folder but no page is suitable to put the documentation in. The best way would be to create a dedicated "ant targets page" where the most important targets would be enumerate with a description what it does. Having no-javadoc and no-checkstlye options covered in that page seems to be a good idea. wdyt? > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17860) WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"
[ https://issues.apache.org/jira/browse/CASSANDRA-17860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17860: --- Fix Version/s: NA Source Control Link: https://github.com/apache/cassandra-website/commit/2db0aea213a6b73b72d9c386c29585f7a1361977 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as [2db0aea213a6b73b72d9c386c29585f7a1361977|https://github.com/apache/cassandra-website/commit/2db0aea213a6b73b72d9c386c29585f7a1361977]. > WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra" > -- > > Key: CASSANDRA-17860 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17860 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Alex Sorokoumov >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > This ticket is to capture the work associated with publishing the September > 2022 blog "Learn How CommitLog Works in Apache Cassandra" > If this blog cannot be published by the *September 15, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- 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
[cassandra-website] branch trunk updated: Sept 2022 blog "Learn How CommitLog Works in Apache Cassandra"
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/trunk by this push: new 2db0aea21 Sept 2022 blog "Learn How CommitLog Works in Apache Cassandra" 2db0aea21 is described below commit 2db0aea213a6b73b72d9c386c29585f7a1361977 Author: Diogenese Topper AuthorDate: Wed Sep 14 18:59:24 2022 -0700 Sept 2022 blog "Learn How CommitLog Works in Apache Cassandra" patch by Alex Sorokoumov, Chris Thornett, Diogenese Topper; reviewed by Mick Semb Wever for CASSANDRA-17860 Co-authored by: Alex Sorokoumov Co-authored by: Chris Thornett Co-authored by: Diogenese Topper --- .../images/blog/Allocating-and-active-segments.png | Bin 0 -> 661957 bytes .../ROOT/images/blog/Compressed-Segment-layout.png | Bin 0 -> 54667 bytes .../modules/ROOT/images/blog/Dirty-intervals.png | Bin 0 -> 23619 bytes .../ROOT/images/blog/Encrypted-Segment-layout.png | Bin 0 -> 93448 bytes ...rks-in-Apache-Cassandra-unsplash-sandip-roy.jpg | Bin 0 -> 158681 bytes .../ROOT/images/blog/Memtables-and-CommitLog.png | Bin 0 -> 113334 bytes .../ROOT/images/blog/Mmaped-Segment-layout.png | Bin 0 -> 54194 bytes .../modules/ROOT/images/blog/Segment layout.png| Bin 0 -> 52523 bytes site-content/source/modules/ROOT/pages/blog.adoc | 25 ...rn-How-CommitLog-Works-in-Apache-Cassandra.adoc | 139 + 10 files changed, 164 insertions(+) diff --git a/site-content/source/modules/ROOT/images/blog/Allocating-and-active-segments.png b/site-content/source/modules/ROOT/images/blog/Allocating-and-active-segments.png new file mode 100644 index 0..939b6d4a8 Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/Allocating-and-active-segments.png differ diff --git a/site-content/source/modules/ROOT/images/blog/Compressed-Segment-layout.png b/site-content/source/modules/ROOT/images/blog/Compressed-Segment-layout.png new file mode 100644 index 0..18f19d188 Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/Compressed-Segment-layout.png differ diff --git a/site-content/source/modules/ROOT/images/blog/Dirty-intervals.png b/site-content/source/modules/ROOT/images/blog/Dirty-intervals.png new file mode 100644 index 0..30e7676d4 Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/Dirty-intervals.png differ diff --git a/site-content/source/modules/ROOT/images/blog/Encrypted-Segment-layout.png b/site-content/source/modules/ROOT/images/blog/Encrypted-Segment-layout.png new file mode 100644 index 0..bfaa3654d Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/Encrypted-Segment-layout.png differ diff --git a/site-content/source/modules/ROOT/images/blog/Learn-How-CommitLog-Works-in-Apache-Cassandra-unsplash-sandip-roy.jpg b/site-content/source/modules/ROOT/images/blog/Learn-How-CommitLog-Works-in-Apache-Cassandra-unsplash-sandip-roy.jpg new file mode 100644 index 0..2e1224b27 Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/Learn-How-CommitLog-Works-in-Apache-Cassandra-unsplash-sandip-roy.jpg differ diff --git a/site-content/source/modules/ROOT/images/blog/Memtables-and-CommitLog.png b/site-content/source/modules/ROOT/images/blog/Memtables-and-CommitLog.png new file mode 100644 index 0..b0a6034ac Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/Memtables-and-CommitLog.png differ diff --git a/site-content/source/modules/ROOT/images/blog/Mmaped-Segment-layout.png b/site-content/source/modules/ROOT/images/blog/Mmaped-Segment-layout.png new file mode 100644 index 0..63a1269af Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/Mmaped-Segment-layout.png differ diff --git a/site-content/source/modules/ROOT/images/blog/Segment layout.png b/site-content/source/modules/ROOT/images/blog/Segment layout.png new file mode 100644 index 0..fc2168021 Binary files /dev/null and b/site-content/source/modules/ROOT/images/blog/Segment layout.png differ diff --git a/site-content/source/modules/ROOT/pages/blog.adoc b/site-content/source/modules/ROOT/pages/blog.adoc index 2820f57be..4d74c1b7c 100644 --- a/site-content/source/modules/ROOT/pages/blog.adoc +++ b/site-content/source/modules/ROOT/pages/blog.adoc @@ -8,6 +8,31 @@ NOTES FOR CONTENT CREATORS - Replace post tile, date, description and link to you post. +//start card +[openblock,card shadow relative test] + +[openblock,card-header] +-- +[discrete] +=== Learn How CommitLog Works in Apache Cassandra +[discrete] + September 26, 2022 +-- +[openblock,card-content] +-- +Learn how Apache Cassandra’s CommittLog works, how Cassandra ensures data durability, and how various tuning parameters affect its behavior. +
[jira] [Updated] (CASSANDRA-17860) WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"
[ https://issues.apache.org/jira/browse/CASSANDRA-17860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17860: --- Reviewers: Michael Semb Wever Status: Review In Progress (was: Patch Available) > WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra" > -- > > Key: CASSANDRA-17860 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17860 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Alex Sorokoumov >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with publishing the September > 2022 blog "Learn How CommitLog Works in Apache Cassandra" > If this blog cannot be published by the *September 15, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- 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-17860) WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra"
[ https://issues.apache.org/jira/browse/CASSANDRA-17860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17860: --- Status: Ready to Commit (was: Review In Progress) > WEBSITE - August 2022 blog "Learn How CommitLog Works in Apache Cassandra" > -- > > Key: CASSANDRA-17860 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17860 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Alex Sorokoumov >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with publishing the September > 2022 blog "Learn How CommitLog Works in Apache Cassandra" > If this blog cannot be published by the *September 15, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- 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-17810) Revise timeout handling on queries triggering timeout introduced by CASSANDRA-7392
[
https://issues.apache.org/jira/browse/CASSANDRA-17810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17810:
--
Fix Version/s: 4.2
Since Version: 3.2
Source Control Link:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=f4b69ba0e82bb051e56a92d792142034d9f617f0
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Revise timeout handling on queries triggering timeout introduced by
> CASSANDRA-7392
> --
>
> Key: CASSANDRA-17810
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17810
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.2
>
>
> In situations where a replica times out with the code introduced in
> CASSANDRA-7392, they drop the timed-out query on the floor without notifying
> the coordinator; this doesn't become apparent coordinator-side until we go to
> serialize the response. While the results of this (i.e. missed data) should
> mostly be fixed by short read protection on repeat requests, the coordinator
> can in some cases throw an exception like {{IllegalStateException:
> UnfilteredRowIterator for keyspace.table has an open RT bound as its last
> item}} which is decidedly unfriendly.
> We should introduce a specific exception to allow replicas to notify a
> coordinator something has timed out and been dropped on the floor so the
> coordinator can appropriately handle that scenario and abort the query at
> that time.
--
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
[cassandra] branch trunk updated: Fix "open RT bound as its last item" exception
This is an automated email from the ASF dual-hosted git repository.
jmckenzie pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new f4b69ba0e8 Fix "open RT bound as its last item" exception
f4b69ba0e8 is described below
commit f4b69ba0e82bb051e56a92d792142034d9f617f0
Author: Josh McKenzie
AuthorDate: Mon Sep 19 14:49:10 2022 -0400
Fix "open RT bound as its last item" exception
Patch by Marcus Eriksson; reviewed by Aleksey Yeschenko and Josh McKenzie
for CASSANDRA-17810
Co-authored-by: Marcus Eriksson
Co-authored-by: Josh McKenzie
---
CHANGES.txt| 1 +
src/java/org/apache/cassandra/db/ReadCommand.java | 125 -
.../cassandra/db/ReadCommandVerbHandler.java | 26 +++--
.../cassandra/db/transform/RTBoundValidator.java | 45
.../exceptions/QueryCancelledException.java| 28 +
.../org/apache/cassandra/service/StorageProxy.java | 17 ++-
.../distributed/test/TimeoutAbortTest.java | 62 ++
.../org/apache/cassandra/db/ReadCommandTest.java | 34 +-
8 files changed, 249 insertions(+), 89 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 60e5f976e5..bda1ba04d7 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
4.2
+ * Fix "open RT bound as its last item" exception (CASSANDRA-17810)
* Fix leak of non-standard Java types in JMX MBeans
`org.apache.cassandra.db:type=StorageService`
and `org.apache.cassandra.db:type=RepairService` as clients using JMX
cannot handle them. More details in NEWS.txt (CASSANDRA-17668)
* Deprecate Throwables.propagate usage (CASSANDRA-14218)
diff --git a/src/java/org/apache/cassandra/db/ReadCommand.java
b/src/java/org/apache/cassandra/db/ReadCommand.java
index 358d408919..ae64710005 100644
--- a/src/java/org/apache/cassandra/db/ReadCommand.java
+++ b/src/java/org/apache/cassandra/db/ReadCommand.java
@@ -36,6 +36,7 @@ import org.slf4j.LoggerFactory;
import io.netty.util.concurrent.FastThreadLocal;
import org.apache.cassandra.config.*;
import org.apache.cassandra.db.filter.*;
+import org.apache.cassandra.exceptions.QueryCancelledException;
import org.apache.cassandra.net.MessageFlag;
import org.apache.cassandra.net.ParamType;
import org.apache.cassandra.net.Verb;
@@ -422,7 +423,8 @@ public abstract class ReadCommand extends AbstractReadQuery
try
{
iterator = withQuerySizeTracking(iterator);
-iterator = withStateTracking(iterator);
+iterator = maybeSlowDownForTesting(iterator);
+iterator = withQueryCancellation(iterator);
iterator =
RTBoundValidator.validate(withoutPurgeableTombstones(iterator, cfs,
executionController), Stage.PURGED, false);
iterator = withMetricsRecording(iterator, cfs.metric,
startTimeNanos);
@@ -601,58 +603,6 @@ public abstract class ReadCommand extends AbstractReadQuery
return Transformation.apply(iter, new MetricRecording());
}
-protected class CheckForAbort extends
StoppingTransformation
-{
-long lastChecked = 0;
-
-protected UnfilteredRowIterator applyToPartition(UnfilteredRowIterator
partition)
-{
-if (maybeAbort())
-{
-partition.close();
-return null;
-}
-
-return Transformation.apply(partition, this);
-}
-
-protected Row applyToRow(Row row)
-{
-if (TEST_ITERATION_DELAY_MILLIS > 0)
-maybeDelayForTesting();
-
-return maybeAbort() ? null : row;
-}
-
-private boolean maybeAbort()
-{
-/**
- * TODO: this is not a great way to abort early; why not expressly
limit checks to 10ms intervals?
- * The value returned by approxTime.now() is updated only every
- * {@link
org.apache.cassandra.utils.MonotonicClock.SampledClock.CHECK_INTERVAL_MS}, by
default 2 millis. Since MonitorableImpl
- * relies on approxTime, we don't need to check unless the
approximate time has elapsed.
- */
-if (lastChecked == approxTime.now())
-return false;
-
-lastChecked = approxTime.now();
-
-if (isAborted())
-{
-stop();
-return true;
-}
-
-return false;
-}
-
-private void maybeDelayForTesting()
-{
-if (!metadata().keyspace.startsWith("system"))
-FBUtilities.sleepQuietly(TEST_ITERATION_DELAY_MILLIS);
-}
-}
-
private boolean shouldTrackSize(DataStorageSpec.LongBytesBound
warnThresholdBytes, DataStorageSpec.LongBytesBound abortThresholdBytes)
{
return trackWarnings
@@ -737,9 +687,74 @@
[jira] [Commented] (CASSANDRA-17884) Test failure: o.a.c.repair.RepairJobTest.testNoTreesRetainedAfterDifference
[
https://issues.apache.org/jira/browse/CASSANDRA-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609611#comment-17609611
]
Ekaterina Dimitrova commented on CASSANDRA-17884:
-
The issue is hit very rarely in this test with JDK11 on 4.0+.
> Test failure: o.a.c.repair.RepairJobTest.testNoTreesRetainedAfterDifference
> ---
>
> Key: CASSANDRA-17884
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17884
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> The unit test
> {{org.apache.cassandra.repair.RepairJobTest#testNoTreesRetainedAfterDifference}}
> seems to be slightly flaky at least in 4.0. We haven't seen it failing on
> Butler, but after [a failure on a patch
> branch|https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/281/workflows/e6094c00-b611-4772-9772-205f4c76ecba/jobs/2126/tests],
> this repeated run shows a 0.28% flakiness:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2076/workflows/8adbfe99-afb5-43af-84ad-43df2a2a86e2/jobs/20816/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2076/workflows/e550d8c2-7c35-4326-bd95-6909978d344b/jobs/20817/tests
> {code}
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> jdk.internal.platform.cgroupv1.SubSystem$MemorySubSystem
> jdk.internal.platform.cgroupv1.Metrics.memory accessible: module java.base
> does not "opens jdk.internal.platform.cgroupv1" to unnamed module @157853da
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at
> java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)
> at org.github.jamm.MemoryMeter.addFieldChildren(MemoryMeter.java:330)
> at org.github.jamm.MemoryMeter.measureDeep(MemoryMeter.java:269)
> at
> org.apache.cassandra.utils.ObjectSizes.measureDeep(ObjectSizes.java:216)
> at
> org.apache.cassandra.repair.RepairJobTest.testNoTreesRetainedAfterDifference(RepairJobTest.java:271)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is really low but the failure is clearly reproducible in j11.
--
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-17884) Test failure: o.a.c.repair.RepairJobTest.testNoTreesRetainedAfterDifference
[
https://issues.apache.org/jira/browse/CASSANDRA-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17884:
Complexity: Normal
Discovered By: User Report
Severity: Normal
Status: Open (was: Triage Needed)
> Test failure: o.a.c.repair.RepairJobTest.testNoTreesRetainedAfterDifference
> ---
>
> Key: CASSANDRA-17884
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17884
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> The unit test
> {{org.apache.cassandra.repair.RepairJobTest#testNoTreesRetainedAfterDifference}}
> seems to be slightly flaky at least in 4.0. We haven't seen it failing on
> Butler, but after [a failure on a patch
> branch|https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/281/workflows/e6094c00-b611-4772-9772-205f4c76ecba/jobs/2126/tests],
> this repeated run shows a 0.28% flakiness:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2076/workflows/8adbfe99-afb5-43af-84ad-43df2a2a86e2/jobs/20816/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2076/workflows/e550d8c2-7c35-4326-bd95-6909978d344b/jobs/20817/tests
> {code}
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> jdk.internal.platform.cgroupv1.SubSystem$MemorySubSystem
> jdk.internal.platform.cgroupv1.Metrics.memory accessible: module java.base
> does not "opens jdk.internal.platform.cgroupv1" to unnamed module @157853da
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at
> java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)
> at org.github.jamm.MemoryMeter.addFieldChildren(MemoryMeter.java:330)
> at org.github.jamm.MemoryMeter.measureDeep(MemoryMeter.java:269)
> at
> org.apache.cassandra.utils.ObjectSizes.measureDeep(ObjectSizes.java:216)
> at
> org.apache.cassandra.repair.RepairJobTest.testNoTreesRetainedAfterDifference(RepairJobTest.java:271)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is really low but the failure is clearly reproducible in j11.
--
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-17884) Test failure: o.a.c.repair.RepairJobTest.testNoTreesRetainedAfterDifference
[
https://issues.apache.org/jira/browse/CASSANDRA-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17884:
Fix Version/s: 4.0.x
4.1.x
4.x
> Test failure: o.a.c.repair.RepairJobTest.testNoTreesRetainedAfterDifference
> ---
>
> Key: CASSANDRA-17884
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17884
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> The unit test
> {{org.apache.cassandra.repair.RepairJobTest#testNoTreesRetainedAfterDifference}}
> seems to be slightly flaky at least in 4.0. We haven't seen it failing on
> Butler, but after [a failure on a patch
> branch|https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/281/workflows/e6094c00-b611-4772-9772-205f4c76ecba/jobs/2126/tests],
> this repeated run shows a 0.28% flakiness:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2076/workflows/8adbfe99-afb5-43af-84ad-43df2a2a86e2/jobs/20816/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2076/workflows/e550d8c2-7c35-4326-bd95-6909978d344b/jobs/20817/tests
> {code}
> java.lang.reflect.InaccessibleObjectException: Unable to make field private
> jdk.internal.platform.cgroupv1.SubSystem$MemorySubSystem
> jdk.internal.platform.cgroupv1.Metrics.memory accessible: module java.base
> does not "opens jdk.internal.platform.cgroupv1" to unnamed module @157853da
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)
> at
> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)
> at
> java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:176)
> at java.base/java.lang.reflect.Field.setAccessible(Field.java:170)
> at org.github.jamm.MemoryMeter.addFieldChildren(MemoryMeter.java:330)
> at org.github.jamm.MemoryMeter.measureDeep(MemoryMeter.java:269)
> at
> org.apache.cassandra.utils.ObjectSizes.measureDeep(ObjectSizes.java:216)
> at
> org.apache.cassandra.repair.RepairJobTest.testNoTreesRetainedAfterDifference(RepairJobTest.java:271)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is really low but the failure is clearly reproducible in j11.
--
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-16304) Consider implementing ClusteringComparator without a lambda
[
https://issues.apache.org/jira/browse/CASSANDRA-16304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609610#comment-17609610
]
Ekaterina Dimitrova commented on CASSANDRA-16304:
-
For the record, these were some tests identified to hit the issue when running
with jdk 17 as part of POC in CASSANDRA-16895:
_testPreparedBatch, testReprepareNewBehaviour, testUseWithMultipleKeyspaces,
testReprepareTwoKeyspacesNewBehaviour, fuzzTest, startupNewIP,
sameIPFailWithoutReplace, sameIPFailWithoutReplace, mixedModeFuzzTest_
> Consider implementing ClusteringComparator without a lambda
> ---
>
> Key: CASSANDRA-16304
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16304
> Project: Cassandra
> Issue Type: Improvement
> Components: Build
>Reporter: Adrian Cole
>Priority: Normal
> Fix For: 4.x
>
>
> Using lambdas forces jamm to do things that can easily break. It might be
> safer to implement things like ClusteringComparator directly as classes or as
> an enum
> {noformat}
> Unexpected exception during request
> (org.apache.cassandra.transport.messages.ErrorMessage)
> java.lang.UnsupportedOperationException: can't get field offset on a hidden
> class: private final org.apache.cassandra.db.ClusteringComparator
> org.apache.cassandra.db.ClusteringComparator$$Lambda$165/0x00010028ab60.arg$1
> at jdk.unsupported/sun.misc.Unsafe.objectFieldOffset(Unknown Source)
> at
> org.github.jamm.MemoryLayoutSpecification.sizeOfInstanceWithUnsafe(MemoryLayoutSpecification.java:108)
> at
> org.github.jamm.MemoryLayoutSpecification.sizeOfWithUnsafe(MemoryLayoutSpecification.java:89)
> at org.github.jamm.MemoryMeter.measure(MemoryMeter.java:217)
> at org.github.jamm.MemoryMeter.measureDeep(MemoryMeter.java:259)
> at
> org.apache.cassandra.utils.ObjectSizes.measureDeep(ObjectSizes.java:155)
> at
> org.apache.cassandra.cql3.QueryProcessor.storePreparedStatement(QueryProcessor.java:454)
> at
> org.apache.cassandra.cql3.QueryProcessor.prepare(QueryProcessor.java:424)
> at
> org.apache.cassandra.cql3.QueryProcessor.prepare(QueryProcessor.java:408)
> at
> org.apache.cassandra.transport.messages.PrepareMessage.execute(PrepareMessage.java:114)
> at
> org.apache.cassandra.transport.Message$Request.execute(Message.java:253)
> at
> org.apache.cassandra.transport.Message$Dispatcher.processRequest(Message.java:725)
> at
> org.apache.cassandra.transport.Message$Dispatcher.lambda$channelRead0$0(Message.java:630)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Unknown Source)
> {noformat}
--
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-17870) nodetool/rebuild: Add flag to exclude nodes from local datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-17870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609606#comment-17609606
]
Francisco Guerrero commented on CASSANDRA-17870:
{quote}
Why prefer excluding the local DC instead of setting a source DC?
{quote}
[~yifanc] This would be for the case where you are building out a new DC, and
your local [new] DC nodes do not have data yet. There's already a way to
specify a *{{src-dc-name}}* (which can be the local DC)
[see|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/tools/nodetool/Rebuild.java#L30].
> nodetool/rebuild: Add flag to exclude nodes from local datacenter
> -
>
> Key: CASSANDRA-17870
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17870
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
>Reporter: Saranya Krishnakumar
>Assignee: Saranya Krishnakumar
>Priority: Normal
> Attachments: fix_nodetool_rebuild.diff
>
>
> During expansion by Dc, when we issue nodetool/rebuild from new dc to rebuild
> the data from other DCs. If src-dc is not passed explicitly, then C* tries to
> rebuild the data from the same (new dc) dc.
> We don’t exclude other nodes in the same DC. Only down sources and the local
> node itself are excluded.
> ```
> // We're _always_ filtering out a local node and down sources
> addSourceFilter(new
> RangeStreamer.FailureDetectorSourceFilter(failureDetector));
> addSourceFilter(new RangeStreamer.ExcludeLocalNodeFilter());
> ```
> We should fix nodetool/rebuild to exclude the local DC (from where we’re
> executing the command) while issuing nodetool/rebuild without passing src dc
--
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] [Comment Edited] (CASSANDRA-16092) Add Index Group Interface for Storage Attached Index
[ https://issues.apache.org/jira/browse/CASSANDRA-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609595#comment-17609595 ] Caleb Rackliffe edited comment on CASSANDRA-16092 at 9/26/22 5:01 PM: -- bq. Should this ticket be resolved fixed then? The changes in isolation have been co-authored and reviewed by 3 committers, all of whom have insight into how this interface is already in use outside OSS. If there are issues at this point, I think they would pop up in relation to integration that happens in another issue (i.e. one also under the general umbrella of CASSANDRA-16052), where we would have appropriate space to discuss and address. WDYT? Indeed, we don't have much precedent for this kind of thing. was (Author: maedhroz): bq. Should this ticket be resolved fixed then? The changes in isolation have been co-authored and reviewed by 3 committers, all of whom have insight into how this interface is already in use outside OSS. If there are issues at this point, I think they would pop up in relation to integration that happens in another issue (i.e. one also under the general umbrella of CASSANDRA-16052), where we would have appropriate space to discuss and address. WDYT? > Add Index Group Interface for Storage Attached Index > > > Key: CASSANDRA-16092 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16092 > Project: Cassandra > Issue Type: New Feature > Components: Feature/SASI >Reporter: Zhao Yang >Assignee: Zhao Yang >Priority: Normal > Fix For: 4.x > > > [Index > group|https://github.com/datastax/cassandra/blob/storage_attached_index/src/java/org/apache/cassandra/index/Index.java#L634] > interface allows: > * indexes on the same table to receive centralized lifecycle events called > secondary index groups. Sharing of data between multiple column indexes on > the same table allows SAI disk usage to realise significant space savings > over other index implementations. > * index-group to analyze user query and provide a query plan that leverages > all available indexes within the group. -- 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-16092) Add Index Group Interface for Storage Attached Index
[ https://issues.apache.org/jira/browse/CASSANDRA-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609595#comment-17609595 ] Caleb Rackliffe commented on CASSANDRA-16092: - bq. Should this ticket be resolved fixed then? The changes in isolation have been co-authored and reviewed by 3 committers, all of whom have insight into how this interface is already in use outside OSS. If there are issues at this point, I think they would pop up in relation to integration that happens in another issue (i.e. one also under the general umbrella of CASSANDRA-16052), where we would have appropriate space to discuss and address. WDYT? > Add Index Group Interface for Storage Attached Index > > > Key: CASSANDRA-16092 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16092 > Project: Cassandra > Issue Type: New Feature > Components: Feature/SASI >Reporter: Zhao Yang >Assignee: Zhao Yang >Priority: Normal > Fix For: 4.x > > > [Index > group|https://github.com/datastax/cassandra/blob/storage_attached_index/src/java/org/apache/cassandra/index/Index.java#L634] > interface allows: > * indexes on the same table to receive centralized lifecycle events called > secondary index groups. Sharing of data between multiple column indexes on > the same table allows SAI disk usage to realise significant space savings > over other index implementations. > * index-group to analyze user query and provide a query plan that leverages > all available indexes within the group. -- 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-16092) Add Index Group Interface for Storage Attached Index
[ https://issues.apache.org/jira/browse/CASSANDRA-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609588#comment-17609588 ] Michael Semb Wever commented on CASSANDRA-16092: bq. On versioning, I've changed this to 4.x to match the umbrella ticket Thanks! bq. The commit exists in the feature branch for the umbrella ticket, CASSANDRA-16052. Should this ticket be resolved fixed then? (In theory I would have presumed "Ready to Commit", given that someone can still come along and raise review questions/concerns before the final merge happens…) (Is there some/any precedence yet in place for CEP epics and their feature branches…?) > Add Index Group Interface for Storage Attached Index > > > Key: CASSANDRA-16092 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16092 > Project: Cassandra > Issue Type: New Feature > Components: Feature/SASI >Reporter: Zhao Yang >Assignee: Zhao Yang >Priority: Normal > Fix For: 4.x > > > [Index > group|https://github.com/datastax/cassandra/blob/storage_attached_index/src/java/org/apache/cassandra/index/Index.java#L634] > interface allows: > * indexes on the same table to receive centralized lifecycle events called > secondary index groups. Sharing of data between multiple column indexes on > the same table allows SAI disk usage to realise significant space savings > over other index implementations. > * index-group to analyze user query and provide a query plan that leverages > all available indexes within the group. -- 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] [Comment Edited] (CASSANDRA-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609585#comment-17609585 ] Brandon Williams edited comment on CASSANDRA-17876 at 9/26/22 4:44 PM: --- This looks good to me, +1. edit: we should document the "no-checkstyle" option was (Author: brandon.williams): This looks good to me, +1. > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17876) remove the unused imports in the source code and fail builds when they are present
[ https://issues.apache.org/jira/browse/CASSANDRA-17876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609585#comment-17609585 ] Brandon Williams commented on CASSANDRA-17876: -- This looks good to me, +1. > remove the unused imports in the source code and fail builds when they are > present > -- > > Key: CASSANDRA-17876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17876 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Normal > Fix For: 4.2 > > Time Spent: 40m > Remaining Estimate: 0h > > remove the unused imports in the source 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-17719) CEP-15: Multi-partition transaction CQL support
[
https://issues.apache.org/jira/browse/CASSANDRA-17719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609581#comment-17609581
]
Caleb Rackliffe commented on CASSANDRA-17719:
-
[~mck] When this issue resolves, it will almost certainly be committed to a
feature branch for CEP-15 (probably CASSANDRA-17091?), and its version will
therefore depend on that. I've just cleared the release version for now.
> CEP-15: Multi-partition transaction CQL support
> ---
>
> Key: CASSANDRA-17719
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17719
> Project: Cassandra
> Issue Type: New Feature
> Components: Accord, CQL/Syntax
>Reporter: Blake Eggleston
>Assignee: Caleb Rackliffe
>Priority: Normal
>
> The dev list thread regarding CQL transaction support seems to have converged
> on a syntax.
>
> The thread is here:
> [https://lists.apache.org/thread/5sds3968mnnk42c24pvgwphg4qvo2xk0]
>
> The message proposing the syntax ultimately agreed on is here:
> [https://lists.apache.org/thread/y289tczngj68bqpoo7gkso3bzmtf86pl]
>
> I'll describe my understanding of the agreed syntax here for, but I'd
> suggest reading through the thread.
>
> The example query is this:
> {code:sql}
> BEGIN TRANSACTION
> LET car = (SELECT miles_driven, is_running FROM cars WHERE model=’pinto’);
> LET user = (SELECT miles_driven FROM users WHERE name=’Blake’);
> SELECT car.is_running, car.miles_driven;
> IF car.is_running THEN
> UPDATE users SET miles_driven = user.miles_driven + 30 WHERE name='blake';
> UPDATE cars SET miles_driven = car.miles_driven + 30 WHERE model='pinto';
> END IF
> COMMIT TRANSACTION
> {code}
> Sections are described below, and we want to require the statement enforces
> an order on the different types of clauses. First, assignments, then
> select(s), then conditional updates. This may be relaxed in the future, but
> is meant to prevent users from interleaving updates and assignments and
> expecting read your own write behavior that we don't want to support in v1.
> h3. Reference assignments
> {code:sql}
> LET car = (SELECT miles_driven, is_running FROM cars WHERE
> model=’pinto’){code}
>
> The first part is basically assigning the result of a SELECT statement to a
> named reference that can be used in updates/conditions and be returned to the
> user. Tuple names belong to a global scope and must not clash with other LET
> statements or update statements (more on that in the updates section). Also,
> the select statement must either be a point read, with all primary key
> columns defined, or explicitly set a limit of 1.
> h3. Selection
> Data to returned to client. Currently, we're only supporting a single select
> statement. Either a normal select statement, or one returning values assigned
> by LET statements as shown in the example. Ultimately we'll want to support
> multiple select statements and returning the results to the client. Although
> that will require a protocol change.
> h3. Updates
> Normal inserts/updates/deletes with the following extensions:
> * Inserts and updates can reference values assigned earlier in the statement
> * Updates can reference their own columns:
> {code:java}
> miles_driven = miles_driven + 30{code}
> - or -
> {code:java}
> miles_driven += 30{code}
> These will of course need to generate any required reads behind the scenes.
> There's no precedence of table vs reference names, so if a relevant column
> name and reference name conflict, the query needs to fail to parse.
> h3. If blocks
> {code:sql}
> IF THEN
> ;
> ;
> END IF
> {code}
>
> For v1, we only need to support a single condition in the format above. In
> the future, we'd like to support multiple branches with multiple conditions
> like:
>
> {code:sql}
> IF THEN
> ;
> ;
> ELSE IF THEN
> ;
> ELSE
> ;
> END IF
> {code}
>
> h3. Conditions
> Comparisons of value references to literals or other references. IS NULL / IS
> NOT NULL also needs to be supported. Multiple comparisons need to be
> supported, but v1 only needs to support AND'ing them together.
> {code:java}
> Supported operators: =, !=, >, >=, <, <=, IS NULL, IS NOT NULL
> = 5
> IS NOT NULL
> IF car IS NOT NULL AND car.miles_driven > 30
> IF car.miles_driven = user.miles_driven{code}
> (Note that {{IS[ NOT ]NULL}} can apply to both tuple references and
> individually dereferenced columns.)
> CONTAINS and CONTAINS KEY require indexed collections, and will not be
> supported in v1.
> h3. Implementation notes
> I have a proof of concept I'd created to demo the initially proposed syntax
> here: [https://github.com/bdeggleston/cassandra/tree/accord-cql-poc], It
> could be used as a starting point, a source of ideas for approaches, or not
> used at
[jira] [Updated] (CASSANDRA-17719) CEP-15: Multi-partition transaction CQL support
[
https://issues.apache.org/jira/browse/CASSANDRA-17719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-17719:
Fix Version/s: (was: 5.x)
> CEP-15: Multi-partition transaction CQL support
> ---
>
> Key: CASSANDRA-17719
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17719
> Project: Cassandra
> Issue Type: New Feature
> Components: Accord, CQL/Syntax
>Reporter: Blake Eggleston
>Assignee: Caleb Rackliffe
>Priority: Normal
>
> The dev list thread regarding CQL transaction support seems to have converged
> on a syntax.
>
> The thread is here:
> [https://lists.apache.org/thread/5sds3968mnnk42c24pvgwphg4qvo2xk0]
>
> The message proposing the syntax ultimately agreed on is here:
> [https://lists.apache.org/thread/y289tczngj68bqpoo7gkso3bzmtf86pl]
>
> I'll describe my understanding of the agreed syntax here for, but I'd
> suggest reading through the thread.
>
> The example query is this:
> {code:sql}
> BEGIN TRANSACTION
> LET car = (SELECT miles_driven, is_running FROM cars WHERE model=’pinto’);
> LET user = (SELECT miles_driven FROM users WHERE name=’Blake’);
> SELECT car.is_running, car.miles_driven;
> IF car.is_running THEN
> UPDATE users SET miles_driven = user.miles_driven + 30 WHERE name='blake';
> UPDATE cars SET miles_driven = car.miles_driven + 30 WHERE model='pinto';
> END IF
> COMMIT TRANSACTION
> {code}
> Sections are described below, and we want to require the statement enforces
> an order on the different types of clauses. First, assignments, then
> select(s), then conditional updates. This may be relaxed in the future, but
> is meant to prevent users from interleaving updates and assignments and
> expecting read your own write behavior that we don't want to support in v1.
> h3. Reference assignments
> {code:sql}
> LET car = (SELECT miles_driven, is_running FROM cars WHERE
> model=’pinto’){code}
>
> The first part is basically assigning the result of a SELECT statement to a
> named reference that can be used in updates/conditions and be returned to the
> user. Tuple names belong to a global scope and must not clash with other LET
> statements or update statements (more on that in the updates section). Also,
> the select statement must either be a point read, with all primary key
> columns defined, or explicitly set a limit of 1.
> h3. Selection
> Data to returned to client. Currently, we're only supporting a single select
> statement. Either a normal select statement, or one returning values assigned
> by LET statements as shown in the example. Ultimately we'll want to support
> multiple select statements and returning the results to the client. Although
> that will require a protocol change.
> h3. Updates
> Normal inserts/updates/deletes with the following extensions:
> * Inserts and updates can reference values assigned earlier in the statement
> * Updates can reference their own columns:
> {code:java}
> miles_driven = miles_driven + 30{code}
> - or -
> {code:java}
> miles_driven += 30{code}
> These will of course need to generate any required reads behind the scenes.
> There's no precedence of table vs reference names, so if a relevant column
> name and reference name conflict, the query needs to fail to parse.
> h3. If blocks
> {code:sql}
> IF THEN
> ;
> ;
> END IF
> {code}
>
> For v1, we only need to support a single condition in the format above. In
> the future, we'd like to support multiple branches with multiple conditions
> like:
>
> {code:sql}
> IF THEN
> ;
> ;
> ELSE IF THEN
> ;
> ELSE
> ;
> END IF
> {code}
>
> h3. Conditions
> Comparisons of value references to literals or other references. IS NULL / IS
> NOT NULL also needs to be supported. Multiple comparisons need to be
> supported, but v1 only needs to support AND'ing them together.
> {code:java}
> Supported operators: =, !=, >, >=, <, <=, IS NULL, IS NOT NULL
> = 5
> IS NOT NULL
> IF car IS NOT NULL AND car.miles_driven > 30
> IF car.miles_driven = user.miles_driven{code}
> (Note that {{IS[ NOT ]NULL}} can apply to both tuple references and
> individually dereferenced columns.)
> CONTAINS and CONTAINS KEY require indexed collections, and will not be
> supported in v1.
> h3. Implementation notes
> I have a proof of concept I'd created to demo the initially proposed syntax
> here: [https://github.com/bdeggleston/cassandra/tree/accord-cql-poc], It
> could be used as a starting point, a source of ideas for approaches, or not
> used at all. The main thing to keep in mind is that value references prevent
> creating read commands and mutations until later in the transaction process,
> and potentially on another machine, which means we can't create accord
>
[jira] [Commented] (CASSANDRA-16092) Add Index Group Interface for Storage Attached Index
[ https://issues.apache.org/jira/browse/CASSANDRA-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609575#comment-17609575 ] Caleb Rackliffe commented on CASSANDRA-16092: - [~mck] The commit exists in the feature branch for the umbrella ticket, CASSANDRA-16052. We had decided that, due to the API changes it contained (and the fact that no actual implementation would make use of them yet), the overall CEP feature branch would be the best place. On versioning, I've changed this to 4.x to match the umbrella ticket, but really it's entirely dependent on where CASSANDRA-16052 lands. > Add Index Group Interface for Storage Attached Index > > > Key: CASSANDRA-16092 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16092 > Project: Cassandra > Issue Type: New Feature > Components: Feature/SASI >Reporter: Zhao Yang >Assignee: Zhao Yang >Priority: Normal > Fix For: 4.x > > > [Index > group|https://github.com/datastax/cassandra/blob/storage_attached_index/src/java/org/apache/cassandra/index/Index.java#L634] > interface allows: > * indexes on the same table to receive centralized lifecycle events called > secondary index groups. Sharing of data between multiple column indexes on > the same table allows SAI disk usage to realise significant space savings > over other index implementations. > * index-group to analyze user query and provide a query plan that leverages > all available indexes within the group. -- 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-16092) Add Index Group Interface for Storage Attached Index
[ https://issues.apache.org/jira/browse/CASSANDRA-16092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-16092: Fix Version/s: 4.x (was: 5.x) > Add Index Group Interface for Storage Attached Index > > > Key: CASSANDRA-16092 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16092 > Project: Cassandra > Issue Type: New Feature > Components: Feature/SASI >Reporter: Zhao Yang >Assignee: Zhao Yang >Priority: Normal > Fix For: 4.x > > > [Index > group|https://github.com/datastax/cassandra/blob/storage_attached_index/src/java/org/apache/cassandra/index/Index.java#L634] > interface allows: > * indexes on the same table to receive centralized lifecycle events called > secondary index groups. Sharing of data between multiple column indexes on > the same table allows SAI disk usage to realise significant space savings > over other index implementations. > * index-group to analyze user query and provide a query plan that leverages > all available indexes within the group. -- 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-17668) Fix leak of non-standard Java types in our Exceptions as clients using JMX are unable to handle them
[
https://issues.apache.org/jira/browse/CASSANDRA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17668:
Since Version: (was: 3.11.10)
> Fix leak of non-standard Java types in our Exceptions as clients using JMX
> are unable to handle them
>
>
> Key: CASSANDRA-17668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17668
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Observability/JMX
>Reporter: Ekaterina Dimitrova
>Assignee: Leonard Ma
>Priority: Normal
> Fix For: 4.2
>
> Attachments: Screen Shot 2022-09-13 at 11.27.30 PM.png
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> This is a continuation of CASSANDRA-17638 where we fixed leaks introduced
> during development of 4.1 to ensure no regressions.
> This ticket is to fix a few leakages which are there since previous major
> versions, not 4.1 regressions.
> {_}setRepairSessionMaxTreeDepth{_}(exists since 3.0) and
> _setRepairSessionSpaceInMegabytes(since 4.0)_
> in the DatabaseDescriptor.
> checkValidForByteConversion and _validateMaxConcurrentAutoUpgradeTasksConf
> (both since 4.0)_
> are used in both setters and on startup. They shouldn't throw
> ConfigurationException in the setters.
> There might be more but those are at least a few obvious I found in the
> DatabaseDescriptor.
> CC [~dcapwell]
--
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] [Comment Edited] (CASSANDRA-17668) Fix leak of non-standard Java types in our Exceptions as clients using JMX are unable to handle them
[
https://issues.apache.org/jira/browse/CASSANDRA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609551#comment-17609551
]
Ekaterina Dimitrova edited comment on CASSANDRA-17668 at 9/26/22 3:44 PM:
--
Committed to trunk:
To [https://github.com/apache/cassandra.git]
7adfdc85cf..e5c9cf4cbe trunk -> trunk
The only issues seen were known:
test_move_backwards_and_cleanup - CASSANDRA-16061
test_multiple_repair - CASSANDRA-17005
Also, for the record - I didn't run in the multiplexer the unit tests because
they cannot be more deterministic than that. Saved some resources here.
Thank you for your work [~lmtrombone]!
was (Author: e.dimitrova):
Committed to trunk:
To https://github.com/apache/cassandra.git
7adfdc85cf..e5c9cf4cbe trunk -> trunk
The only issues seen were known:
test_move_backwards_and_cleanup - CASSANDRA-16061
test_multiple_repair - CASSANDRA-17005
Also, for the record - I didn't run in the multiplexer the unit tests because
they cannot be more deterministic than that. Saved some resources here.
> Fix leak of non-standard Java types in our Exceptions as clients using JMX
> are unable to handle them
>
>
> Key: CASSANDRA-17668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17668
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Observability/JMX
>Reporter: Ekaterina Dimitrova
>Assignee: Leonard Ma
>Priority: Normal
> Fix For: 4.2
>
> Attachments: Screen Shot 2022-09-13 at 11.27.30 PM.png
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> This is a continuation of CASSANDRA-17638 where we fixed leaks introduced
> during development of 4.1 to ensure no regressions.
> This ticket is to fix a few leakages which are there since previous major
> versions, not 4.1 regressions.
> {_}setRepairSessionMaxTreeDepth{_}(exists since 3.0) and
> _setRepairSessionSpaceInMegabytes(since 4.0)_
> in the DatabaseDescriptor.
> checkValidForByteConversion and _validateMaxConcurrentAutoUpgradeTasksConf
> (both since 4.0)_
> are used in both setters and on startup. They shouldn't throw
> ConfigurationException in the setters.
> There might be more but those are at least a few obvious I found in the
> DatabaseDescriptor.
> CC [~dcapwell]
--
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-17668) Fix leak of non-standard Java types in our Exceptions as clients using JMX are unable to handle them
[
https://issues.apache.org/jira/browse/CASSANDRA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17668:
Status: Ready to Commit (was: Review In Progress)
> Fix leak of non-standard Java types in our Exceptions as clients using JMX
> are unable to handle them
>
>
> Key: CASSANDRA-17668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17668
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Observability/JMX
>Reporter: Ekaterina Dimitrova
>Assignee: Leonard Ma
>Priority: Normal
> Fix For: 4.x
>
> Attachments: Screen Shot 2022-09-13 at 11.27.30 PM.png
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> This is a continuation of CASSANDRA-17638 where we fixed leaks introduced
> during development of 4.1 to ensure no regressions.
> This ticket is to fix a few leakages which are there since previous major
> versions, not 4.1 regressions.
> {_}setRepairSessionMaxTreeDepth{_}(exists since 3.0) and
> _setRepairSessionSpaceInMegabytes(since 4.0)_
> in the DatabaseDescriptor.
> checkValidForByteConversion and _validateMaxConcurrentAutoUpgradeTasksConf
> (both since 4.0)_
> are used in both setters and on startup. They shouldn't throw
> ConfigurationException in the setters.
> There might be more but those are at least a few obvious I found in the
> DatabaseDescriptor.
> CC [~dcapwell]
--
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-17668) Fix leak of non-standard Java types in our Exceptions as clients using JMX are unable to handle them
[
https://issues.apache.org/jira/browse/CASSANDRA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17668:
Fix Version/s: 4.2
(was: 4.x)
Since Version: 3.11.10
Source Control Link:
https://github.com/apache/cassandra/commit/e5c9cf4cbe6634ba9e148b6e27b6bad98648e597
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Fix leak of non-standard Java types in our Exceptions as clients using JMX
> are unable to handle them
>
>
> Key: CASSANDRA-17668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17668
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Observability/JMX
>Reporter: Ekaterina Dimitrova
>Assignee: Leonard Ma
>Priority: Normal
> Fix For: 4.2
>
> Attachments: Screen Shot 2022-09-13 at 11.27.30 PM.png
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> This is a continuation of CASSANDRA-17638 where we fixed leaks introduced
> during development of 4.1 to ensure no regressions.
> This ticket is to fix a few leakages which are there since previous major
> versions, not 4.1 regressions.
> {_}setRepairSessionMaxTreeDepth{_}(exists since 3.0) and
> _setRepairSessionSpaceInMegabytes(since 4.0)_
> in the DatabaseDescriptor.
> checkValidForByteConversion and _validateMaxConcurrentAutoUpgradeTasksConf
> (both since 4.0)_
> are used in both setters and on startup. They shouldn't throw
> ConfigurationException in the setters.
> There might be more but those are at least a few obvious I found in the
> DatabaseDescriptor.
> CC [~dcapwell]
--
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-17668) Fix leak of non-standard Java types in our Exceptions as clients using JMX are unable to handle them
[
https://issues.apache.org/jira/browse/CASSANDRA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609551#comment-17609551
]
Ekaterina Dimitrova commented on CASSANDRA-17668:
-
Committed to trunk:
To https://github.com/apache/cassandra.git
7adfdc85cf..e5c9cf4cbe trunk -> trunk
The only issues seen were known:
test_move_backwards_and_cleanup - CASSANDRA-16061
test_multiple_repair - CASSANDRA-17005
Also, for the record - I didn't run in the multiplexer the unit tests because
they cannot be more deterministic than that. Saved some resources here.
> Fix leak of non-standard Java types in our Exceptions as clients using JMX
> are unable to handle them
>
>
> Key: CASSANDRA-17668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17668
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Observability/JMX
>Reporter: Ekaterina Dimitrova
>Assignee: Leonard Ma
>Priority: Normal
> Fix For: 4.x
>
> Attachments: Screen Shot 2022-09-13 at 11.27.30 PM.png
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> This is a continuation of CASSANDRA-17638 where we fixed leaks introduced
> during development of 4.1 to ensure no regressions.
> This ticket is to fix a few leakages which are there since previous major
> versions, not 4.1 regressions.
> {_}setRepairSessionMaxTreeDepth{_}(exists since 3.0) and
> _setRepairSessionSpaceInMegabytes(since 4.0)_
> in the DatabaseDescriptor.
> checkValidForByteConversion and _validateMaxConcurrentAutoUpgradeTasksConf
> (both since 4.0)_
> are used in both setters and on startup. They shouldn't throw
> ConfigurationException in the setters.
> There might be more but those are at least a few obvious I found in the
> DatabaseDescriptor.
> CC [~dcapwell]
--
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-17005) Fix test dtest.repair_tests.incremental_repair_test.TestIncRepair.test_multiple_repair
[
https://issues.apache.org/jira/browse/CASSANDRA-17005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609550#comment-17609550
]
Ekaterina Dimitrova commented on CASSANDRA-17005:
-
And one more time:
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1948/workflows/24fc5596-0685-48e6-86ce-45a7b05ca944/jobs/15444
> Fix test
> dtest.repair_tests.incremental_repair_test.TestIncRepair.test_multiple_repair
> --
>
> Key: CASSANDRA-17005
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17005
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Ekaterina Dimitrova
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.0.x, 4.1
>
>
> [dtest.repair_tests.incremental_repair_test.TestIncRepair.test_multiple_repair|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1143/testReport/junit/dtest.repair_tests.incremental_repair_test/TestIncRepair/test_multiple_repair/]
> is flaky:
> h3.
> {code:java}
> Error Message
> cassandra.OperationTimedOut: errors={'127.0.0.2:9042': 'Client request
> timeout. See Session.execute[_async](timeout)'}, last_host=127.0.0.2:9042
> Stacktrace
> self = 0x7ff52f4f4fd0> def test_multiple_repair(self): """ * Launch a three node
> cluster * Create a keyspace with RF 3 and a table * Insert 49 rows * Stop
> node3 * Insert 50 more rows * Restart node3 * Issue an incremental repair on
> node3 * Stop node2 * Insert a final50 rows * Restart node2 * Issue an
> incremental repair on node2 * Replace node3 with a new node * Verify data
> integrity # TODO: Several more verifications of data need to be interspersed
> throughout the test. The final assertion is insufficient. @jira_ticket
> CASSANDRA-10644 """ cluster = self.cluster cluster.populate(3).start() node1,
> node2, node3 = cluster.nodelist() session =
> self.patient_cql_connection(node1) create_ks(session, 'ks', 3) if
> cluster.version() < '4.0': create_cf(session, 'cf', read_repair=0.0,
> columns={'c1': 'text', 'c2': 'text'}) else: create_cf(session, 'cf',
> columns={'c1': 'text', 'c2': 'text'}) logger.debug("insert data")
> insert_c1c2(session, keys=list(range(1, 50)),
> consistency=ConsistencyLevel.ALL) node1.flush() logger.debug("bringing down
> node 3") node3.flush() node3.stop(gently=False) logger.debug("inserting
> additional data into node 1 and 2") insert_c1c2(session, keys=list(range(50,
> 100)), consistency=ConsistencyLevel.TWO) node1.flush() node2.flush()
> logger.debug("restarting and repairing node 3")
> node3.start(wait_for_binary_proto=True) if cluster.version() >= "2.2":
> node3.repair() else: node3.nodetool("repair -par -inc") # wait stream
> handlers to be closed on windows # after session is finished (See
> CASSANDRA-10644) if is_win: time.sleep(2) logger.debug("stopping node 2")
> node2.stop(gently=False) logger.debug("inserting data in nodes 1 and 3")
> insert_c1c2(session, keys=list(range(100, 150)),
> consistency=ConsistencyLevel.TWO) node1.flush() node3.flush()
> logger.debug("start and repair node 2")
> node2.start(wait_for_binary_proto=True) if cluster.version() >= "2.2":
> node2.repair() else: node2.nodetool("repair -par -inc") logger.debug("replace
> node and check data integrity") node3.stop(gently=False) node5 =
> Node('node5', cluster, True, ('127.0.0.5', 9160), ('127.0.0.5', 7000),
> '7500', '0', None, ('127.0.0.5', 9042)) cluster.add(node5, False,
> data_center="dc1") node5.start(replace_address='127.0.0.3') >
> assert_one(session, "SELECT COUNT(*) FROM ks.cf LIMIT 200", [149])
> repair_tests/incremental_repair_test.py:300: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ tools/assertions.py:130: in
> assert_one res = session.execute(simple_query)
> ../venv/src/cassandra-driver/cassandra/cluster.py:2618: in execute return
> self.execute_async(query, parameters, trace, custom_payload, timeout,
> execution_profile, paging_state, host, execute_as).result() _ _ _ _ _ _ _ _ _
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self =
> See Session.execute[_async](timeout)'}, last_host=127.0.0.2:9042
> coordinator_host=None> def result(self): """ Return the final result or raise
> an Exception if errors were encountered. If the final result or error has not
> been set yet, this method will block until it is set, or the timeout set for
> the request expires. Timeout is specified in the Session request execution
> functions. If the timeout is exceeded, an :exc:`cassandra.OperationTimedOut`
> will be raised. This is a client-side timeout. For more information about
> server-side coordinator timeouts, see :class:`.policies.RetryPolicy`. Example
> usage:: >>> future =
[jira] [Commented] (CASSANDRA-16061) transient_replication_ring_test.py::TestTransientReplicationRing::test_move_forwards_and_cleanup
[ https://issues.apache.org/jira/browse/CASSANDRA-16061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609548#comment-17609548 ] Ekaterina Dimitrova commented on CASSANDRA-16061: - Seen on trunk: https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1948/workflows/b7f46851-91bd-485d-aff3-c7d2150cb401/jobs/15425/tests#failed-test-0 > transient_replication_ring_test.py::TestTransientReplicationRing::test_move_forwards_and_cleanup > > > Key: CASSANDRA-16061 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16061 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > Failing here, also locally: > [https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/312/workflows/da4ce69c-e778-467e-b9f3-27ab166a8321/jobs/1945] -- 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
[cassandra] branch trunk updated: Handle leak of non-standard Java types as clients using JMX cannot handle them
This is an automated email from the ASF dual-hosted git repository.
edimitrova pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new e5c9cf4cbe Handle leak of non-standard Java types as clients using JMX
cannot handle them
e5c9cf4cbe is described below
commit e5c9cf4cbe6634ba9e148b6e27b6bad98648e597
Author: Leonard Ma
AuthorDate: Fri Sep 2 17:54:04 2022 -0700
Handle leak of non-standard Java types as clients using JMX cannot handle
them
-deprecate and replace JMX setters that throw non-standard exceptions
-deprecate and replace respective JMX getters as well to make JMX usage
consistent
patch by Leonard Ma; reviewed by Ekaterina Dimitrova and David Capwell for
CASSANDRA-17668
---
CHANGES.txt| 2 +
NEWS.txt | 12 ++-
.../cassandra/service/ActiveRepairService.java | 27 ++
.../service/ActiveRepairServiceMBean.java | 11 +++
.../apache/cassandra/service/StorageService.java | 105
.../cassandra/service/StorageServiceMBean.java | 56 ++-
.../cassandra/config/DatabaseDescriptorTest.java | 2 +-
.../cassandra/service/ActiveRepairServiceTest.java | 34 +++
.../cassandra/service/StorageServiceTest.java | 108 +
9 files changed, 351 insertions(+), 6 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index f49d5f2e1e..60e5f976e5 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,6 @@
4.2
+ * Fix leak of non-standard Java types in JMX MBeans
`org.apache.cassandra.db:type=StorageService`
+ and `org.apache.cassandra.db:type=RepairService` as clients using JMX
cannot handle them. More details in NEWS.txt (CASSANDRA-17668)
* Deprecate Throwables.propagate usage (CASSANDRA-14218)
* Allow disabling hotness persistence for high sstable counts
(CASSANDRA-17868)
* Prevent NullPointerException when changing neverPurgeTombstones from true
to false (CASSANDRA-17897)
diff --git a/NEWS.txt b/NEWS.txt
index b64a06c35d..d9c2f20942 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -100,7 +100,17 @@ Upgrading
Deprecation
---
-
+- In the JMX MBean `org.apache.cassandra.db:type=RepairService`
(CASSANDRA-17668):
+- deprecate the getter/setter methods
`getRepairSessionSpaceInMebibytes` and `setRepairSessionSpaceInMebibytes`
+ in favor of `getRepairSessionSpaceInMiB` and
`setRepairSessionSpaceInMiB` respectively
+- In the JMX MBean `org.apache.cassandra.db:type=StorageService`
(CASSANDRA-17668):
+- deprecate the getter/setter methods `getRepairSessionMaxTreeDepth`
and `setRepairSessionMaxTreeDepth`
+ in favor of `getRepairSessionMaximumTreeDepth` and
`setRepairSessionMaximumTreeDepth`
+- deprecate the setter method `setColumnIndexSize` in favor of
`setColumnIndexSizeInKiB`
+- deprecate the getter/setter methods `getColumnIndexCacheSize` and
`setColumnIndexCacheSize` in favor of
+ `getColumnIndexCacheSizeInKiB` and `setColumnIndexCacheSizeInKiB`
respectively
+- deprecate the getter/setter methods `getBatchSizeWarnThreshold` and
`setBatchSizeWarnThreshold` in favor of
+ `getBatchSizeWarnThresholdInKiB` and
`setBatchSizeWarnThresholdInKiB` respectively
4.1
===
diff --git a/src/java/org/apache/cassandra/service/ActiveRepairService.java
b/src/java/org/apache/cassandra/service/ActiveRepairService.java
index 68247eaf58..220bf92421 100644
--- a/src/java/org/apache/cassandra/service/ActiveRepairService.java
+++ b/src/java/org/apache/cassandra/service/ActiveRepairService.java
@@ -46,6 +46,7 @@ import org.apache.cassandra.concurrent.ExecutorPlus;
import org.apache.cassandra.config.Config;
import org.apache.cassandra.config.DurationSpec;
import org.apache.cassandra.db.compaction.CompactionManager;
+import org.apache.cassandra.exceptions.ConfigurationException;
import org.apache.cassandra.locator.AbstractReplicationStrategy;
import org.apache.cassandra.locator.EndpointsByRange;
import org.apache.cassandra.locator.EndpointsForRange;
@@ -297,18 +298,44 @@ public class ActiveRepairService implements
IEndpointStateChangeSubscriber, IFai
return DatabaseDescriptor.getRepairSessionSpaceInMiB();
}
+@Deprecated
@Override
public void setRepairSessionSpaceInMebibytes(int sizeInMebibytes)
{
DatabaseDescriptor.setRepairSessionSpaceInMiB(sizeInMebibytes);
}
+@Deprecated
@Override
public int getRepairSessionSpaceInMebibytes()
{
return DatabaseDescriptor.getRepairSessionSpaceInMiB();
}
+@Override
+public void setRepairSessionSpaceInMiB(int sizeInMebibytes)
+{
+try
+{
+DatabaseDescriptor.setRepairSessionSpaceInMiB(sizeInMebibytes);
+}
+catch (ConfigurationException e)
+{
+
[jira] [Updated] (CASSANDRA-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
[
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-17461:
Status: Ready to Commit (was: Review In Progress)
> Test Failure:
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Blake Eggleston
>Priority: Normal
> Fix For: 4.1-beta, 4.x
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}}
> for trunk:
> *
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> *
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> *
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> *
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed
> out: received 1 of 2 required responses after 0 contention retries
> at
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
> at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
> at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan
> these urls:
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
> file:/home/cassandra/cassandra/build/classes/fqltool/,
> file:/home/cassandra/cassandra/build/test/classes/,
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node1_isolatedExecutor:10] node1
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging
> service to quiesce
> INFO [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node2_isolatedExecutor:8] node2 2022-03-19
> 16:21:55,222 MessagingService.java:519 - Waiting for messaging service to
> quiesce
> {code}
> Failures can also be repeatedly hit with CircleCI test multiplexer:
>
[jira] [Updated] (CASSANDRA-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
[
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-17461:
Since Version: 4.1-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/286d2ee053ac2e6fe50749fa2833533254697662
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Test Failure:
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Blake Eggleston
>Priority: Normal
> Fix For: 4.1-beta, 4.x
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}}
> for trunk:
> *
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> *
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> *
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> *
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed
> out: received 1 of 2 required responses after 0 contention retries
> at
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
> at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
> at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan
> these urls:
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
> file:/home/cassandra/cassandra/build/classes/fqltool/,
> file:/home/cassandra/cassandra/build/test/classes/,
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node1_isolatedExecutor:10] node1
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging
> service to quiesce
> INFO [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node2_isolatedExecutor:8] node2 2022-03-19
> 16:21:55,222 MessagingService.java:519 - Waiting for
[jira] [Updated] (CASSANDRA-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
[
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-17461:
Reviewers: Benedict Elliott Smith, Blake Eggleston (was: Benedict Elliott
Smith)
Status: Review In Progress (was: Patch Available)
> Test Failure:
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Blake Eggleston
>Priority: Normal
> Fix For: 4.1-beta, 4.x
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}}
> for trunk:
> *
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> *
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> *
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> *
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed
> out: received 1 of 2 required responses after 0 contention retries
> at
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
> at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
> at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan
> these urls:
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
> file:/home/cassandra/cassandra/build/classes/fqltool/,
> file:/home/cassandra/cassandra/build/test/classes/,
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node1_isolatedExecutor:10] node1
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging
> service to quiesce
> INFO [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node2_isolatedExecutor:8] node2 2022-03-19
> 16:21:55,222 MessagingService.java:519 - Waiting for messaging service to
> quiesce
> {code}
> Failures can also be repeatedly hit with CircleCI test
[jira] [Updated] (CASSANDRA-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
[
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-17461:
Test and Documentation Plan: circle
Status: Patch Available (was: In Progress)
> Test Failure:
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Blake Eggleston
>Priority: Normal
> Fix For: 4.1-beta, 4.x
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}}
> for trunk:
> *
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> *
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> *
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> *
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed
> out: received 1 of 2 required responses after 0 contention retries
> at
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
> at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
> at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan
> these urls:
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
> file:/home/cassandra/cassandra/build/classes/fqltool/,
> file:/home/cassandra/cassandra/build/test/classes/,
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node1_isolatedExecutor:10] node1
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging
> service to quiesce
> INFO [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node2_isolatedExecutor:8] node2 2022-03-19
> 16:21:55,222 MessagingService.java:519 - Waiting for messaging service to
> quiesce
> {code}
> Failures can also be repeatedly hit with CircleCI test multiplexer:
>
[jira] [Updated] (CASSANDRA-17668) Fix leak of non-standard Java types in our Exceptions as clients using JMX are unable to handle them
[
https://issues.apache.org/jira/browse/CASSANDRA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17668:
Fix Version/s: (was: 3.0.x)
(was: 3.11.x)
(was: 4.0.x)
(was: 4.1.x)
> Fix leak of non-standard Java types in our Exceptions as clients using JMX
> are unable to handle them
>
>
> Key: CASSANDRA-17668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17668
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Observability/JMX
>Reporter: Ekaterina Dimitrova
>Assignee: Leonard Ma
>Priority: Normal
> Fix For: 4.x
>
> Attachments: Screen Shot 2022-09-13 at 11.27.30 PM.png
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> This is a continuation of CASSANDRA-17638 where we fixed leaks introduced
> during development of 4.1 to ensure no regressions.
> This ticket is to fix a few leakages which are there since previous major
> versions, not 4.1 regressions.
> {_}setRepairSessionMaxTreeDepth{_}(exists since 3.0) and
> _setRepairSessionSpaceInMegabytes(since 4.0)_
> in the DatabaseDescriptor.
> checkValidForByteConversion and _validateMaxConcurrentAutoUpgradeTasksConf
> (both since 4.0)_
> are used in both setters and on startup. They shouldn't throw
> ConfigurationException in the setters.
> There might be more but those are at least a few obvious I found in the
> DatabaseDescriptor.
> CC [~dcapwell]
--
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-17920) Cassandra 4.0.4 on RHEL7 cannot be upgraded to 4.0.5
[ https://issues.apache.org/jira/browse/CASSANDRA-17920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17920: - Resolution: Invalid Status: Resolved (was: Triage Needed) The repo has changed locations, please see https://cassandra.apache.org/_/download.html > Cassandra 4.0.4 on RHEL7 cannot be upgraded to 4.0.5 > > > Key: CASSANDRA-17920 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17920 > Project: Cassandra > Issue Type: Bug >Reporter: Daniel Silwon >Priority: Normal > > Dears, > We are using the repo from url: > https://www.apache.org/dist/cassandra/redhat/40x > > During update we got an error: > yum update > Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, > search-disabled-repos, subscription-manager > Apache_Cassandra_4_0_Cassandra_40x | 2.0 kB 00:00:00 > rhel-7-server-optional-rpms | 3.2 kB 00:00:00 > rhel-7-server-rpms | 3.5 kB 00:00:00 > Resolving Dependencies > --> Running transaction check > ---> Package cassandra.noarch 0:4.0.4-1 will be updated > ---> Package cassandra.noarch 0:4.0.5-1 will be an update > *Error: Invalid version flag: or* > Uploading Enabled Repositories Report > Loaded plugins: langpacks, product-id, subscription-manager > Do you have any idea how to solve it? > Best Regards, > Dan -- 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-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
[
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609514#comment-17609514
]
Brandon Williams commented on CASSANDRA-17461:
--
This is the only ticket blocking the release of 4.1, is there anything left to
be done here?
> Test Failure:
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Blake Eggleston
>Priority: Normal
> Fix For: 4.1-beta, 4.x
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}}
> for trunk:
> *
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> *
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> *
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> *
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed
> out: received 1 of 2 required responses after 0 contention retries
> at
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
> at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
> at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan
> these urls:
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
> file:/home/cassandra/cassandra/build/classes/fqltool/,
> file:/home/cassandra/cassandra/build/test/classes/,
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node1_isolatedExecutor:10] node1
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging
> service to quiesce
> INFO [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node2_isolatedExecutor:8] node2 2022-03-19
> 16:21:55,222 MessagingService.java:519 - Waiting for messaging service to
> quiesce
> {code}
> Failures can also be repeatedly hit with CircleCI test
[jira] [Updated] (CASSANDRA-17810) Revise timeout handling on queries triggering timeout introduced by CASSANDRA-7392
[
https://issues.apache.org/jira/browse/CASSANDRA-17810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-17810:
--
Reviewers: Aleksey Yeschenko, Aleksey Yeschenko (was: Aleksey Yeschenko)
Aleksey Yeschenko, Aleksey Yeschenko (was: Aleksey Yeschenko)
Status: Review In Progress (was: Patch Available)
> Revise timeout handling on queries triggering timeout introduced by
> CASSANDRA-7392
> --
>
> Key: CASSANDRA-17810
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17810
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
>
> In situations where a replica times out with the code introduced in
> CASSANDRA-7392, they drop the timed-out query on the floor without notifying
> the coordinator; this doesn't become apparent coordinator-side until we go to
> serialize the response. While the results of this (i.e. missed data) should
> mostly be fixed by short read protection on repeat requests, the coordinator
> can in some cases throw an exception like {{IllegalStateException:
> UnfilteredRowIterator for keyspace.table has an open RT bound as its last
> item}} which is decidedly unfriendly.
> We should introduce a specific exception to allow replicas to notify a
> coordinator something has timed out and been dropped on the floor so the
> coordinator can appropriately handle that scenario and abort the query at
> that time.
--
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-17810) Revise timeout handling on queries triggering timeout introduced by CASSANDRA-7392
[
https://issues.apache.org/jira/browse/CASSANDRA-17810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-17810:
--
Status: Ready to Commit (was: Review In Progress)
+1
> Revise timeout handling on queries triggering timeout introduced by
> CASSANDRA-7392
> --
>
> Key: CASSANDRA-17810
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17810
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
>
> In situations where a replica times out with the code introduced in
> CASSANDRA-7392, they drop the timed-out query on the floor without notifying
> the coordinator; this doesn't become apparent coordinator-side until we go to
> serialize the response. While the results of this (i.e. missed data) should
> mostly be fixed by short read protection on repeat requests, the coordinator
> can in some cases throw an exception like {{IllegalStateException:
> UnfilteredRowIterator for keyspace.table has an open RT bound as its last
> item}} which is decidedly unfriendly.
> We should introduce a specific exception to allow replicas to notify a
> coordinator something has timed out and been dropped on the floor so the
> coordinator can appropriately handle that scenario and abort the query at
> that time.
--
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-17919) Capital P gets confused in the parser for a Duration in places where IDENT are needed
[
https://issues.apache.org/jira/browse/CASSANDRA-17919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-17919:
---
Complexity: Low Hanging Fruit (was: Normal)
> Capital P gets confused in the parser for a Duration in places where IDENT
> are needed
> -
>
> Key: CASSANDRA-17919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17919
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: David Capwell
>Priority: Normal
>
> This was found while adding Accord Transaction syntax into CQL and fuzz
> testing to validate all possible cases… in doing this the following was found
> {code}
> String query = "BEGIN TRANSACTION\n" +
>" LET P = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" LET row2 = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" SELECT v FROM " + keyspace + ".tbl WHERE k=?
> AND c=?;\n" +
>" IF P IS NULL AND row2.v = ? THEN\n" +
>"INSERT INTO " + keyspace + ".tbl (k, c, v)
> VALUES (?, ?, ?);\n" +
>" END IF\n" +
>"COMMIT TRANSACTION";
> {code}
> Fails with
> {code}
> SyntaxException: line 2:6 mismatched input 'P' expecting IDENT (BEGIN
> TRANSACTION LET [P]...)
> {code}
> The new LET syntax found this, but was able to reproduce in other cases
> {code}
> cqlsh:ks> CREATE TABLE P (k INT PRIMARY KEY);
> SyntaxException: line 1:13 no viable alternative at input 'P' (CREATE TABLE
> [P]...)
> cqlsh:ks>
> cqlsh:ks> CREATE TABLE p (k INT PRIMARY KEY);
> cqlsh:ks>
> {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] [Comment Edited] (CASSANDRA-17919) Capital P gets confused in the parser for a Duration in places where IDENT are needed
[
https://issues.apache.org/jira/browse/CASSANDRA-17919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609477#comment-17609477
]
Benjamin Lerer edited comment on CASSANDRA-17919 at 9/26/22 12:51 PM:
--
According to [Wikipedia|https://en.wikipedia.org/wiki/ISO_8601#Durations]:
{quote}Date and time elements including their designator may be omitted if
their value is zero, and lower-order elements may also be omitted for reduced
precision. For example, "P23DT23H" and "P4Y" are both acceptable duration
representations. However, at least one element must be present, thus "P" is not
a valid representation for a duration of 0 seconds. "PT0S" or "P0D", however,
are both valid and represent the same duration.
{quote}
Effectively the lexer rule and the parsing logic from {{Duration.from}} should
be rewritten.
was (Author: blerer):
According to [Wikipedia|https://en.wikipedia.org/wiki/ISO_8601#Durations]:
{quote}Date and time elements including their designator may be omitted if
their value is zero, and lower-order elements may also be omitted for reduced
precision. For example, "P23DT23H" and "P4Y" are both acceptable duration
representations. However, at least one element must be present, thus "P" is not
a valid representation for a duration of 0 seconds. "PT0S" or "P0D", however,
are both valid and represent the same duration.
{quote}
Effectively the lexer rule should be rewritten.
> Capital P gets confused in the parser for a Duration in places where IDENT
> are needed
> -
>
> Key: CASSANDRA-17919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17919
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: David Capwell
>Priority: Normal
>
> This was found while adding Accord Transaction syntax into CQL and fuzz
> testing to validate all possible cases… in doing this the following was found
> {code}
> String query = "BEGIN TRANSACTION\n" +
>" LET P = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" LET row2 = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" SELECT v FROM " + keyspace + ".tbl WHERE k=?
> AND c=?;\n" +
>" IF P IS NULL AND row2.v = ? THEN\n" +
>"INSERT INTO " + keyspace + ".tbl (k, c, v)
> VALUES (?, ?, ?);\n" +
>" END IF\n" +
>"COMMIT TRANSACTION";
> {code}
> Fails with
> {code}
> SyntaxException: line 2:6 mismatched input 'P' expecting IDENT (BEGIN
> TRANSACTION LET [P]...)
> {code}
> The new LET syntax found this, but was able to reproduce in other cases
> {code}
> cqlsh:ks> CREATE TABLE P (k INT PRIMARY KEY);
> SyntaxException: line 1:13 no viable alternative at input 'P' (CREATE TABLE
> [P]...)
> cqlsh:ks>
> cqlsh:ks> CREATE TABLE p (k INT PRIMARY KEY);
> cqlsh:ks>
> {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] [Comment Edited] (CASSANDRA-17919) Capital P gets confused in the parser for a Duration in places where IDENT are needed
[
https://issues.apache.org/jira/browse/CASSANDRA-17919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609477#comment-17609477
]
Benjamin Lerer edited comment on CASSANDRA-17919 at 9/26/22 12:39 PM:
--
According to [Wikipedia|https://en.wikipedia.org/wiki/ISO_8601#Durations]:
{quote}Date and time elements including their designator may be omitted if
their value is zero, and lower-order elements may also be omitted for reduced
precision. For example, "P23DT23H" and "P4Y" are both acceptable duration
representations. However, at least one element must be present, thus "P" is not
a valid representation for a duration of 0 seconds. "PT0S" or "P0D", however,
are both valid and represent the same duration.
{quote}
Effectively the lexer rule should be rewritten.
was (Author: blerer):
According to [Wikipedia|https://en.wikipedia.org/wiki/ISO_8601#Durations]:
{quote} Date and time elements including their designator may be omitted if
their value is zero, and lower-order elements may also be omitted for reduced
precision. For example, "P23DT23H" and "P4Y" are both acceptable duration
representations. However, at least one element must be present, thus "P" is not
a valid representation for a duration of 0 seconds. "PT0S" or "P0D", however,
are both valid and represent the same duration. \{quote}
Effectively the lexer rule should be rewritten.
> Capital P gets confused in the parser for a Duration in places where IDENT
> are needed
> -
>
> Key: CASSANDRA-17919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17919
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: David Capwell
>Priority: Normal
>
> This was found while adding Accord Transaction syntax into CQL and fuzz
> testing to validate all possible cases… in doing this the following was found
> {code}
> String query = "BEGIN TRANSACTION\n" +
>" LET P = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" LET row2 = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" SELECT v FROM " + keyspace + ".tbl WHERE k=?
> AND c=?;\n" +
>" IF P IS NULL AND row2.v = ? THEN\n" +
>"INSERT INTO " + keyspace + ".tbl (k, c, v)
> VALUES (?, ?, ?);\n" +
>" END IF\n" +
>"COMMIT TRANSACTION";
> {code}
> Fails with
> {code}
> SyntaxException: line 2:6 mismatched input 'P' expecting IDENT (BEGIN
> TRANSACTION LET [P]...)
> {code}
> The new LET syntax found this, but was able to reproduce in other cases
> {code}
> cqlsh:ks> CREATE TABLE P (k INT PRIMARY KEY);
> SyntaxException: line 1:13 no viable alternative at input 'P' (CREATE TABLE
> [P]...)
> cqlsh:ks>
> cqlsh:ks> CREATE TABLE p (k INT PRIMARY KEY);
> cqlsh:ks>
> {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] [Comment Edited] (CASSANDRA-17919) Capital P gets confused in the parser for a Duration in places where IDENT are needed
[
https://issues.apache.org/jira/browse/CASSANDRA-17919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609477#comment-17609477
]
Benjamin Lerer edited comment on CASSANDRA-17919 at 9/26/22 12:38 PM:
--
According to [Wikipedia|https://en.wikipedia.org/wiki/ISO_8601#Durations]:
{quote} Date and time elements including their designator may be omitted if
their value is zero, and lower-order elements may also be omitted for reduced
precision. For example, "P23DT23H" and "P4Y" are both acceptable duration
representations. However, at least one element must be present, thus "P" is not
a valid representation for a duration of 0 seconds. "PT0S" or "P0D", however,
are both valid and represent the same duration. \{quote}
Effectively the lexer rule should be rewritten.
was (Author: blerer):
According to [Wikipedia|https://en.wikipedia.org/wiki/ISO_8601#Durations]:
{quote}Date and time elements including their designator may be omitted if
their value is zero, and lower-order elements may also be omitted for reduced
precision. For example, "P23DT23H" and "P4Y" are both acceptable duration
representations. However, at least one element must be present, thus "P" is not
a valid representation for a duration of 0 seconds. "PT0S" or "P0D", however,
are both valid and represent the same duration. \{quote}
Effectively the lexer rule should be rewritten.
> Capital P gets confused in the parser for a Duration in places where IDENT
> are needed
> -
>
> Key: CASSANDRA-17919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17919
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: David Capwell
>Priority: Normal
>
> This was found while adding Accord Transaction syntax into CQL and fuzz
> testing to validate all possible cases… in doing this the following was found
> {code}
> String query = "BEGIN TRANSACTION\n" +
>" LET P = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" LET row2 = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" SELECT v FROM " + keyspace + ".tbl WHERE k=?
> AND c=?;\n" +
>" IF P IS NULL AND row2.v = ? THEN\n" +
>"INSERT INTO " + keyspace + ".tbl (k, c, v)
> VALUES (?, ?, ?);\n" +
>" END IF\n" +
>"COMMIT TRANSACTION";
> {code}
> Fails with
> {code}
> SyntaxException: line 2:6 mismatched input 'P' expecting IDENT (BEGIN
> TRANSACTION LET [P]...)
> {code}
> The new LET syntax found this, but was able to reproduce in other cases
> {code}
> cqlsh:ks> CREATE TABLE P (k INT PRIMARY KEY);
> SyntaxException: line 1:13 no viable alternative at input 'P' (CREATE TABLE
> [P]...)
> cqlsh:ks>
> cqlsh:ks> CREATE TABLE p (k INT PRIMARY KEY);
> cqlsh:ks>
> {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-17919) Capital P gets confused in the parser for a Duration in places where IDENT are needed
[
https://issues.apache.org/jira/browse/CASSANDRA-17919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609477#comment-17609477
]
Benjamin Lerer commented on CASSANDRA-17919:
According to [Wikipedia|https://en.wikipedia.org/wiki/ISO_8601#Durations]:
{quote}Date and time elements including their designator may be omitted if
their value is zero, and lower-order elements may also be omitted for reduced
precision. For example, "P23DT23H" and "P4Y" are both acceptable duration
representations. However, at least one element must be present, thus "P" is not
a valid representation for a duration of 0 seconds. "PT0S" or "P0D", however,
are both valid and represent the same duration. \{quote}
Effectively the lexer rule should be rewritten.
> Capital P gets confused in the parser for a Duration in places where IDENT
> are needed
> -
>
> Key: CASSANDRA-17919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17919
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: David Capwell
>Priority: Normal
>
> This was found while adding Accord Transaction syntax into CQL and fuzz
> testing to validate all possible cases… in doing this the following was found
> {code}
> String query = "BEGIN TRANSACTION\n" +
>" LET P = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" LET row2 = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" SELECT v FROM " + keyspace + ".tbl WHERE k=?
> AND c=?;\n" +
>" IF P IS NULL AND row2.v = ? THEN\n" +
>"INSERT INTO " + keyspace + ".tbl (k, c, v)
> VALUES (?, ?, ?);\n" +
>" END IF\n" +
>"COMMIT TRANSACTION";
> {code}
> Fails with
> {code}
> SyntaxException: line 2:6 mismatched input 'P' expecting IDENT (BEGIN
> TRANSACTION LET [P]...)
> {code}
> The new LET syntax found this, but was able to reproduce in other cases
> {code}
> cqlsh:ks> CREATE TABLE P (k INT PRIMARY KEY);
> SyntaxException: line 1:13 no viable alternative at input 'P' (CREATE TABLE
> [P]...)
> cqlsh:ks>
> cqlsh:ks> CREATE TABLE p (k INT PRIMARY KEY);
> cqlsh:ks>
> {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-17920) Cassandra 4.0.4 on RHEL7 cannot be upgraded to 4.0.5
[ https://issues.apache.org/jira/browse/CASSANDRA-17920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Silwon updated CASSANDRA-17920: -- Description: Dears, We are using the repo from url: https://www.apache.org/dist/cassandra/redhat/40x During update we got an error: yum update Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, search-disabled-repos, subscription-manager Apache_Cassandra_4_0_Cassandra_40x | 2.0 kB 00:00:00 rhel-7-server-optional-rpms | 3.2 kB 00:00:00 rhel-7-server-rpms | 3.5 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package cassandra.noarch 0:4.0.4-1 will be updated ---> Package cassandra.noarch 0:4.0.5-1 will be an update *Error: Invalid version flag: or* Uploading Enabled Repositories Report Loaded plugins: langpacks, product-id, subscription-manager Do you have any idea how to solve it? Best Regards, Dan was: Dears, We are using the repo from url: https://www.apache.org/dist/cassandra/redhat/40x During update we got an error: yum update Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, search-disabled-repos, subscription-manager Apache_Cassandra_4_0_Cassandra_40x | 2.0 kB 00:00:00 rhel-7-server-optional-rpms | 3.2 kB 00:00:00 rhel-7-server-rpms | 3.5 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package cassandra.noarch 0:4.0.4-1 will be updated ---> Package cassandra.noarch 0:4.0.5-1 will be an update *Error: Invalid version flag: or* Uploading Enabled Repositories Report Loaded plugins: langpacks, product-id, subscription-manager Do you have any idea how to solve it? Best Regards, Dan > Cassandra 4.0.4 on RHEL7 cannot be upgraded to 4.0.5 > > > Key: CASSANDRA-17920 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17920 > Project: Cassandra > Issue Type: Bug >Reporter: Daniel Silwon >Priority: Normal > > Dears, > We are using the repo from url: > https://www.apache.org/dist/cassandra/redhat/40x > > During update we got an error: > yum update > Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, > search-disabled-repos, subscription-manager > Apache_Cassandra_4_0_Cassandra_40x | 2.0 kB 00:00:00 > rhel-7-server-optional-rpms | 3.2 kB 00:00:00 > rhel-7-server-rpms | 3.5 kB 00:00:00 > Resolving Dependencies > --> Running transaction check > ---> Package cassandra.noarch 0:4.0.4-1 will be updated > ---> Package cassandra.noarch 0:4.0.5-1 will be an update > *Error: Invalid version flag: or* > Uploading Enabled Repositories Report > Loaded plugins: langpacks, product-id, subscription-manager > Do you have any idea how to solve it? > Best Regards, > Dan -- 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-17920) Cassandra 4.0.4 on RHEL7 cannot be upgraded to 4.0.5
[ https://issues.apache.org/jira/browse/CASSANDRA-17920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Silwon updated CASSANDRA-17920: -- Description: Dears, We are using the repo from url: https://www.apache.org/dist/cassandra/redhat/40x During update we got an error: yum update Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, search-disabled-repos, subscription-manager Apache_Cassandra_4_0_Cassandra_40x | 2.0 kB 00:00:00 rhel-7-server-optional-rpms | 3.2 kB 00:00:00 rhel-7-server-rpms | 3.5 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package cassandra.noarch 0:4.0.4-1 will be updated ---> Package cassandra.noarch 0:4.0.5-1 will be an update *Error: Invalid version flag: or* Uploading Enabled Repositories Report Loaded plugins: langpacks, product-id, subscription-manager Do you have any idea how to solve it? Best Regards, Dan was: Dears, We are using the repo from url: https://www.apache.org/dist/cassandra/redhat/40x During update we got an error: yum update Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, search-disabled-repos, subscription-manager ITCARD_Apache_Cassandra_4_0_Cassandra_40x | 2.0 kB 00:00:00 rhel-7-server-optional-rpms | 3.2 kB 00:00:00 rhel-7-server-rpms | 3.5 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package cassandra.noarch 0:4.0.4-1 will be updated ---> Package cassandra.noarch 0:4.0.5-1 will be an update *Error: Invalid version flag: or* Uploading Enabled Repositories Report Loaded plugins: langpacks, product-id, subscription-manager Do you have any idea how to solve it? Best Regards, Dan > Cassandra 4.0.4 on RHEL7 cannot be upgraded to 4.0.5 > > > Key: CASSANDRA-17920 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17920 > Project: Cassandra > Issue Type: Bug >Reporter: Daniel Silwon >Priority: Normal > > Dears, > We are using the repo from url: > https://www.apache.org/dist/cassandra/redhat/40x > > During update we got an error: > yum update > Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, > search-disabled-repos, subscription-manager > Apache_Cassandra_4_0_Cassandra_40x > > | 2.0 kB 00:00:00 > rhel-7-server-optional-rpms > > | 3.2 kB 00:00:00 > rhel-7-server-rpms > > | 3.5 kB 00:00:00 > Resolving Dependencies > --> Running transaction check > ---> Package cassandra.noarch 0:4.0.4-1 will be updated > ---> Package cassandra.noarch 0:4.0.5-1 will be an update > *Error: Invalid version flag: or* > Uploading Enabled Repositories Report > Loaded plugins: langpacks, product-id, subscription-manager > Do you have any idea how to solve it? > Best Regards, > Dan -- 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-17920) Cassandra 4.0.4 on RHEL7 cannot be upgraded to 4.0.5
[ https://issues.apache.org/jira/browse/CASSANDRA-17920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Silwon updated CASSANDRA-17920: -- Description: Dears, We are using the repo from url: https://www.apache.org/dist/cassandra/redhat/40x During update we got an error: yum update Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, search-disabled-repos, subscription-manager ITCARD_Apache_Cassandra_4_0_Cassandra_40x | 2.0 kB 00:00:00 rhel-7-server-optional-rpms | 3.2 kB 00:00:00 rhel-7-server-rpms | 3.5 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package cassandra.noarch 0:4.0.4-1 will be updated ---> Package cassandra.noarch 0:4.0.5-1 will be an update *Error: Invalid version flag: or* Uploading Enabled Repositories Report Loaded plugins: langpacks, product-id, subscription-manager Do you have any idea how to solve it? Best Regards, Dan was: Dears, We are using the repo from url: https://www.apache.org/dist/cassandra/redhat/40x During update we got an error: ``` yum update Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, search-disabled-repos, subscription-manager ITCARD_Apache_Cassandra_4_0_Cassandra_40x | 2.0 kB 00:00:00 rhel-7-server-optional-rpms | 3.2 kB 00:00:00 rhel-7-server-rpms | 3.5 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package cassandra.noarch 0:4.0.4-1 will be updated ---> Package cassandra.noarch 0:4.0.5-1 will be an update *Error: Invalid version flag: or* Uploading Enabled Repositories Report Loaded plugins: langpacks, product-id, subscription-manager ``` Do you have any idea how to solve it? Best Regards, Dan > Cassandra 4.0.4 on RHEL7 cannot be upgraded to 4.0.5 > > > Key: CASSANDRA-17920 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17920 > Project: Cassandra > Issue Type: Bug >Reporter: Daniel Silwon >Priority: Normal > > Dears, > We are using the repo from url: > https://www.apache.org/dist/cassandra/redhat/40x > > During update we got an error: > yum update > Loaded plugins: enabled_repos_upload, langpacks, package_upload, product-id, > search-disabled-repos, subscription-manager > ITCARD_Apache_Cassandra_4_0_Cassandra_40x > > | 2.0 kB 00:00:00 > rhel-7-server-optional-rpms > > | 3.2 kB 00:00:00 > rhel-7-server-rpms > > | 3.5 kB 00:00:00 > Resolving Dependencies > --> Running transaction check > ---> Package cassandra.noarch 0:4.0.4-1 will be updated > ---> Package cassandra.noarch 0:4.0.5-1 will be an update > *Error: Invalid version flag: or* > Uploading Enabled Repositories Report > Loaded plugins: langpacks, product-id, subscription-manager > Do you have any idea how to solve it? > Best Regards, > Dan -- 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
