[jira] [Commented] (CASSANDRA-17563) Fix CircleCI Midres config
[ https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531468#comment-17531468 ] Ekaterina Dimitrova commented on CASSANDRA-17563: - Committed to cassandra-4.1 -> https://github.com/apache/cassandra/commit/523d38095f6c7f33c602616db3a7373bbeb0cde9 Merged to trunk. > Fix CircleCI Midres config > -- > > Key: CASSANDRA-17563 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17563 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1.x > > > During CircleCI addition of a new job to the config, the midres file got > messy. Two of the immediate issues (but we need to verify all jobs will use > the right executors and resources): > * the new job needs to use higher parallelism as the original in-jvm job > * j8_dtests_with_vnodes should get from midres 50 large but currently > midres makes it run with 25 and medium which fails around 100 tests -- This message was sent by Atlassian Jira (v8.20.7#820007) - 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 (2480a7e7ee -> 523d38095f)
This is an automated email from the ASF dual-hosted git repository. edimitrova pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 2480a7e7ee Update trunk to version 4.2 add 523d38095f Fix CircleCI MIDRES configuration patch by Ekaterina Dimitrova; reviewed by Andres de la Peña for CASSANDRA-17563 No new revisions were added by this update. Summary of changes: .circleci/config-2_1.yml.mid_res.patch | 45 +- .circleci/config.yml.MIDRES| 12 - 2 files changed, 28 insertions(+), 29 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (99bf8ba465 -> c6207171f2)
This is an automated email from the ASF dual-hosted git repository. edimitrova pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 99bf8ba465 Merge branch 'cassandra-4.1' into trunk add 523d38095f Fix CircleCI MIDRES configuration patch by Ekaterina Dimitrova; reviewed by Andres de la Peña for CASSANDRA-17563 new c6207171f2 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: .circleci/config-2_1.yml.mid_res.patch | 45 +- .circleci/config.yml.MIDRES| 12 - 2 files changed, 28 insertions(+), 29 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. edimitrova pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit c6207171f283d595a8d00f7719a524b2329f413f Merge: 99bf8ba465 523d38095f Author: Ekaterina Dimitrova AuthorDate: Tue May 3 21:03:49 2022 -0400 Merge branch 'cassandra-4.1' into trunk .circleci/config-2_1.yml.mid_res.patch | 45 +- .circleci/config.yml.MIDRES| 12 - 2 files changed, 28 insertions(+), 29 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17563) Fix CircleCI Midres config
[ https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531466#comment-17531466 ] Ekaterina Dimitrova commented on CASSANDRA-17563: - The usual suspects... nothing new and related to this patch or the branching as issue. I will commit it soon. Then wen can move back to discussing the newly suggested scripts. > Fix CircleCI Midres config > -- > > Key: CASSANDRA-17563 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17563 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1.x > > > During CircleCI addition of a new job to the config, the midres file got > messy. Two of the immediate issues (but we need to verify all jobs will use > the right executors and resources): > * the new job needs to use higher parallelism as the original in-jvm job > * j8_dtests_with_vnodes should get from midres 50 large but currently > midres makes it run with 25 and medium which fails around 100 tests -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15737) Add StorageServiceMBean#setDynamicBadnessThreshold to expose dynamic badness threshold
[ https://issues.apache.org/jira/browse/CASSANDRA-15737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531463#comment-17531463 ] Jordan West commented on CASSANDRA-15737: - This had fallen off my radar but I can pick it back up if there is interest [~blerer] [~dcapwell] > Add StorageServiceMBean#setDynamicBadnessThreshold to expose dynamic badness > threshold > -- > > Key: CASSANDRA-15737 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15737 > Project: Cassandra > Issue Type: Improvement > Components: Messaging/Internode >Reporter: Jordan West >Assignee: Jordan West >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > https://issues.apache.org/jira/browse/CASSANDRA-12179 made the > DynamicEndpointSnitch properties dynamic at runtime but didn’t expose a > method to modify badness threshold. This can be useful in operations that > also modify severity manually or if operators want to temporarily disable > dynamic snitch behavior. -- This message was sent by Atlassian Jira (v8.20.7#820007) - 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 (bf2498964 -> eeac0aa28)
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 bf2498964 generate docs for c630db6b new eeac0aa28 generate docs for c630db6b 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 (bf2498964) \ N -- N -- N refs/heads/asf-staging (eeac0aa28) 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] [Commented] (CASSANDRA-17594) Fix flaky python-tests due to connection getting closed
[
https://issues.apache.org/jira/browse/CASSANDRA-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531448#comment-17531448
]
David Capwell commented on CASSANDRA-17594:
---
this patch seems to cause some repair tests to fail, so will look closer into
that (juggling things, so will do tomorrow)
> Fix flaky python-tests due to connection getting closed
> ---
>
> Key: CASSANDRA-17594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We log unknown exceptions at the networking level, which includes case where
> the remote side closes the connection (such as the cases caused by shutting
> down), depending on how quickly the instances shutdown, this could cause
> python-dtest to fail for random tests with a message such as
> {code}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800
> ExceptionHandlers.java:134 - Unknown exception in client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer, WARN [epollEventLoopGroup-5-9]
> 2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in
> client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17595) nodetool enablefullquerylog can NPE when directory has no files
[
https://issues.apache.org/jira/browse/CASSANDRA-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531432#comment-17531432
]
David Capwell commented on CASSANDRA-17595:
---
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|cassandra-4.1|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17595-cassandra-4.1-0099BC8C-594E-4D5C-A02A-7AC27EBCEC4C]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17595-cassandra-4.1-0099BC8C-594E-4D5C-A02A-7AC27EBCEC4C]|[build|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1655/]|
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17595-trunk-0099BC8C-594E-4D5C-A02A-7AC27EBCEC4C]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17595-trunk-0099BC8C-594E-4D5C-A02A-7AC27EBCEC4C]|[build|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1656/]|
> nodetool enablefullquerylog can NPE when directory has no files
> ---
>
> Key: CASSANDRA-17595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17595
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.1.x
>
>
> fqltool_test.py::TestFQLTool::test_unclean_enable found an issue with
> org.apache.cassandra.utils.binlog.BinLog#deleteRecursively, it assumes
> listing files returns empty list rather than null and throws a NPE
> {code}
> E -- StackTrace --
> E java.lang.NullPointerException
> E at
> org.apache.cassandra.utils.binlog.BinLog.deleteRecursively(BinLog.java:490)
> E at
> org.apache.cassandra.utils.binlog.BinLog.cleanDirectory(BinLog.java:477)
> E at
> org.apache.cassandra.utils.binlog.BinLog$Builder.build(BinLog.java:436)
> E at
> org.apache.cassandra.fql.FullQueryLogger.enable(FullQueryLogger.java:106)
> E at
> org.apache.cassandra.service.StorageService.enableFullQueryLogger(StorageService.java:6495)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:72)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:276)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> E at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> E at
> com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> E at
> com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> E at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> E at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> E at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17595) nodetool enablefullquerylog can NPE when directory has no files
[
https://issues.apache.org/jira/browse/CASSANDRA-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17595:
--
Status: Ready to Commit (was: Review In Progress)
> nodetool enablefullquerylog can NPE when directory has no files
> ---
>
> Key: CASSANDRA-17595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17595
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.1.x
>
>
> fqltool_test.py::TestFQLTool::test_unclean_enable found an issue with
> org.apache.cassandra.utils.binlog.BinLog#deleteRecursively, it assumes
> listing files returns empty list rather than null and throws a NPE
> {code}
> E -- StackTrace --
> E java.lang.NullPointerException
> E at
> org.apache.cassandra.utils.binlog.BinLog.deleteRecursively(BinLog.java:490)
> E at
> org.apache.cassandra.utils.binlog.BinLog.cleanDirectory(BinLog.java:477)
> E at
> org.apache.cassandra.utils.binlog.BinLog$Builder.build(BinLog.java:436)
> E at
> org.apache.cassandra.fql.FullQueryLogger.enable(FullQueryLogger.java:106)
> E at
> org.apache.cassandra.service.StorageService.enableFullQueryLogger(StorageService.java:6495)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:72)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:276)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> E at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> E at
> com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> E at
> com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> E at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> E at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> E at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17595) nodetool enablefullquerylog can NPE when directory has no files
[
https://issues.apache.org/jira/browse/CASSANDRA-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17595:
--
Reviewers: Jon Meredith (was: David Capwell, Jon Meredith)
> nodetool enablefullquerylog can NPE when directory has no files
> ---
>
> Key: CASSANDRA-17595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17595
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.1.x
>
>
> fqltool_test.py::TestFQLTool::test_unclean_enable found an issue with
> org.apache.cassandra.utils.binlog.BinLog#deleteRecursively, it assumes
> listing files returns empty list rather than null and throws a NPE
> {code}
> E -- StackTrace --
> E java.lang.NullPointerException
> E at
> org.apache.cassandra.utils.binlog.BinLog.deleteRecursively(BinLog.java:490)
> E at
> org.apache.cassandra.utils.binlog.BinLog.cleanDirectory(BinLog.java:477)
> E at
> org.apache.cassandra.utils.binlog.BinLog$Builder.build(BinLog.java:436)
> E at
> org.apache.cassandra.fql.FullQueryLogger.enable(FullQueryLogger.java:106)
> E at
> org.apache.cassandra.service.StorageService.enableFullQueryLogger(StorageService.java:6495)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:72)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:276)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> E at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> E at
> com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> E at
> com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> E at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> E at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> E at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17595) nodetool enablefullquerylog can NPE when directory has no files
[
https://issues.apache.org/jira/browse/CASSANDRA-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17595:
--
Reviewers: Jon Meredith, David Capwell
Jon Meredith, David Capwell (was: David Capwell, Jon Meredith)
Status: Review In Progress (was: Patch Available)
> nodetool enablefullquerylog can NPE when directory has no files
> ---
>
> Key: CASSANDRA-17595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17595
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.1.x
>
>
> fqltool_test.py::TestFQLTool::test_unclean_enable found an issue with
> org.apache.cassandra.utils.binlog.BinLog#deleteRecursively, it assumes
> listing files returns empty list rather than null and throws a NPE
> {code}
> E -- StackTrace --
> E java.lang.NullPointerException
> E at
> org.apache.cassandra.utils.binlog.BinLog.deleteRecursively(BinLog.java:490)
> E at
> org.apache.cassandra.utils.binlog.BinLog.cleanDirectory(BinLog.java:477)
> E at
> org.apache.cassandra.utils.binlog.BinLog$Builder.build(BinLog.java:436)
> E at
> org.apache.cassandra.fql.FullQueryLogger.enable(FullQueryLogger.java:106)
> E at
> org.apache.cassandra.service.StorageService.enableFullQueryLogger(StorageService.java:6495)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:72)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:276)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> E at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> E at
> com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> E at
> com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> E at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> E at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> E at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17595) nodetool enablefullquerylog can NPE when directory has no files
[
https://issues.apache.org/jira/browse/CASSANDRA-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531427#comment-17531427
]
Jon Meredith commented on CASSANDRA-17595:
--
+1
> nodetool enablefullquerylog can NPE when directory has no files
> ---
>
> Key: CASSANDRA-17595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17595
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.1.x
>
>
> fqltool_test.py::TestFQLTool::test_unclean_enable found an issue with
> org.apache.cassandra.utils.binlog.BinLog#deleteRecursively, it assumes
> listing files returns empty list rather than null and throws a NPE
> {code}
> E -- StackTrace --
> E java.lang.NullPointerException
> E at
> org.apache.cassandra.utils.binlog.BinLog.deleteRecursively(BinLog.java:490)
> E at
> org.apache.cassandra.utils.binlog.BinLog.cleanDirectory(BinLog.java:477)
> E at
> org.apache.cassandra.utils.binlog.BinLog$Builder.build(BinLog.java:436)
> E at
> org.apache.cassandra.fql.FullQueryLogger.enable(FullQueryLogger.java:106)
> E at
> org.apache.cassandra.service.StorageService.enableFullQueryLogger(StorageService.java:6495)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:72)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:276)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> E at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> E at
> com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> E at
> com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> E at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> E at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> E at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17563) Fix CircleCI Midres config
[ https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531417#comment-17531417 ] Ekaterina Dimitrova commented on CASSANDRA-17563: - Now when the CI and branches are back on track, I am going to rebase and run again the patch with our brand new cassandra-4.1 and trunk. Commit pending CI [4.1|https://github.com/apache/cassandra/compare/cassandra-4.1...ekaterinadimitrova2:16677-4.1?expand=1] | [CI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=16677-4.1=all] [trunk |https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:trunk-17589?expand=1]| [CI| https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=trunk-17589=all] > Fix CircleCI Midres config > -- > > Key: CASSANDRA-17563 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17563 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1.x > > > During CircleCI addition of a new job to the config, the midres file got > messy. Two of the immediate issues (but we need to verify all jobs will use > the right executors and resources): > * the new job needs to use higher parallelism as the original in-jvm job > * j8_dtests_with_vnodes should get from midres 50 large but currently > midres makes it run with 25 and medium which fails around 100 tests -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15606) Support Logback and log4j2
[ https://issues.apache.org/jira/browse/CASSANDRA-15606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Savni Nagarkar reassigned CASSANDRA-15606: -- Assignee: Savni Nagarkar > Support Logback and log4j2 > -- > > Key: CASSANDRA-15606 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15606 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: David Capwell >Assignee: Savni Nagarkar >Priority: Normal > > Right now we only support Logback, CCM expects this as well; it is desirable > to also support log4j2. > Right now, if someone wishes to use log4j2 they have to do the following > 1) Compile with Logback > 2) delete logback jars > 3) add log4j2 jars > 4) disable logging in CCM > This should be simpler and should just be based off the operator (if Logback > is better for you, use it, if log4j2 is then use it). > The main point where we depend on Logback is > org.apache.cassandra.utils.logging.LogbackLoggingSupport and this is only > enabled if org.apache.cassandra.utils.logging.LoggingSupportFactory sees > “logback” in the class name; else everything is disabled (which is why the > above steps work). This logic adds some nice integration so this should not > be lost and should also be supported in log4j2. > Lastly, given the implementation of how slf4j picks the binding > (ServiceLoader which is classpath order), we should make sure its clear how > to properly switch between the two; ideally, if the operator some how selects > both, the behavior should be deterministic (slf4j is not)) -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17563) Fix CircleCI Midres config
[ https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17563: Reviewers: Andres de la Peña, Ekaterina Dimitrova, Josh McKenzie, Ekaterina Dimitrova (was: Ekaterina Dimitrova, Josh McKenzie) Andres de la Peña, Ekaterina Dimitrova, Josh McKenzie, Ekaterina Dimitrova (was: Andres de la Peña, Ekaterina Dimitrova, Josh McKenzie) Status: Review In Progress (was: Patch Available) > Fix CircleCI Midres config > -- > > Key: CASSANDRA-17563 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17563 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1 > > > During CircleCI addition of a new job to the config, the midres file got > messy. Two of the immediate issues (but we need to verify all jobs will use > the right executors and resources): > * the new job needs to use higher parallelism as the original in-jvm job > * j8_dtests_with_vnodes should get from midres 50 large but currently > midres makes it run with 25 and medium which fails around 100 tests -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17563) Fix CircleCI Midres config
[ https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17563: Fix Version/s: 4.1.x (was: 4.1) > Fix CircleCI Midres config > -- > > Key: CASSANDRA-17563 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17563 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1.x > > > During CircleCI addition of a new job to the config, the midres file got > messy. Two of the immediate issues (but we need to verify all jobs will use > the right executors and resources): > * the new job needs to use higher parallelism as the original in-jvm job > * j8_dtests_with_vnodes should get from midres 50 large but currently > midres makes it run with 25 and medium which fails around 100 tests -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17595) nodetool enablefullquerylog can NPE when directory has no files
[
https://issues.apache.org/jira/browse/CASSANDRA-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17595:
--
Test and Documentation Plan: existing tests
Status: Patch Available (was: In Progress)
> nodetool enablefullquerylog can NPE when directory has no files
> ---
>
> Key: CASSANDRA-17595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17595
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.1.x
>
>
> fqltool_test.py::TestFQLTool::test_unclean_enable found an issue with
> org.apache.cassandra.utils.binlog.BinLog#deleteRecursively, it assumes
> listing files returns empty list rather than null and throws a NPE
> {code}
> E -- StackTrace --
> E java.lang.NullPointerException
> E at
> org.apache.cassandra.utils.binlog.BinLog.deleteRecursively(BinLog.java:490)
> E at
> org.apache.cassandra.utils.binlog.BinLog.cleanDirectory(BinLog.java:477)
> E at
> org.apache.cassandra.utils.binlog.BinLog$Builder.build(BinLog.java:436)
> E at
> org.apache.cassandra.fql.FullQueryLogger.enable(FullQueryLogger.java:106)
> E at
> org.apache.cassandra.service.StorageService.enableFullQueryLogger(StorageService.java:6495)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:72)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:276)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> E at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> E at
> com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> E at
> com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> E at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> E at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> E at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17595) nodetool enablefullquerylog can NPE when directory has no files
David Capwell created CASSANDRA-17595:
-
Summary: nodetool enablefullquerylog can NPE when directory has no
files
Key: CASSANDRA-17595
URL: https://issues.apache.org/jira/browse/CASSANDRA-17595
Project: Cassandra
Issue Type: Bug
Components: Tool/fql
Reporter: David Capwell
fqltool_test.py::TestFQLTool::test_unclean_enable found an issue with
org.apache.cassandra.utils.binlog.BinLog#deleteRecursively, it assumes listing
files returns empty list rather than null and throws a NPE
{code}
E -- StackTrace --
E java.lang.NullPointerException
E at
org.apache.cassandra.utils.binlog.BinLog.deleteRecursively(BinLog.java:490)
E at
org.apache.cassandra.utils.binlog.BinLog.cleanDirectory(BinLog.java:477)
E at
org.apache.cassandra.utils.binlog.BinLog$Builder.build(BinLog.java:436)
E at
org.apache.cassandra.fql.FullQueryLogger.enable(FullQueryLogger.java:106)
E at
org.apache.cassandra.service.StorageService.enableFullQueryLogger(StorageService.java:6495)
E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
E at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
E at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
E at java.lang.reflect.Method.invoke(Method.java:498)
E at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:72)
E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
E at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
E at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
E at java.lang.reflect.Method.invoke(Method.java:498)
E at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:276)
E at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
E at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
E at
com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
E at
com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
E at
com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
E at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
E at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
E at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
E at
javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
E at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
E at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
E at
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17595) nodetool enablefullquerylog can NPE when directory has no files
[
https://issues.apache.org/jira/browse/CASSANDRA-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17595:
--
Bug Category: Parent values: Correctness(12982)Level 1 values: Transient
Incorrect Response(12987)
Complexity: Low Hanging Fruit
Discovered By: Unit Test
Fix Version/s: 4.1.x
Severity: Critical
Status: Open (was: Triage Needed)
> nodetool enablefullquerylog can NPE when directory has no files
> ---
>
> Key: CASSANDRA-17595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17595
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.1.x
>
>
> fqltool_test.py::TestFQLTool::test_unclean_enable found an issue with
> org.apache.cassandra.utils.binlog.BinLog#deleteRecursively, it assumes
> listing files returns empty list rather than null and throws a NPE
> {code}
> E -- StackTrace --
> E java.lang.NullPointerException
> E at
> org.apache.cassandra.utils.binlog.BinLog.deleteRecursively(BinLog.java:490)
> E at
> org.apache.cassandra.utils.binlog.BinLog.cleanDirectory(BinLog.java:477)
> E at
> org.apache.cassandra.utils.binlog.BinLog$Builder.build(BinLog.java:436)
> E at
> org.apache.cassandra.fql.FullQueryLogger.enable(FullQueryLogger.java:106)
> E at
> org.apache.cassandra.service.StorageService.enableFullQueryLogger(StorageService.java:6495)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:72)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:276)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> E at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> E at
> com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> E at
> com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> E at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> E at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> E at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17595) nodetool enablefullquerylog can NPE when directory has no files
[
https://issues.apache.org/jira/browse/CASSANDRA-17595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell reassigned CASSANDRA-17595:
-
Assignee: David Capwell
> nodetool enablefullquerylog can NPE when directory has no files
> ---
>
> Key: CASSANDRA-17595
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17595
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/fql
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
>
> fqltool_test.py::TestFQLTool::test_unclean_enable found an issue with
> org.apache.cassandra.utils.binlog.BinLog#deleteRecursively, it assumes
> listing files returns empty list rather than null and throws a NPE
> {code}
> E -- StackTrace --
> E java.lang.NullPointerException
> E at
> org.apache.cassandra.utils.binlog.BinLog.deleteRecursively(BinLog.java:490)
> E at
> org.apache.cassandra.utils.binlog.BinLog.cleanDirectory(BinLog.java:477)
> E at
> org.apache.cassandra.utils.binlog.BinLog$Builder.build(BinLog.java:436)
> E at
> org.apache.cassandra.fql.FullQueryLogger.enable(FullQueryLogger.java:106)
> E at
> org.apache.cassandra.service.StorageService.enableFullQueryLogger(StorageService.java:6495)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:72)
> E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> E at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> E at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> E at java.lang.reflect.Method.invoke(Method.java:498)
> E at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:276)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
> E at
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
> E at
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
> E at
> com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
> E at
> com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
> E at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
> E at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
> E at
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
> E at
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17544) Add EnableFlag to guardrails API
[
https://issues.apache.org/jira/browse/CASSANDRA-17544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531403#comment-17531403
]
Bernardo Botella Corbi commented on CASSANDRA-17544:
Posted the rebase. Please let me know if more changes are needed. Happy to help!
> Add EnableFlag to guardrails API
>
>
> Key: CASSANDRA-17544
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17544
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Guardrails
>Reporter: Josh McKenzie
>Assignee: Bernardo Botella Corbi
>Priority: Low
> Fix For: 4.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently we only have a DisableFlag which, for guardrails where we're
> enabling or disabling a feature, leads to some pretty odd ergonomics in the
> code. For example:
>
> {code:java}
> public static final DisableFlag compactTablesEnabled =
> new DisableFlag("compact_tables",
> state ->
> !CONFIG_PROVIDER.getOrCreate(state).getCompactTablesEnabled(),
> "Creation of new COMPACT STORAGE tables"); {code}
> So far, the usage of these toggle flags appears to be skewed heavily towards
> the inverse, or an EnableFlag that'd look something like this:
> {code:java}
> public static final EnableFlag featureEnabled = new
> EnableFlag("feature_name", state ->
> CONFIG_PROVIDER.getOrCreate(state).getCompactTablesEnabled(), "Text for
> feature"); {code}
> While it's a relatively small change it'll help tidy up some of the
> guardrails framework and make the logic clearer.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17571) Config upper bound should be handled earlier
[ https://issues.apache.org/jira/browse/CASSANDRA-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17571: Fix Version/s: 4.1.x (was: 4.1) > Config upper bound should be handled earlier > > > Key: CASSANDRA-17571 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17571 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1.x > > > Config upper bound should be handled on startup/config setup and not during > conversion -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17594) Fix flaky python-tests due to connection getting closed
[
https://issues.apache.org/jira/browse/CASSANDRA-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-17594:
Reviewers: Caleb Rackliffe, Caleb Rackliffe
Caleb Rackliffe, Caleb Rackliffe (was: Caleb Rackliffe)
Status: Review In Progress (was: Patch Available)
> Fix flaky python-tests due to connection getting closed
> ---
>
> Key: CASSANDRA-17594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We log unknown exceptions at the networking level, which includes case where
> the remote side closes the connection (such as the cases caused by shutting
> down), depending on how quickly the instances shutdown, this could cause
> python-dtest to fail for random tests with a message such as
> {code}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800
> ExceptionHandlers.java:134 - Unknown exception in client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer, WARN [epollEventLoopGroup-5-9]
> 2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in
> client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17557) Fix a few config parameters after the Paxos improvements commit
[ https://issues.apache.org/jira/browse/CASSANDRA-17557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17557: Fix Version/s: 4.1.x (was: 4.1) > Fix a few config parameters after the Paxos improvements commit > --- > > Key: CASSANDRA-17557 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17557 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.1.x > > > After committing the Paxos improvements, it was identified that the following > configuration parameters need additional work: > * repair_request_timeout_in_ms - can be removed > * paxos_auto_repair_threshold_mb - I think it can be also removed; to be > confirmed with the author > Discussed a bit in Slack and on this PR - > https://github.com/apache/cassandra/commit/d2923275e360a1ee9db498e748c269f701bb3a8b -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17594) Fix flaky python-tests due to connection getting closed
[
https://issues.apache.org/jira/browse/CASSANDRA-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17594:
--
Test and Documentation Plan: submitted CI against the branch
Status: Patch Available (was: In Progress)
> Fix flaky python-tests due to connection getting closed
> ---
>
> Key: CASSANDRA-17594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We log unknown exceptions at the networking level, which includes case where
> the remote side closes the connection (such as the cases caused by shutting
> down), depending on how quickly the instances shutdown, this could cause
> python-dtest to fail for random tests with a message such as
> {code}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800
> ExceptionHandlers.java:134 - Unknown exception in client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer, WARN [epollEventLoopGroup-5-9]
> 2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in
> client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16052) CEP-7 Storage Attached Indexes
[ https://issues.apache.org/jira/browse/CASSANDRA-16052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531386#comment-17531386 ] Caleb Rackliffe commented on CASSANDRA-16052: - With CASSANDRA-17034 merged, the remaining large dependency we need to take care of to make further progress w/ this is CASSANDRA-17240. [~adelapena] and I should be starting review for that soon... > CEP-7 Storage Attached Indexes > -- > > Key: CASSANDRA-16052 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16052 > Project: Cassandra > Issue Type: Epic > Components: Feature/2i Index >Reporter: Zhao Yang >Assignee: Caleb Rackliffe >Priority: Normal > Fix For: 5.x > > Time Spent: 0.5h > Remaining Estimate: 0h > > [CEP|https://docs.google.com/document/d/1V830eAMmQAspjJdjviVZIaSolVGvZ1hVsqOLWyV0DS4/edit#heading=h.67ap6rr1mxr] > - A new index implementation, called Storage > Attached Index(SAI), based on the advancement made by SASI. > * disk usage by sharing of common data between multiple column indexes on > the same table and better compression of on-disk structures. > * numeric range query performance with modified KDTree and collection type > support. > * compaction performance and stability for larger data set. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17594) Fix flaky python-tests due to connection getting closed
[
https://issues.apache.org/jira/browse/CASSANDRA-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531384#comment-17531384
]
David Capwell commented on CASSANDRA-17594:
---
thanks, rebased and kicked off CI
> Fix flaky python-tests due to connection getting closed
> ---
>
> Key: CASSANDRA-17594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
>
> We log unknown exceptions at the networking level, which includes case where
> the remote side closes the connection (such as the cases caused by shutting
> down), depending on how quickly the instances shutdown, this could cause
> python-dtest to fail for random tests with a message such as
> {code}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800
> ExceptionHandlers.java:134 - Unknown exception in client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer, WARN [epollEventLoopGroup-5-9]
> 2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in
> client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17594) Fix flaky python-tests due to connection getting closed
[
https://issues.apache.org/jira/browse/CASSANDRA-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531380#comment-17531380
]
Ekaterina Dimitrova commented on CASSANDRA-17594:
-
You might want to rebase before submitting it :) Mick just made final CI
changes after the branching so things should be fine now but... please, rebase
:)
> Fix flaky python-tests due to connection getting closed
> ---
>
> Key: CASSANDRA-17594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
>
> We log unknown exceptions at the networking level, which includes case where
> the remote side closes the connection (such as the cases caused by shutting
> down), depending on how quickly the instances shutdown, this could cause
> python-dtest to fail for random tests with a message such as
> {code}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800
> ExceptionHandlers.java:134 - Unknown exception in client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer, WARN [epollEventLoopGroup-5-9]
> 2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in
> client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531377#comment-17531377
]
Michael Semb Wever commented on CASSANDRA-17589:
Remaining PRs (in cassandra-builds for (5) and (6) committed with
[3d3150124c3d6aef94f580a0f97531aa9c427f65|https://github.com/apache/cassandra-builds/commit/3d3150124c3d6aef94f580a0f97531aa9c427f65]
and
[d2d15cee9c417e502e29a1a92ded6efa31b92707|https://github.com/apache/cassandra-builds/commit/d2d15cee9c417e502e29a1a92ded6efa31b92707].
> Create release branch cassandra-4.1
> ---
>
> Key: CASSANDRA-17589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17589
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.1 trunk
> git push --set-upstream origin cassandra-4.1
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.2
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> 3. Add `4.1.x` to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 4.x to 4.1.x)
> 4. Update docker images to include cassandra-4.1
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-builds] 02/02: Update trunk to version 4.2
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-builds.git
commit d2d15cee9c417e502e29a1a92ded6efa31b92707
Author: Mick Semb Wever
AuthorDate: Mon May 2 15:59:41 2022 +0200
Update trunk to version 4.2
Ddocker testing images to include cassandra-4.2 (delete unused ubuntu1910).
Build dtest jar for 4.2 too.
Add 4.1 ci-cassandra.a.o jobs.
Increase git's http.postBuffer (common CI problem).
patch by Mick Semb Wever; reviewed by Ekaterina Dimitrova for
CASSANDRA-17589
---
build-scripts/cassandra-test.sh| 2 +-
docker/almalinux-image.docker | 1 +
docker/buster-image.docker | 1 +
docker/centos8-image.docker| 1 +
docker/jessie-image.docker | 1 +
docker/testing/ubuntu1910_j11.docker | 133 -
.../testing/ubuntu1910_j11_w_dependencies.docker | 39 --
.../testing/ubuntu2004_j11_w_dependencies.docker | 3 +
jenkins-dsl/cassandra_job_dsl_seed.groovy | 8 +-
9 files changed, 12 insertions(+), 177 deletions(-)
diff --git a/build-scripts/cassandra-test.sh b/build-scripts/cassandra-test.sh
index e83778c..bb9b9d3 100755
--- a/build-scripts/cassandra-test.sh
+++ b/build-scripts/cassandra-test.sh
@@ -38,7 +38,7 @@ _build_all_dtest_jars() {
cd $TMP_DIR
until git clone --quiet --depth 1 --no-single-branch
https://github.com/apache/cassandra.git cassandra-dtest-jars ; do echo "git
clone failed… trying again… " ; done
cd cassandra-dtest-jars
-for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0
trunk; do
+for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0
cassandra-4.1 trunk; do
git checkout $branch
ant realclean
ant jar dtest-jar
diff --git a/docker/almalinux-image.docker b/docker/almalinux-image.docker
index 01c266a..3b7b17a 100644
--- a/docker/almalinux-image.docker
+++ b/docker/almalinux-image.docker
@@ -47,6 +47,7 @@ RUN mkdir -p
$RPM_BUILD_DIR/{BUILD,BUILDROOT,RPMS,SOURCES,SPECS,SRPMS}
# Clone Cassandra and cache maven artifacts
ARG CASSANDRA_GIT_URL=https://github.com/apache/cassandra.git
+RUN git config --global http.postBuffer 524288000
RUN git clone ${CASSANDRA_GIT_URL} ${CASSANDRA_DIR}
WORKDIR $CASSANDRA_DIR
diff --git a/docker/buster-image.docker b/docker/buster-image.docker
index 04a3e87..c24167c 100644
--- a/docker/buster-image.docker
+++ b/docker/buster-image.docker
@@ -48,6 +48,7 @@ USER build
# clone Cassandra and cache maven artifacts
ARG CASSANDRA_GIT_URL=https://github.com/apache/cassandra.git
+RUN git config --global http.postBuffer 524288000
RUN git clone ${CASSANDRA_GIT_URL} ${CASSANDRA_DIR}
WORKDIR ${CASSANDRA_DIR}
diff --git a/docker/centos8-image.docker b/docker/centos8-image.docker
index 01ddd0b..226dcec 100644
--- a/docker/centos8-image.docker
+++ b/docker/centos8-image.docker
@@ -47,6 +47,7 @@ RUN mkdir -p
$RPM_BUILD_DIR/{BUILD,BUILDROOT,RPMS,SOURCES,SPECS,SRPMS}
# Clone Cassandra and cache maven artifacts
ARG CASSANDRA_GIT_URL=https://github.com/apache/cassandra.git
+RUN git config --global http.postBuffer 524288000
RUN git clone ${CASSANDRA_GIT_URL} ${CASSANDRA_DIR}
WORKDIR $CASSANDRA_DIR
diff --git a/docker/jessie-image.docker b/docker/jessie-image.docker
index 1ae10cc..b564a15 100644
--- a/docker/jessie-image.docker
+++ b/docker/jessie-image.docker
@@ -42,6 +42,7 @@ USER build
# clone Cassandra and cache maven artifacts
ARG CASSANDRA_GIT_URL=https://github.com/apache/cassandra.git
+RUN git config --global http.postBuffer 524288000
RUN git clone ${CASSANDRA_GIT_URL} ${CASSANDRA_DIR}
WORKDIR ${CASSANDRA_DIR}
diff --git a/docker/testing/ubuntu1910_j11.docker
b/docker/testing/ubuntu1910_j11.docker
deleted file mode 100644
index 0449852..000
--- a/docker/testing/ubuntu1910_j11.docker
+++ /dev/null
@@ -1,133 +0,0 @@
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-# http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-FROM ubuntu:19.10
-MAINTAINER Apache Cassandra
-
-# configure apt to retry downloads
-RUN echo 'APT::Acquire::Retries "9";' > /etc/apt/apt.conf.d/80-retries
-
-# install our python dependencies and some other stuff we need
-# libev4 libev-dev are for the python driver / libssl-dev is for python3.6
-
-RUN export DEBIAN_FRONTEND=noninteractive && \
-sed -i -re
[cassandra-builds] 01/02: Use the git clone reference feature in jenkins, pointing each split's git clone to the first split
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-builds.git
commit 3d3150124c3d6aef94f580a0f97531aa9c427f65
Author: Mick Semb Wever
AuthorDate: Sun Apr 10 20:33:58 2022 +0200
Use the git clone reference feature in jenkins, pointing each split's git
clone to the first split
Also clean the workspace when jobs are done.
patch by Mick Semb Wever; reviewed by Ekaterina Dimitrova for
CASSANDRA-17589
---
jenkins-dsl/cassandra_job_dsl_seed.groovy | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/jenkins-dsl/cassandra_job_dsl_seed.groovy
b/jenkins-dsl/cassandra_job_dsl_seed.groovy
index c2e27a7..43b6493 100644
--- a/jenkins-dsl/cassandra_job_dsl_seed.groovy
+++ b/jenkins-dsl/cassandra_job_dsl_seed.groovy
@@ -272,7 +272,7 @@ matrixJob('Cassandra-template-dtest-matrix') {
cleanAfterCheckout()
cloneOption {
shallow(false)
-reference('.')
+reference('../1')
honorRefspec(true)
noTags(true)
timeout(maxJobHours * 60)
@@ -541,6 +541,7 @@ cassandraBranches.each {
}
}
}
+cleanWs()
}
}
}
@@ -643,6 +644,7 @@ cassandraBranches.each {
}
}
}
+cleanWs()
}
}
}
@@ -716,6 +718,7 @@ cassandraBranches.each {
}
}
}
+cleanWs()
}
}
}
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-builds] branch trunk updated (b830c21 -> d2d15ce)
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-builds.git from b830c21 Revert "ninja-fix – disable arm64 builds until INFRA-22930 is resolved properly" new 3d31501 Use the git clone reference feature in jenkins, pointing each split's git clone to the first split new d2d15ce Update trunk to version 4.2 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: build-scripts/cassandra-test.sh| 2 +- docker/almalinux-image.docker | 1 + docker/buster-image.docker | 1 + docker/centos8-image.docker| 1 + docker/jessie-image.docker | 1 + docker/testing/ubuntu1910_j11.docker | 133 - .../testing/ubuntu1910_j11_w_dependencies.docker | 39 -- .../testing/ubuntu2004_j11_w_dependencies.docker | 3 + jenkins-dsl/cassandra_job_dsl_seed.groovy | 13 +- 9 files changed, 16 insertions(+), 178 deletions(-) delete mode 100644 docker/testing/ubuntu1910_j11.docker delete mode 100644 docker/testing/ubuntu1910_j11_w_dependencies.docker - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531372#comment-17531372
]
Michael Semb Wever commented on CASSANDRA-17589:
(2a) and (6) in-tree committed with
[2480a7e7ee64791acec6add38e134753b95236fd|https://github.com/apache/cassandra/commit/2480a7e7ee64791acec6add38e134753b95236fd]
and
[99bf8ba465b15baa59d3dc4e0ed861721dabd191|https://github.com/apache/cassandra/commit/99bf8ba465b15baa59d3dc4e0ed861721dabd191].
> Create release branch cassandra-4.1
> ---
>
> Key: CASSANDRA-17589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17589
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.1 trunk
> git push --set-upstream origin cassandra-4.1
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.2
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> 3. Add `4.1.x` to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 4.x to 4.1.x)
> 4. Update docker images to include cassandra-4.1
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
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: Update trunk to version 4.2
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 2480a7e7ee Update trunk to version 4.2 2480a7e7ee is described below commit 2480a7e7ee64791acec6add38e134753b95236fd Author: Mick Semb Wever AuthorDate: Mon May 2 17:17:46 2022 +0200 Update trunk to version 4.2 Update jvm-dtest supported upgrade paths. Update circeci to build 4.1 dtest jar patch by Mick Semb Wever; reviewed by Ekaterina Dimitrova for CASSANDRA-17589 --- .circleci/config-2_1.yml | 2 +- .circleci/config.yml | 2 +- .circleci/config.yml.HIGHRES | 2 +- .circleci/config.yml.LOWRES | 2 +- .circleci/config.yml.MIDRES | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.circleci/config-2_1.yml b/.circleci/config-2_1.yml index d57d7ed391..21323e9a57 100644 --- a/.circleci/config-2_1.yml +++ b/.circleci/config-2_1.yml @@ -1228,7 +1228,7 @@ commands: cd ~/cassandra mkdir ~/dtest_jars git remote add apache https://github.com/apache/cassandra.git - for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0 trunk; do + for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0 cassandra-4.1 trunk; do # check out the correct cassandra version: git remote set-branches --add apache '$branch' git fetch --depth 1 apache $branch diff --git a/.circleci/config.yml b/.circleci/config.yml index be35258a5c..7e945d1933 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -3619,7 +3619,7 @@ jobs: cd ~/cassandra mkdir ~/dtest_jars git remote add apache https://github.com/apache/cassandra.git - for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0 trunk; do + for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0 cassandra-4.1 trunk; do # check out the correct cassandra version: git remote set-branches --add apache '$branch' git fetch --depth 1 apache $branch diff --git a/.circleci/config.yml.HIGHRES b/.circleci/config.yml.HIGHRES index d64c2647e0..3696a28340 100644 --- a/.circleci/config.yml.HIGHRES +++ b/.circleci/config.yml.HIGHRES @@ -3619,7 +3619,7 @@ jobs: cd ~/cassandra mkdir ~/dtest_jars git remote add apache https://github.com/apache/cassandra.git - for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0 trunk; do + for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0 cassandra-4.1 trunk; do # check out the correct cassandra version: git remote set-branches --add apache '$branch' git fetch --depth 1 apache $branch diff --git a/.circleci/config.yml.LOWRES b/.circleci/config.yml.LOWRES index be35258a5c..7e945d1933 100644 --- a/.circleci/config.yml.LOWRES +++ b/.circleci/config.yml.LOWRES @@ -3619,7 +3619,7 @@ jobs: cd ~/cassandra mkdir ~/dtest_jars git remote add apache https://github.com/apache/cassandra.git - for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0 trunk; do + for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0 cassandra-4.1 trunk; do # check out the correct cassandra version: git remote set-branches --add apache '$branch' git fetch --depth 1 apache $branch diff --git a/.circleci/config.yml.MIDRES b/.circleci/config.yml.MIDRES index 988db3ef1c..2f62019162 100644 --- a/.circleci/config.yml.MIDRES +++ b/.circleci/config.yml.MIDRES @@ -3619,7 +3619,7 @@ jobs: cd ~/cassandra mkdir ~/dtest_jars git remote add apache https://github.com/apache/cassandra.git - for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0 trunk; do + for branch in cassandra-2.2 cassandra-3.0 cassandra-3.11 cassandra-4.0 cassandra-4.1 trunk; do # check out the correct cassandra version: git remote set-branches --add apache '$branch' git fetch --depth 1 apache $branch - 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 99bf8ba465b15baa59d3dc4e0ed861721dabd191
Merge: 963c24969e 2480a7e7ee
Author: Mick Semb Wever
AuthorDate: Tue May 3 20:46:45 2022 +0200
Merge branch 'cassandra-4.1' into trunk
.circleci/config-2_1.yml | 2 +-
.circleci/config.yml | 2 +-
.circleci/config.yml.HIGHRES | 2 +-
.circleci/config.yml.LOWRES| 2 +-
.circleci/config.yml.MIDRES| 2 +-
.../org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java | 7 ++-
6 files changed, 11 insertions(+), 6 deletions(-)
diff --cc
test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
index 5c32fcdd3b,5c32fcdd3b..e530dbdc45
---
a/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
+++
b/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java
@@@ -86,14 -86,14 +86,19 @@@ public class UpgradeTestBase extends Di
public static final Semver v3X = new Semver("3.11.0", SemverType.LOOSE);
public static final Semver v40 = new Semver("4.0-alpha1",
SemverType.LOOSE);
public static final Semver v41 = new Semver("4.1-alpha1",
SemverType.LOOSE);
++public static final Semver v42 = new Semver("4.2-alpha1",
SemverType.LOOSE);
protected static final List> SUPPORTED_UPGRADE_PATHS
= ImmutableList.of(
Pair.create(v30, v3X),
Pair.create(v30, v40),
Pair.create(v30, v41),
++Pair.create(v30, v42),
Pair.create(v3X, v40),
Pair.create(v3X, v41),
--Pair.create(v40, v41));
++Pair.create(v3X, v42),
++Pair.create(v40, v41),
++Pair.create(v40, v42),
++Pair.create(v41, v42));
// the last is always the current
public static final Semver CURRENT =
SUPPORTED_UPGRADE_PATHS.get(SUPPORTED_UPGRADE_PATHS.size() - 1).right;
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (963c24969e -> 99bf8ba465)
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 963c24969e Merge branch 'cassandra-4.1' into trunk new 2480a7e7ee Update trunk to version 4.2 new 99bf8ba465 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: .circleci/config-2_1.yml | 2 +- .circleci/config.yml | 2 +- .circleci/config.yml.HIGHRES | 2 +- .circleci/config.yml.LOWRES| 2 +- .circleci/config.yml.MIDRES| 2 +- .../org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java | 7 ++- 6 files changed, 11 insertions(+), 6 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17594) Fix flaky python-tests due to connection getting closed
[
https://issues.apache.org/jira/browse/CASSANDRA-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531362#comment-17531362
]
David Capwell commented on CASSANDRA-17594:
---
will linke CI after lunch
> Fix flaky python-tests due to connection getting closed
> ---
>
> Key: CASSANDRA-17594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
>
> We log unknown exceptions at the networking level, which includes case where
> the remote side closes the connection (such as the cases caused by shutting
> down), depending on how quickly the instances shutdown, this could cause
> python-dtest to fail for random tests with a message such as
> {code}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800
> ExceptionHandlers.java:134 - Unknown exception in client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer, WARN [epollEventLoopGroup-5-9]
> 2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in
> client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17594) Fix flaky python-tests due to connection getting closed
[
https://issues.apache.org/jira/browse/CASSANDRA-17594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17594:
--
Bug Category: Parent values: Correctness(12982)Level 1 values: Transient
Incorrect Response(12987)
Complexity: Low Hanging Fruit
Discovered By: Unit Test
Fix Version/s: NA
Severity: Normal
Status: Open (was: Triage Needed)
> Fix flaky python-tests due to connection getting closed
> ---
>
> Key: CASSANDRA-17594
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: NA
>
>
> We log unknown exceptions at the networking level, which includes case where
> the remote side closes the connection (such as the cases caused by shutting
> down), depending on how quickly the instances shutdown, this could cause
> python-dtest to fail for random tests with a message such as
> {code}
> Unexpected error found in node logs (see stdout for full details). Errors:
> [WARN [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800
> ExceptionHandlers.java:134 - Unknown exception in client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer, WARN [epollEventLoopGroup-5-9]
> 2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in
> client networking
> io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
> Connection reset by peer]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17594) Fix flaky python-tests due to connection getting closed
David Capwell created CASSANDRA-17594:
-
Summary: Fix flaky python-tests due to connection getting closed
Key: CASSANDRA-17594
URL: https://issues.apache.org/jira/browse/CASSANDRA-17594
Project: Cassandra
Issue Type: Bug
Components: Test/dtest/python
Reporter: David Capwell
Assignee: David Capwell
We log unknown exceptions at the networking level, which includes case where
the remote side closes the connection (such as the cases caused by shutting
down), depending on how quickly the instances shutdown, this could cause
python-dtest to fail for random tests with a message such as
{code}
Unexpected error found in node logs (see stdout for full details). Errors:
[WARN [epollEventLoopGroup-5-9] 2022-05-03T16:47:03,800
ExceptionHandlers.java:134 - Unknown exception in client networking
io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
Connection reset by peer, WARN [epollEventLoopGroup-5-9]
2022-05-03T16:47:03,800 ExceptionHandlers.java:134 - Unknown exception in
client networking
io.netty.channel.unix.Errors$NativeIoException: writeAddress(..) failed:
Connection reset by peer]
{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531358#comment-17531358
]
Michael Semb Wever commented on CASSANDRA-17589:
(6) dtest patch submitted with
[3801a9b00884279a3e8c095b1cf6fb920ac76fa8|https://github.com/apache/cassandra-dtest/commit/3801a9b00884279a3e8c095b1cf6fb920ac76fa8].
> Create release branch cassandra-4.1
> ---
>
> Key: CASSANDRA-17589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17589
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.1 trunk
> git push --set-upstream origin cassandra-4.1
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.2
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> 3. Add `4.1.x` to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 4.x to 4.1.x)
> 4. Update docker images to include cassandra-4.1
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-dtest] branch trunk updated: Update trunk to version 4.2
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-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new 3801a9b0 Update trunk to version 4.2
3801a9b0 is described below
commit 3801a9b00884279a3e8c095b1cf6fb920ac76fa8
Author: Mick Semb Wever
AuthorDate: Mon May 2 20:54:50 2022 +0200
Update trunk to version 4.2
patch by Mick Semb Wever; reviewed by Ekaterina Dimitrova for
CASSANDRA-17589
---
upgrade_tests/upgrade_manifest.py | 24 +++-
1 file changed, 15 insertions(+), 9 deletions(-)
diff --git a/upgrade_tests/upgrade_manifest.py
b/upgrade_tests/upgrade_manifest.py
index 29382f09..02361ef8 100644
--- a/upgrade_tests/upgrade_manifest.py
+++ b/upgrade_tests/upgrade_manifest.py
@@ -27,7 +27,8 @@ CASSANDRA_3_0 = '3.0'
CASSANDRA_3_11 = '3.11'
CASSANDRA_4_0 = '4.0'
CASSANDRA_4_1 = '4.1'
-TRUNK = CASSANDRA_4_1
+CASSANDRA_4_2 = '4.2'
+TRUNK = CASSANDRA_4_2
def is_same_family_current_to_indev(origin, destination):
"""
@@ -100,6 +101,8 @@ def set_version_family():
version_family = CASSANDRA_4_0
elif current_version.vstring.startswith('4.1'):
version_family = CASSANDRA_4_1
+elif current_version.vstring.startswith('4.2'):
+version_family = CASSANDRA_4_2
else:
# when this occurs, it's time to update this manifest a bit!
raise RuntimeError("Testing upgrades from/to version %s is not
supported. Please use a custom manifest (see upgrade_manifest.py)" %
current_version.vstring)
@@ -154,14 +157,17 @@ indev_2_2_x = VersionMeta(name='indev_2_2_x',
family=CASSANDRA_2_2, variant='ind
current_2_2_x = VersionMeta(name='current_2_2_x', family=CASSANDRA_2_2,
variant='current', version='2.2.19', min_proto_v=1, max_proto_v=3,
java_versions=(7, 8))
indev_3_0_x = VersionMeta(name='indev_3_0_x', family=CASSANDRA_3_0,
variant='indev', version='github:apache/cassandra-3.0', min_proto_v=3,
max_proto_v=4, java_versions=(8,))
-current_3_0_x = VersionMeta(name='current_3_0_x', family=CASSANDRA_3_0,
variant='current', version='3.0.24', min_proto_v=3, max_proto_v=4,
java_versions=(8,))
+current_3_0_x = VersionMeta(name='current_3_0_x', family=CASSANDRA_3_0,
variant='current', version='3.0.26', min_proto_v=3, max_proto_v=4,
java_versions=(8,))
indev_3_11_x = VersionMeta(name='indev_3_11_x', family=CASSANDRA_3_11,
variant='indev', version='github:apache/cassandra-3.11', min_proto_v=3,
max_proto_v=4, java_versions=(8,))
-current_3_11_x = VersionMeta(name='current_3_11_x', family=CASSANDRA_3_11,
variant='current', version='3.11.10', min_proto_v=3, max_proto_v=4,
java_versions=(8,))
+current_3_11_x = VersionMeta(name='current_3_11_x', family=CASSANDRA_3_11,
variant='current', version='3.11.12', min_proto_v=3, max_proto_v=4,
java_versions=(8,))
indev_4_0_x = VersionMeta(name='indev_4_0_x', family=CASSANDRA_4_0,
variant='indev', version='github:apache/cassandra-4.0', min_proto_v=3,
max_proto_v=4, java_versions=(8,))
current_4_0_x = VersionMeta(name='current_4_0_x', family=CASSANDRA_4_0,
variant='current', version='4.0.3', min_proto_v=4, max_proto_v=5,
java_versions=(8,))
+indev_4_1_x = VersionMeta(name='indev_4_1_x', family=CASSANDRA_4_1,
variant='indev', version='github:apache/cassandra-4.1', min_proto_v=3,
max_proto_v=4, java_versions=(8,))
+#current_4_1_x = VersionMeta(name='current_4_1_x', family=CASSANDRA_4_1,
variant='current', version='4.1-alpha1', min_proto_v=4, max_proto_v=5,
java_versions=(8,))
+
indev_trunk = VersionMeta(name='indev_trunk', family=TRUNK, variant='indev',
version='github:apache/trunk', min_proto_v=4, max_proto_v=5, java_versions=(8,))
@@ -176,14 +182,14 @@ indev_trunk = VersionMeta(name='indev_trunk',
family=TRUNK, variant='indev', ver
MANIFEST = {
current_2_1_x: [indev_2_2_x, indev_3_0_x, indev_3_11_x],
current_2_2_x: [indev_2_2_x, indev_3_0_x, indev_3_11_x],
-current_3_0_x: [indev_3_0_x, indev_3_11_x, indev_4_0_x, indev_trunk],
-current_3_11_x: [indev_3_11_x, indev_4_0_x, indev_trunk],
-current_4_0_x: [indev_4_0_x, indev_trunk],
+current_3_0_x: [indev_3_0_x, indev_3_11_x, indev_4_0_x, indev_4_1_x,
indev_trunk],
+current_3_11_x: [indev_3_11_x, indev_4_0_x, indev_4_1_x, indev_trunk],
+current_4_0_x: [indev_4_0_x, indev_4_1_x, indev_trunk],
indev_2_2_x: [indev_3_0_x, indev_3_11_x],
-indev_3_0_x: [indev_3_11_x, indev_4_0_x, indev_trunk],
-indev_3_11_x: [indev_4_0_x, indev_trunk],
-indev_4_0_x: [indev_trunk]
+indev_3_0_x: [indev_3_11_x, indev_4_0_x, indev_4_1_x, indev_trunk],
+indev_3_11_x: [indev_4_0_x, indev_4_1_x, indev_trunk],
+indev_4_0_x: [indev_4_1_x, indev_trunk]
}
def _have_common_proto(origin_meta, destination_meta):
-
To unsubscribe, e-mail:
[jira] [Commented] (CASSANDRA-17592) Rename truncate_drop guardrail to drop_truncate_table
[ https://issues.apache.org/jira/browse/CASSANDRA-17592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531351#comment-17531351 ] Josh McKenzie commented on CASSANDRA-17592: --- Either [~aleksey] or [~adelapena] care to take review on this? I'll ping once CI's working in general and I rerun. > Rename truncate_drop guardrail to drop_truncate_table > - > > Key: CASSANDRA-17592 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17592 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Guardrails >Reporter: Josh McKenzie >Assignee: Josh McKenzie >Priority: Normal > > As per discussion on CASSANDRA-17558, we need to rename this guardrail before > 4.1 goes out to include the fact that it only applies to tables. > > This will pave the way for us to add a guardrail to disallow dropping > keyspaces in the future. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17592) Rename truncate_drop guardrail to drop_truncate_table
[ https://issues.apache.org/jira/browse/CASSANDRA-17592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie updated CASSANDRA-17592: -- Summary: Rename truncate_drop guardrail to drop_truncate_table (was: Rename truncate_drop guardrail to truncate_drop_table) > Rename truncate_drop guardrail to drop_truncate_table > - > > Key: CASSANDRA-17592 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17592 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Guardrails >Reporter: Josh McKenzie >Assignee: Josh McKenzie >Priority: Normal > > As per discussion on CASSANDRA-17558, we need to rename this guardrail before > 4.1 goes out to include the fact that it only applies to tables. > > This will pave the way for us to add a guardrail to disallow dropping > keyspaces in the future. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17558) Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser accounts
[ https://issues.apache.org/jira/browse/CASSANDRA-17558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531345#comment-17531345 ] Josh McKenzie commented on CASSANDRA-17558: --- Ticket up w/PR for it here: CASSANDRA-17592 CI having some woes; should be sorted soon enough as Mick's working on it for cassandra-4.1 branch. bq. I'd go with drop_truncate_table_enabled Good call. Just pushed a commit to that branch to do this. Let's follow up on the other ticket. > Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser > accounts > > > Key: CASSANDRA-17558 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17558 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Guardrails >Reporter: Josh McKenzie >Assignee: Josh McKenzie >Priority: Normal > Fix For: 4.1 > > > While this can also be accomplished via roles, there's value in having a > cluster-wide "all role ban" on specific operations that operators can > configure for clusters that have need of those settings. > In this case, we want the ability to completely disallow DROP or TRUNCATE > TABLE commands so users cannot inadvertently throw away data and operators > don't have to runbook managing roles to ensure that this functionality > doesn't leak through. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531343#comment-17531343
]
Ekaterina Dimitrova commented on CASSANDRA-17589:
-
{quote}bq. Just a thought - let's keep it all either on this ticket or
sub-tasks of this ticket so we can then take all that and document the process
on the wiki at the end. Should give us some good targets for automation over
the next year leading up to our next release.
{quote}
+1, that was my intention but didn't express it properly I guess. This ticket
or new, follow up, sub-ticket :)
> Create release branch cassandra-4.1
> ---
>
> Key: CASSANDRA-17589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17589
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.1 trunk
> git push --set-upstream origin cassandra-4.1
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.2
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> 3. Add `4.1.x` to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 4.x to 4.1.x)
> 4. Update docker images to include cassandra-4.1
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531332#comment-17531332
]
Josh McKenzie commented on CASSANDRA-17589:
---
Just a thought - let's keep it all either on this ticket or sub-tasks of this
ticket so we can then take all that and document the process on the wiki at the
end. Should give us some good targets for automation over the next year leading
up to our next release.
> Create release branch cassandra-4.1
> ---
>
> Key: CASSANDRA-17589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17589
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.1 trunk
> git push --set-upstream origin cassandra-4.1
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.2
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> 3. Add `4.1.x` to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 4.x to 4.1.x)
> 4. Update docker images to include cassandra-4.1
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531326#comment-17531326
]
Ekaterina Dimitrova commented on CASSANDRA-17589:
-
A point about Butler was brought in ASF Slack. [~brandon.williams] said he will
take a look at it too tomorrow.
Shall we open a follow up task or keep it under this ticket too? I am not sure
how much work that will be. Butler is new for this release but we need to add
it to our release process from now on. Also, probably we need to document who
has access and what are the technical steps needed.
> Create release branch cassandra-4.1
> ---
>
> Key: CASSANDRA-17589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17589
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.1 trunk
> git push --set-upstream origin cassandra-4.1
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.2
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> 3. Add `4.1.x` to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 4.x to 4.1.x)
> 4. Update docker images to include cassandra-4.1
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16999) system.peers and system.peers_v2 do not contain the native_transport and/or native_transport_port_ssl
[ https://issues.apache.org/jira/browse/CASSANDRA-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531291#comment-17531291 ] Ekaterina Dimitrova commented on CASSANDRA-16999: - Looking around our Jira board, is this a blocker for 4.1? > system.peers and system.peers_v2 do not contain the native_transport and/or > native_transport_port_ssl > - > > Key: CASSANDRA-16999 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16999 > Project: Cassandra > Issue Type: Bug > Components: Local/Other >Reporter: Steve Lacerda >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.0.x, 4.x > > > system.peers_v2 includes a “native_port” but has no notion of > native_transport_port vs. native_transport_port_ssl. Given this limited > information, there’s no clear way for the driver to know that different ports > are being used for SSL vs. non-SSL or which of those two ports is identified > by “native_port”. > > The issue we ran into is that the java driver, since it has no notion of the > transport port SSL, the driver was only using the contact points and was not > load balancing. > > The customer had both set: > native_transport_port: 9042 > native_transport_port_ssl: 9142 > > They were attempting to connect to 9142, but that was failing. They could > only use 9042, and so their applications load balancing was failing. We found > that any node that was a contact point was connecting, but the other nodes > were never acting as coordinators. > > There are still issues in the driver, for which I have created JAVA-2967, > which also refers to JAVA-2638, but the system.peers and system.peers_v2 > tables should both contain native_transport_port and > native_transport_port_ssl. > > -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17416) Test Failure: org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testCDCIndexFileWriteOnSync
[ https://issues.apache.org/jira/browse/CASSANDRA-17416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531264#comment-17531264 ] Josh McKenzie commented on CASSANDRA-17416: --- bq. I think we should either document the behavior or make the update atomic. I would lean to the former for simplicity and re-reading the file is going to give the correct content. WDYT? +1 to documenting the nuance of the API and we can also have the unit test pause a bit and retry N times, throwing a specific exception about the expectation (we expected race w/new file write to lead to us being able to read a new file after retry but got null N times) in there. While still *technically* there's surface area to flake w/that, it should be a vanishingly small pct chance if we retry 100 times with 20ms sleeps and we can give a very direct guide as to why it failed. I'm happy to make both these changes and push up a PR. Thanks for checking and confirming [~yifanc] (as well as checking into Ekaterina's other observed failure pattern) > Test Failure: > org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testCDCIndexFileWriteOnSync > -- > > Key: CASSANDRA-17416 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17416 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Marcus Eriksson >Assignee: Josh McKenzie >Priority: Normal > Fix For: 4.x > > > [https://ci-cassandra.apache.org/job/Cassandra-trunk/985/testReport/org.apache.cassandra.db.commitlog/CommitLogSegmentManagerCDCTest/testCDCIndexFileWriteOnSync_cdc_3/] > h3. Error Message > expected:<1748956> but was:<1749196> > h3. Stacktrace > junit.framework.AssertionFailedError: expected:<1748956> but was:<1749196> at > org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testCDCIndexFileWriteOnSync(CommitLogSegmentManagerCDCTest.java:160) > 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) > h3. Standard Output > INFO [main] 2022-03-02 15:04:59,516 YamlConfigurationLoader.java:103 - > Configuration location: > file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml DEBUG [main] > 2022-03-02 15:04:59,520 YamlConfigurationLoader.java:124 - Loading settings > from file:home/cassandra/cassandra/build/test/cassandra.cdc.yaml INFO > [main] 2022-03-02 15:04:59,674 Config.java:907 - Node > configuration:[allocate_tokens_for_keyspace=null; > allocate_tokens_for_local_replication_factor=null; allow_extra_insecure_ > ...[truncated 4125855 chars]... -02 15:06:57,491 PathUtils.java:73 - Deleting > file during startup: > /home/cassandra/cassandra/build/test/cassandra/data/system_schema/views-9786ac1cdd583201a7cdad556410c985/nb-11-big-Summary.db > DEBUG [MemtableFlushWriter:2] 2022-03-02 15:06:57,496 > ColumnFamilyStore.java:1207 - Flushed to > [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb-55-big-Data.db')] > (1 sstables, 4.895KiB), biggest 4.895KiB, smallest 4.895KiB -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17558) Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser accounts
[ https://issues.apache.org/jira/browse/CASSANDRA-17558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531259#comment-17531259 ] Aleksey Yeschenko commented on CASSANDRA-17558: --- I'd prefer to change it now if we are changing it at all, yes. > Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser > accounts > > > Key: CASSANDRA-17558 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17558 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Guardrails >Reporter: Josh McKenzie >Assignee: Josh McKenzie >Priority: Normal > Fix For: 4.1 > > > While this can also be accomplished via roles, there's value in having a > cluster-wide "all role ban" on specific operations that operators can > configure for clusters that have need of those settings. > In this case, we want the ability to completely disallow DROP or TRUNCATE > TABLE commands so users cannot inadvertently throw away data and operators > don't have to runbook managing roles to ensure that this functionality > doesn't leak through. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17581) nodetool with Java 8u331 returns "URISyntaxException: 'Malformed IPv6 address at index 7: rmi://[127.0.0.1]:7199'"
[
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531246#comment-17531246
]
Ekaterina Dimitrova commented on CASSANDRA-17581:
-
Applicable to both PRs: can we add some tests?
> nodetool with Java 8u331 returns "URISyntaxException: 'Malformed IPv6 address
> at index 7: rmi://[127.0.0.1]:7199'"
> --
>
> Key: CASSANDRA-17581
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17581
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: Jermy Li
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Error when {{{color:#0747a6}new NodeProbe("127.0.0.1", 7199){color}}} with
> {color:#de350b}JDK 1.8.0_332{color}:
> {code:java}
> java.io.IOException: Failed to retrieve RMIServer stub:
> javax.naming.InvalidNameException: Malformed IPv6 address at index 7:
> rmi://[127.0.0.1]:7199
> Root exception is java.lang.IllegalArgumentException: Malformed IPv6 address
> at index 7: rmi://[127.0.0.1]:7199 {code}
> Here is the error stack trace:
> {noformat}
> 2022-04-24 07:22:40 [grizzly-http-server-2] [INFO]
> c.b.h.b.s.c.CassandraMetrics - Probe to cassandra node: '127.0.0.1:7199'
> 2022-04-24 07:22:40 [grizzly-http-server-2] [WARN]
> c.b.h.b.s.c.CassandraMetrics - Unable to get metrics from host '127.0.0.1':
> java.io.IOException: Failed to retrieve RMIServer stub:
> javax.naming.InvalidNameException: Malformed IPv6 address at index 7:
> rmi://[127.0.0.1]:7199 [Root exception is java.lang.IllegalArgumentException:
> Malformed IPv6 address at index 7: rmi://[127.0.0.1]:7199]
> at
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:369)
> ~[?:1.8.0_332]
> at
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
> ~[?:1.8.0_332]
> at org.apache.cassandra.tools.NodeProbe.connect(NodeProbe.java:191)
> ~[cassandra-all-3.10.jar:3.10]
> at org.apache.cassandra.tools.NodeProbe.(NodeProbe.java:158)
> ~[cassandra-all-3.10.jar:3.10]
> at
> com.baidu.hugegraph.backend.store.cassandra.CassandraMetrics.newNodeProbe(CassandraMetrics.java:308)
> ~[hugegraph-cassandra-0.13.0.jar:?]
> at
> com.baidu.hugegraph.backend.store.cassandra.CassandraMetrics.getMetricsByHost(CassandraMetrics.java:100)
> ~[hugegraph-cassandra-0.13.0.jar:?]
> at
> com.baidu.hugegraph.backend.store.cassandra.CassandraMetrics.executeAllHosts(CassandraMetrics.java:299)
> ~[hugegraph-cassandra-0.13.0.jar:?]
> at
> com.baidu.hugegraph.backend.store.cassandra.CassandraMetrics.metrics(CassandraMetrics.java:86)
> ~[hugegraph-cassandra-0.13.0.jar:?]
> at
> com.baidu.hugegraph.backend.store.cassandra.CassandraStore.lambda$registerMetaHandlers$0(CassandraStore.java:99)
> ~[hugegraph-cassandra-0.13.0.jar:?]
> at
> com.baidu.hugegraph.backend.store.MetaDispatcher.dispatchMetaHandler(MetaDispatcher.java:45)
> ~[hugegraph-core-0.13.0.jar:0.13.0.0]
> at
> com.baidu.hugegraph.backend.store.AbstractBackendStore.metadata(AbstractBackendStore.java:53)
> ~[hugegraph-core-0.13.0.jar:0.13.0.0]
> at
> com.baidu.hugegraph.backend.tx.AbstractTransaction.metadata(AbstractTransaction.java:109)
> ~[hugegraph-core-0.13.0.jar:0.13.0.0]
> at
> com.baidu.hugegraph.StandardHugeGraph.metadata(StandardHugeGraph.java:975)
> ~[hugegraph-core-0.13.0.jar:0.13.0.0]
> at
> com.baidu.hugegraph.auth.HugeGraphAuthProxy.metadata(HugeGraphAuthProxy.java:669)
> ~[hugegraph-api-0.13.0.jar:0.67.0.0]
> at com.baidu.hugegraph.api.metrics.MetricsAPI.backend(MetricsAPI.java:87)
> ~[hugegraph-api-0.13.0.jar:0.67.0.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:1.8.0_332]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:1.8.0_332]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:1.8.0_332]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_332]
> at
> org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
> ~[jersey-server-2.25.1.jar:?]
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
> ~[jersey-server-2.25.1.jar:?]
> at
> org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
> ~[jersey-server-2.25.1.jar:?]
> at
>
[jira] [Commented] (CASSANDRA-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531228#comment-17531228
]
Ekaterina Dimitrova commented on CASSANDRA-17589:
-
LGTM, +1
{quote}Both cassandra-builds PRs tested on local jenkins.
{quote}
That is enough for me if you see it locally that the cleaning and the cloning
only from the 1st split work as expected. Thank you!
What do we do with the images? Later?
> Create release branch cassandra-4.1
> ---
>
> Key: CASSANDRA-17589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17589
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.1 trunk
> git push --set-upstream origin cassandra-4.1
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.2
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> 3. Add `4.1.x` to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 4.x to 4.1.x)
> 4. Update docker images to include cassandra-4.1
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531228#comment-17531228
]
Ekaterina Dimitrova edited comment on CASSANDRA-17589 at 5/3/22 2:31 PM:
-
LGTM, +1
{quote}Both cassandra-builds PRs tested on local jenkins.
{quote}
That is enough for me if you see it locally that the cleaning and the cloning
only from the 1st split works as expected. Thank you!
What do we do with the images? Later?
was (Author: e.dimitrova):
LGTM, +1
{quote}Both cassandra-builds PRs tested on local jenkins.
{quote}
That is enough for me if you see it locally that the cleaning and the cloning
only from the 1st split work as expected. Thank you!
What do we do with the images? Later?
> Create release branch cassandra-4.1
> ---
>
> Key: CASSANDRA-17589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17589
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.1 trunk
> git push --set-upstream origin cassandra-4.1
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.2
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> 3. Add `4.1.x` to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 4.x to 4.1.x)
> 4. Update docker images to include cassandra-4.1
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17221) Add Math functions
[
https://issues.apache.org/jira/browse/CASSANDRA-17221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531221#comment-17531221
]
Ekaterina Dimitrova commented on CASSANDRA-17221:
-
Hi [~xvade] , Yes, trunk is where I look at.
Over the weekend cassandra-4.1 and new trunk branches were created and I
suspect this made some mess with your branch. If you check it - the last commit
is some huge merge commit. Your own commits are somewhere in between the trunk
commits.
You should have trunk and last on top of everything else - your own commits.
Please let me know if you need any help.
> Add Math functions
> ---
>
> Key: CASSANDRA-17221
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17221
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Simon Chess
>Priority: Normal
> Labels: AdventCalendar2021, lhf
> Fix For: 4.x
>
>
> We should add native Maths functions for the most common operations:
> * {{abs\(x)}} returns the absolute value of the x
> * {{exp\(x)}} returns the value of e (the base of natural logarithms) raised
> to the power of x
> * {{log\(x)}} returns the natural logarithm (base e) of x
> * {{log10\(x)}} returns the base-10 logarithm of x
> * {{round\(x)}} returns the closest integer to x
> +Additional information for newcomers:+
> The new functions should be put in a new class {{MathFcts}} similar to
> {{TimeFcts}}.
> The {{MathsFcts.all()}} method should be called in
> {{SystemKeyspace.functions}}
> The unit tests for the functions should be put in a {{MathFctsTest}} similar
> to {{TimeFctsTest}}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17451) Flaky upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk.test_noncomposite_static_cf
[
https://issues.apache.org/jira/browse/CASSANDRA-17451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531156#comment-17531156
]
Marcus Eriksson commented on CASSANDRA-17451:
-
tests:
https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1653/
> Flaky
> upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk.test_noncomposite_static_cf
> ---
>
> Key: CASSANDRA-17451
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17451
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Stefan Miklosovic
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 4.x
>
>
> dtest-upgrade.upgrade_tests.cql_tests
> TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk
> test_noncomposite_static_cf is flaky.
> {code}
> Error Message
> cassandra.WriteFailure: Error from server: code=1500 [Replica(s) failed to
> execute write] message="Operation failed - received 1 responses and 1
> failures: UNKNOWN from /127.0.0.1:7000" info={'consistency': 'ONE',
> 'required_responses': 1, 'received_responses': 1, 'failures': 1,
> 'error_code_map': {'127.0.0.1': '0x'}}
> Stacktrace
> self = 0x7fc77ceb7d00>
> def test_noncomposite_static_cf(self):
> """ Test non-composite static CF syntax """
> cursor = self.prepare()
>
> # Create
> cursor.execute("""
> CREATE TABLE users (
> userid uuid PRIMARY KEY,
> firstname ascii,
> lastname ascii,
> age int
> ) WITH COMPACT STORAGE;
> """)
>
> for is_upgraded, cursor in self.do_upgrade(cursor):
> logger.debug("Querying {} node".format("upgraded" if is_upgraded
> else "old"))
> cursor.execute("TRUNCATE users")
>
> # Inserts
> cursor.execute("INSERT INTO users (userid, firstname, lastname,
> age) VALUES (550e8400-e29b-41d4-a716-44665544, 'Frodo', 'Baggins', 32)")
> cursor.execute("UPDATE users SET firstname = 'Samwise', lastname
> = 'Gamgee', age = 33 WHERE userid = f47ac10b-58cc-4372-a567-0e02b2c3d479")
>
> # Queries
> assert_one(cursor, "SELECT firstname, lastname FROM users WHERE
> userid = 550e8400-e29b-41d4-a716-44665544", ['Frodo', 'Baggins'])
>
> assert_one(cursor, "SELECT * FROM users WHERE userid =
> 550e8400-e29b-41d4-a716-44665544",
>[UUID('550e8400-e29b-41d4-a716-44665544'), 32,
> 'Frodo', 'Baggins'])
> # FIXME There appears to be some sort of problem with reusable
> cells
> # when executing this query. It's likely that CASSANDRA-9705 will
> # fix this, but I'm not 100% sure.
> assert_one(cursor, "SELECT * FROM users WHERE userid =
> f47ac10b-58cc-4372-a567-0e02b2c3d479",
>[UUID('f47ac10b-58cc-4372-a567-0e02b2c3d479'), 33,
> 'Samwise', 'Gamgee'])
> assert_all(cursor, "SELECT * FROM users",
>[[UUID('f47ac10b-58cc-4372-a567-0e02b2c3d479'), 33,
> 'Samwise', 'Gamgee'],
> [UUID('550e8400-e29b-41d4-a716-44665544'), 32,
> 'Frodo', 'Baggins']])
>
> # Test batch inserts
> > cursor.execute("""
> BEGIN BATCH
> INSERT INTO users (userid, age) VALUES
> (550e8400-e29b-41d4-a716-44665544, 36)
> UPDATE users SET age = 37 WHERE userid =
> f47ac10b-58cc-4372-a567-0e02b2c3d479
> DELETE firstname, lastname FROM users WHERE userid =
> 550e8400-e29b-41d4-a716-44665544
> DELETE firstname, lastname FROM users WHERE userid =
> f47ac10b-58cc-4372-a567-0e02b2c3d479
> APPLY BATCH
> """)
> upgrade_tests/cql_tests.py:157:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> ../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()
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17451) Flaky upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk.test_noncomposite_static_cf
[
https://issues.apache.org/jira/browse/CASSANDRA-17451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531155#comment-17531155
]
Benedict Elliott Smith commented on CASSANDRA-17451:
+1
> Flaky
> upgrade_tests.cql_tests.TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk.test_noncomposite_static_cf
> ---
>
> Key: CASSANDRA-17451
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17451
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Stefan Miklosovic
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 4.x
>
>
> dtest-upgrade.upgrade_tests.cql_tests
> TestCQLNodes2RF1_Upgrade_current_4_0_x_To_indev_trunk
> test_noncomposite_static_cf is flaky.
> {code}
> Error Message
> cassandra.WriteFailure: Error from server: code=1500 [Replica(s) failed to
> execute write] message="Operation failed - received 1 responses and 1
> failures: UNKNOWN from /127.0.0.1:7000" info={'consistency': 'ONE',
> 'required_responses': 1, 'received_responses': 1, 'failures': 1,
> 'error_code_map': {'127.0.0.1': '0x'}}
> Stacktrace
> self = 0x7fc77ceb7d00>
> def test_noncomposite_static_cf(self):
> """ Test non-composite static CF syntax """
> cursor = self.prepare()
>
> # Create
> cursor.execute("""
> CREATE TABLE users (
> userid uuid PRIMARY KEY,
> firstname ascii,
> lastname ascii,
> age int
> ) WITH COMPACT STORAGE;
> """)
>
> for is_upgraded, cursor in self.do_upgrade(cursor):
> logger.debug("Querying {} node".format("upgraded" if is_upgraded
> else "old"))
> cursor.execute("TRUNCATE users")
>
> # Inserts
> cursor.execute("INSERT INTO users (userid, firstname, lastname,
> age) VALUES (550e8400-e29b-41d4-a716-44665544, 'Frodo', 'Baggins', 32)")
> cursor.execute("UPDATE users SET firstname = 'Samwise', lastname
> = 'Gamgee', age = 33 WHERE userid = f47ac10b-58cc-4372-a567-0e02b2c3d479")
>
> # Queries
> assert_one(cursor, "SELECT firstname, lastname FROM users WHERE
> userid = 550e8400-e29b-41d4-a716-44665544", ['Frodo', 'Baggins'])
>
> assert_one(cursor, "SELECT * FROM users WHERE userid =
> 550e8400-e29b-41d4-a716-44665544",
>[UUID('550e8400-e29b-41d4-a716-44665544'), 32,
> 'Frodo', 'Baggins'])
> # FIXME There appears to be some sort of problem with reusable
> cells
> # when executing this query. It's likely that CASSANDRA-9705 will
> # fix this, but I'm not 100% sure.
> assert_one(cursor, "SELECT * FROM users WHERE userid =
> f47ac10b-58cc-4372-a567-0e02b2c3d479",
>[UUID('f47ac10b-58cc-4372-a567-0e02b2c3d479'), 33,
> 'Samwise', 'Gamgee'])
> assert_all(cursor, "SELECT * FROM users",
>[[UUID('f47ac10b-58cc-4372-a567-0e02b2c3d479'), 33,
> 'Samwise', 'Gamgee'],
> [UUID('550e8400-e29b-41d4-a716-44665544'), 32,
> 'Frodo', 'Baggins']])
>
> # Test batch inserts
> > cursor.execute("""
> BEGIN BATCH
> INSERT INTO users (userid, age) VALUES
> (550e8400-e29b-41d4-a716-44665544, 36)
> UPDATE users SET age = 37 WHERE userid =
> f47ac10b-58cc-4372-a567-0e02b2c3d479
> DELETE firstname, lastname FROM users WHERE userid =
> 550e8400-e29b-41d4-a716-44665544
> DELETE firstname, lastname FROM users WHERE userid =
> f47ac10b-58cc-4372-a567-0e02b2c3d479
> APPLY BATCH
> """)
> upgrade_tests/cql_tests.py:157:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> ../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()
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17456) Test Failures: write_failures_test.TestMultiDCWriteFailures.test_oversized_mutation
[
https://issues.apache.org/jira/browse/CASSANDRA-17456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531148#comment-17531148
]
Andres de la Peña commented on CASSANDRA-17456:
---
Looks good to me, I have just started repeated runs for both
{{OversizedMutationTest}} and {{CommitLogTest}} after rebasing on the new
{{cassandra-4.1}} branch without conflicts:
OversizedMutationTest + pre-commit:
* [j8
|https://app.circleci.com/pipelines/github/adelapena/cassandra/1520/workflows/207ac25e-7a88-4220-8d9d-f752df711450]
*
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1520/workflows/b58bb268-af63-4272-840c-25f028b3e0f5]
CommitLogTest:
* [j8
|https://app.circleci.com/pipelines/github/adelapena/cassandra/1521/workflows/cdb34d69-518b-47ed-8e9d-676695fd8296]
*
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1521/workflows/7b1c1f9b-ad0c-4579-94e2-e7f4a5586567]
> Test Failures:
> write_failures_test.TestMultiDCWriteFailures.test_oversized_mutation
> ---
>
> Key: CASSANDRA-17456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17456
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Aleksandr Sorokoumov
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1002/testReport/dtest-offheap.write_failures_test/TestMultiDCWriteFailures/test_oversized_mutation/
> {code:java}
> Error Message
> AssertionError: assert 0 == 8 + where 8 = JolokiaAgent.read_attribute of 0x7f1fca78dac0>>('org.apache.cassandra.metrics:type=Storage,name=TotalHints',
> 'Count') +where > =
> .read_attribute +
> and 'org.apache.cassandra.metrics:type=Storage,name=TotalHints' =
> make_mbean('metrics', type='Storage', name='TotalHints')
> Stacktrace
> self =
> def test_oversized_mutation(self):
> """
> Test that multi-DC write failures return operation failed rather
> than a timeout.
> @jira_ticket CASSANDRA-16334.
> """
>
> cluster = self.cluster
> cluster.populate([2, 2])
> cluster.set_configuration_options(values={'max_mutation_size_in_kb':
> 128})
> cluster.start()
>
> node1 = cluster.nodelist()[0]
> session = self.patient_exclusive_cql_connection(node1)
>
> session.execute("CREATE KEYSPACE k WITH replication = {'class':
> 'NetworkTopologyStrategy', 'dc1': 2, 'dc2': 2}")
> session.execute("CREATE TABLE k.t (key int PRIMARY KEY, val blob)")
>
> payload = '1' * 1024 * 256
> query = "INSERT INTO k.t (key, val) VALUES (1,
> textAsBlob('{}'))".format(payload)
>
> assert_write_failure(session, query, ConsistencyLevel.LOCAL_ONE)
> assert_write_failure(session, query, ConsistencyLevel.ONE)
>
> # verify that no hints are created
> with JolokiaAgent(node1) as jmx:
> > assert 0 == jmx.read_attribute(make_mbean('metrics',
> > type='Storage', name='TotalHints'), 'Count')
> E AssertionError: assert 0 == 8
> E+ where 8 = 0x7f1fca78dac0>>('org.apache.cassandra.metrics:type=Storage,name=TotalHints',
> 'Count')
> E+where > =
> .read_attribute
> E+and
> 'org.apache.cassandra.metrics:type=Storage,name=TotalHints' =
> make_mbean('metrics', type='Storage', name='TotalHints')
> write_failures_test.py:277: AssertionError
> REST API
> CloudBees CI Client Controller 2.319.3.4-rolling
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531144#comment-17531144
]
Michael Semb Wever commented on CASSANDRA-17589:
Both cassandra-builds PRs tested on local jenkins.
> Create release branch cassandra-4.1
> ---
>
> Key: CASSANDRA-17589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17589
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.1 trunk
> git push --set-upstream origin cassandra-4.1
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.2
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> 3. Add `4.1.x` to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 4.x to 4.1.x)
> 4. Update docker images to include cassandra-4.1
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17558) Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser accounts
[
https://issues.apache.org/jira/browse/CASSANDRA-17558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531131#comment-17531131
]
Andres de la Peña commented on CASSANDRA-17558:
---
I'd do the rename of the property before releasing 4.1, so we don't have to
deprecate it immediately after it's introduction.
If we want to keep a single guardrail for {{DROP}} and {{TRUNCATE}} instead of
separate guardrails, I'd go with {{drop_truncate_table_enabled}} or
{{{}drop_or_truncate_table_enabled{}}}, starting with {{{}drop_{}}}. That way
it can be more easily associated to the future {{{}drop_keyspace_enabled{}}},
since I guess that it will be common for users to use the same value for both
guardrails.
> Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser
> accounts
>
>
> Key: CASSANDRA-17558
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17558
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.1
>
>
> While this can also be accomplished via roles, there's value in having a
> cluster-wide "all role ban" on specific operations that operators can
> configure for clusters that have need of those settings.
> In this case, we want the ability to completely disallow DROP or TRUNCATE
> TABLE commands so users cannot inadvertently throw away data and operators
> don't have to runbook managing roles to ensure that this functionality
> doesn't leak through.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531127#comment-17531127
]
Michael Semb Wever commented on CASSANDRA-17589:
CI
- python dtest-upgrade:
https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest-upgrade/1003/
- python dtest (shows failures in trunk are fixed):
https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest/1364/
> Create release branch cassandra-4.1
> ---
>
> Key: CASSANDRA-17589
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17589
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0, 4.x
>
>
> Figure out what needs to be done beyond the following…
> 1. Create release branch
> {code}
> git switch -c cassandra-4.1 trunk
> git push --set-upstream origin cassandra-4.1
> {code}
> 2. Bump trunk's version
> {code}
> git switch trunk
> # increment version to 4.2
> edit build.xml debian/changelog CHANGES.txt NEWS.txt
> {code}
> 2a. Update jvm-dtest supported upgrade paths
> -
> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L85-L96
>
> 3. Add `4.1.x` to jira versions
> (no existing tickets will be changed - assignees need to change appropriate
> bugs from 4.x to 4.1.x)
> 4. Update docker images to include cassandra-4.1
> (Docker images also need to be deployed)
> 5. Add pipeline to ci-cassandra
> https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L51
> 6. Add dtest version and upgrade paths
> -
> https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py
> - https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml#L2374
> -
> https://github.com/apache/cassandra-builds/blob/trunk/build-scripts/cassandra-test.sh#L41
> 7. Update how_to_commit documentation
> https://github.com/apache/cassandra/blob/trunk/doc/source/development/how_to_commit.rst
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
