[jira] [Commented] (CASSANDRA-17596) Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build
[ https://issues.apache.org/jira/browse/CASSANDRA-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532069#comment-17532069 ] Berenguer Blasi commented on CASSANDRA-17596: - LGTM at face value as a null start/end does make much sense imo. But I'd wait for sbdy else with more knowledge in that area to confirm. Also we'd need CI runs for the other branches before the merge imo. #my2cts :-) > Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build > > > Key: CASSANDRA-17596 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17596 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.1, 4.0.5, 4.x > > > These two arrays are not initialised (1) which means that if I do not set > start nor end, when ClusteringBound.create is called, it will be null, but it > will fail here (2) as values will be null. > The fix consists of check if values are null and if they are, we build that > bound immediately. > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SimpleBuilders.java#L257-L258 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/ClusteringBound.java#L128 -- 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-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:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-17581:
Reviewers: Berenguer Blasi
> 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: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.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] [Comment Edited] (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=17531860#comment-17531860
]
Brandon Williams edited comment on CASSANDRA-17581 at 5/5/22 2:57 AM:
--
That solution works for me! I've added a test for both ipv4 and ipv6 hosts
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17581] and have
rebased Jermy's patch to run against it:
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1673/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1673/pipeline]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.11]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1674/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1674/pipeline]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1679/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1679/pipeline]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.1]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1676/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1676/pipeline]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-trunk]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1678/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1678/pipeline]|
was (Author: brandon.williams):
That solution works for me! I've added a test for both ipv4 and ipv6 hosts
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17581] and have
rebased Jermy's patch to run against it:
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1673/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1673/pipeline]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.11]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1674/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1674/pipeline]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1675/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1675/pipeline]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.1]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1676/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1676/pipeline]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-trunk]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1677/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1677/pipeline]|
> 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: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.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
[jira] [Comment Edited] (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=17531860#comment-17531860
]
Brandon Williams edited comment on CASSANDRA-17581 at 5/5/22 1:17 AM:
--
That solution works for me! I've added a test for both ipv4 and ipv6 hosts
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17581] and have
rebased Jermy's patch to run against it:
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1673/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1673/pipeline]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.11]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1674/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1674/pipeline]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1675/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1675/pipeline]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.1]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1676/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1676/pipeline]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-trunk]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1677/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1677/pipeline]|
was (Author: brandon.williams):
That solution works for me! I've added a test for both ipv4 and ipv6 hosts
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17581] and have
rebased Jermy's patch to run against it:
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1658/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1658/pipeline]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.11]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1659/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1659/pipeline]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1663/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1663/pipeline]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.1]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1666/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1666/pipeline]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-trunk]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1672/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1672/pipeline]|
> 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: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.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
[jira] [Updated] (CASSANDRA-17601) IllegalStateException with prepared queries selecting static columns in mixed 3.0.x/4.x clusters
[
https://issues.apache.org/jira/browse/CASSANDRA-17601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Meredith updated CASSANDRA-17601:
-
Bug Category: Parent values: Degradation(12984)Level 1 values: Other
Exception(12998)
Complexity: Challenging
Component/s: Cluster/Gossip
Consistency/Coordination
Discovered By: User Report
Fix Version/s: 4.0.x
4.1.x
4.x
Severity: Normal
Status: Open (was: Triage Needed)
> IllegalStateException with prepared queries selecting static columns in mixed
> 3.0.x/4.x clusters
>
>
> Key: CASSANDRA-17601
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17601
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip, Consistency/Coordination
>Reporter: Jon Meredith
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> Clusters that contain prepared statements that partially select static
> columns before the upgrade will fail to execute those statements coordinated
> from the 4.x nodes until the upgrade completes.
> h2. Reproduction
> Setup (before upgrade)
> {code:java}
> CREATE KEYSPACE ks1 WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor':3}
> CREATE TABLE ks1.tbl1 (pk1 int,
> ck2 int,
> s3 int static,
> s4 int static,
> c5 int,
> PRIMARY KEY (pk1, ck2));
> INSERT INTO ks1.tbl1 (pk1, ck2, s3, s4, c5) VALUES (1, 2, 3, 4, 5);
> {code}
> Prepared Statement (prepare before upgrade)
> {code:java}
> SELECT c5, s3 FROM ks1.tbl1 WHERE pk1 = ? AND ck2 = ?;
> {code}
> Exception on 3.0.x nodes (when executing prepared statement after upgrade)
> {code:java}
> java.lang.IllegalStateException: [s3, s4] is not a subset of [s3] at
> org.apache.cassandra.db.Columns$Serializer.encodeBitmap(Columns.java:566)
> at
> org.apache.cassandra.db.Columns$Serializer.serializeSubset(Columns.java:498)
> at
> org.apache.cassandra.db.rows.UnfilteredSerializer.serializeRowBody(UnfilteredSerializer.java:235)
> at
> org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:209)
> at
> org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:141)
> at
> org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:129)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:140)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:95)
> at
> org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:80)
> at
> org.apache.cassandra.db.partitions.UnfilteredPartitionIterators$Serializer.serialize(UnfilteredPartitionIterators.java:308)
> at
> org.apache.cassandra.db.ReadResponse$LocalDataResponse.build(ReadResponse.java:191)
> at
> org.apache.cassandra.db.ReadResponse$LocalDataResponse.(ReadResponse.java:181)
> at
> org.apache.cassandra.db.ReadResponse$LocalDataResponse.(ReadResponse.java:177)
> at
> org.apache.cassandra.db.ReadResponse.createDataResponse(ReadResponse.java:48)
> at org.apache.cassandra.db.ReadCommand.createResponse(ReadCommand.java:335)
> at
> org.apache.cassandra.db.ReadCommandVerbHandler.doVerb(ReadCommandVerbHandler.java:91)
> at org.apache.cassandra.net.InboundSink.lambda$new$0(InboundSink.java:77)
> at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:93)
> at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:44)
> at
> org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:433)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
> at
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:134)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
> Exception on 4.0.x nodes (when executing prepared statement after upgrade)
> {code:java}
> java.lang.IllegalStateException: [ColumnDefinition{name=s3,
> type=org.apache.cassandra.db.marshal.IntType, kind=STATIC, position=-1},
> ColumnDefinition{name=s4, type=org.apache.cassandra.db.marshal.IntType,
> kind=STATIC, position=-1}] is not a subset of [s3]
> at org.apache.cassandra.db.Columns$Serializer.encodeBitmap(Columns.java:555)
> at
>
[jira] [Created] (CASSANDRA-17601) IllegalStateException with prepared queries selecting static columns in mixed 3.0.x/4.x clusters
Jon Meredith created CASSANDRA-17601:
Summary: IllegalStateException with prepared queries selecting
static columns in mixed 3.0.x/4.x clusters
Key: CASSANDRA-17601
URL: https://issues.apache.org/jira/browse/CASSANDRA-17601
Project: Cassandra
Issue Type: Bug
Reporter: Jon Meredith
Assignee: Jon Meredith
Clusters that contain prepared statements that partially select static columns
before the upgrade will fail to execute those statements coordinated from the
4.x nodes until the upgrade completes.
h2. Reproduction
Setup (before upgrade)
{code:java}
CREATE KEYSPACE ks1 WITH replication = {'class': 'SimpleStrategy',
'replication_factor':3}
CREATE TABLE ks1.tbl1 (pk1 int,
ck2 int,
s3 int static,
s4 int static,
c5 int,
PRIMARY KEY (pk1, ck2));
INSERT INTO ks1.tbl1 (pk1, ck2, s3, s4, c5) VALUES (1, 2, 3, 4, 5);
{code}
Prepared Statement (prepare before upgrade)
{code:java}
SELECT c5, s3 FROM ks1.tbl1 WHERE pk1 = ? AND ck2 = ?;
{code}
Exception on 3.0.x nodes (when executing prepared statement after upgrade)
{code:java}
java.lang.IllegalStateException: [s3, s4] is not a subset of [s3] at
org.apache.cassandra.db.Columns$Serializer.encodeBitmap(Columns.java:566)
at org.apache.cassandra.db.Columns$Serializer.serializeSubset(Columns.java:498)
at
org.apache.cassandra.db.rows.UnfilteredSerializer.serializeRowBody(UnfilteredSerializer.java:235)
at
org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:209)
at
org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:141)
at
org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:129)
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:140)
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:95)
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:80)
at
org.apache.cassandra.db.partitions.UnfilteredPartitionIterators$Serializer.serialize(UnfilteredPartitionIterators.java:308)
at
org.apache.cassandra.db.ReadResponse$LocalDataResponse.build(ReadResponse.java:191)
at
org.apache.cassandra.db.ReadResponse$LocalDataResponse.(ReadResponse.java:181)
at
org.apache.cassandra.db.ReadResponse$LocalDataResponse.(ReadResponse.java:177)
at org.apache.cassandra.db.ReadResponse.createDataResponse(ReadResponse.java:48)
at org.apache.cassandra.db.ReadCommand.createResponse(ReadCommand.java:335)
at
org.apache.cassandra.db.ReadCommandVerbHandler.doVerb(ReadCommandVerbHandler.java:91)
at org.apache.cassandra.net.InboundSink.lambda$new$0(InboundSink.java:77)
at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:93)
at org.apache.cassandra.net.InboundSink.accept(InboundSink.java:44)
at
org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:433)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
at
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:134)
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
Exception on 4.0.x nodes (when executing prepared statement after upgrade)
{code:java}
java.lang.IllegalStateException: [ColumnDefinition{name=s3,
type=org.apache.cassandra.db.marshal.IntType, kind=STATIC, position=-1},
ColumnDefinition{name=s4, type=org.apache.cassandra.db.marshal.IntType,
kind=STATIC, position=-1}] is not a subset of [s3]
at org.apache.cassandra.db.Columns$Serializer.encodeBitmap(Columns.java:555)
at org.apache.cassandra.db.Columns$Serializer.serializeSubset(Columns.java:487)
at
org.apache.cassandra.db.rows.UnfilteredSerializer.serializeRowBody(UnfilteredSerializer.java:216)
at
org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:190)
at
org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:121)
at
org.apache.cassandra.db.rows.UnfilteredSerializer.serialize(UnfilteredSerializer.java:109)
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:140)
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:94)
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:79)
at
[cassandra-website] branch asf-staging updated (76f886cf2 -> 8adce8e7a)
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 76f886cf2 generate docs for c630db6b new 8adce8e7a 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 (76f886cf2) \ N -- N -- N refs/heads/asf-staging (8adce8e7a) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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=17531976#comment-17531976 ] David Capwell commented on CASSANDRA-17563: --- moved the script to CASSANDRA-17600 > 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-17600) CircleCI should rely on well known behavior rather than manual patch files
[ https://issues.apache.org/jira/browse/CASSANDRA-17600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17600: -- Test and Documentation Plan: ran ci Status: Patch Available (was: Open) > CircleCI should rely on well known behavior rather than manual patch files > -- > > Key: CASSANDRA-17600 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17600 > Project: Cassandra > Issue Type: Improvement > Components: CI >Reporter: David Capwell >Assignee: David Capwell >Priority: Low > Fix For: NA > > > This started in CASSANDRA-17563 > It is way too easy to break our MIDRES/HIGHER configurations as they relies > on manual patch generations. To avoid this, we should have a new script > control these files that is aware of jobs and able to update resources needed -- 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-17600) CircleCI should rely on well known behavior rather than manual patch files
[ https://issues.apache.org/jira/browse/CASSANDRA-17600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17600: -- Change Category: Code Clarity Complexity: Low Hanging Fruit Fix Version/s: NA Priority: Low (was: Normal) Status: Open (was: Triage Needed) > CircleCI should rely on well known behavior rather than manual patch files > -- > > Key: CASSANDRA-17600 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17600 > Project: Cassandra > Issue Type: Improvement > Components: CI >Reporter: David Capwell >Assignee: David Capwell >Priority: Low > Fix For: NA > > > This started in CASSANDRA-17563 > It is way too easy to break our MIDRES/HIGHER configurations as they relies > on manual patch generations. To avoid this, we should have a new script > control these files that is aware of jobs and able to update resources needed -- 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-17600) CircleCI should rely on well known behavior rather than manual patch files
David Capwell created CASSANDRA-17600: - Summary: CircleCI should rely on well known behavior rather than manual patch files Key: CASSANDRA-17600 URL: https://issues.apache.org/jira/browse/CASSANDRA-17600 Project: Cassandra Issue Type: Improvement Components: CI Reporter: David Capwell Assignee: David Capwell This started in CASSANDRA-17563 It is way too easy to break our MIDRES/HIGHER configurations as they relies on manual patch generations. To avoid this, we should have a new script control these files that is aware of jobs and able to update resources needed -- 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-17579) WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" + Liquibase case study
[ https://issues.apache.org/jira/browse/CASSANDRA-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17579: - Epic Link: (was: CASSANDRA-16761) > WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" > + Liquibase case study > > > Key: CASSANDRA-17579 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17579 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > Attachments: c17579-01-blog-index.png, c17579-02-blog-post.png, > c17579-03-case_studies-index.png, c17579-04-case_study.png > > > This ticket is to capture the work associated with publishing the April 2022 > blog "Liquibase is Ready to Support Cassandra 4.0 Users" and adding the > Liquidbase case study to the website. > If this blog + case study cannot be published by the *April 28, 2022 publish > date*, please contact me, suggest changes, or correct the date when possible > in the pull request for the appropriate time that the blog will go live (on > both the blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.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:
--
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra-dtest/commit/be48c417e6bbbd7c58f43ed001c9a2209a6339ab
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> 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: 40m
> 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
[cassandra-dtest] branch trunk updated: Fix flaky python-tests due to connection getting closed Patch by David Capwell; reviewed by Caleb Rackliffe for CASSANDRA-17594
This is an automated email from the ASF dual-hosted git repository.
dcapwell 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 be48c417 Fix flaky python-tests due to connection getting closed Patch
by David Capwell; reviewed by Caleb Rackliffe for CASSANDRA-17594
be48c417 is described below
commit be48c417e6bbbd7c58f43ed001c9a2209a6339ab
Author: David Capwell
AuthorDate: Tue May 3 11:49:14 2022 -0700
Fix flaky python-tests due to connection getting closed
Patch by David Capwell; reviewed by Caleb Rackliffe for CASSANDRA-17594
---
conftest.py | 12 +---
dtest_setup.py | 28
repair_tests/repair_test.py | 3 ++-
topology_test.py| 2 +-
4 files changed, 32 insertions(+), 13 deletions(-)
diff --git a/conftest.py b/conftest.py
index 347c6965..19c30832 100644
--- a/conftest.py
+++ b/conftest.py
@@ -219,15 +219,16 @@ def fixture_log_test_name_and_date(request,
fixture_logging_setup):
def _filter_errors(dtest_setup, errors):
"""Filter errors, removing those that match ignore_log_patterns in the
current DTestSetup"""
for e in errors:
+e = repr(e)
for pattern in dtest_setup.ignore_log_patterns:
-if re.search(pattern, repr(e)):
+if re.search(pattern, e) or re.search(pattern, e.replace('\n', '
')):
break
else:
yield e
def check_logs_for_errors(dtest_setup):
-errors = []
+all_errors = []
for node in dtest_setup.cluster.nodelist():
if not os.path.exists(node.logfilename()):
continue
@@ -240,11 +241,8 @@ def check_logs_for_errors(dtest_setup):
error_str = error.strip()
if error_str:
-logger.error("Unexpected error in {node_name} log, error:
\n{error}"
- .format(node_name=node.name, error=error_str))
-errors.append(error_str)
-break
-return errors
+all_errors.append("[{node_name}]
{error}".format(node_name=node.name, error=error_str))
+return all_errors
def copy_logs(request, cluster, directory=None, name=None):
diff --git a/dtest_setup.py b/dtest_setup.py
index d04fb001..6a396b8e 100644
--- a/dtest_setup.py
+++ b/dtest_setup.py
@@ -44,13 +44,18 @@ def retry_till_success(fun, *args, **kwargs):
# brief pause before next attempt
time.sleep(0.25)
+def default_ignore_log_patterns():
+# to allow tests to append to the list, make sure to create a new list as
the output
+# to this function, else multiple tests could corrupt the default set
+return ['.*\[epollEventLoopGroup-.*\].*- Unknown exception in client
networking.*: Connection reset by peer']
+
class DTestSetup(object):
def __init__(self, dtest_config=None, setup_overrides=None,
cluster_name="test"):
self.dtest_config = dtest_config
self.setup_overrides = setup_overrides
self.cluster_name = cluster_name
-self.ignore_log_patterns = []
+self._ignore_log_patterns = default_ignore_log_patterns()
self.cluster = None
self.cluster_options = []
self.replacement_node = None
@@ -72,6 +77,23 @@ class DTestSetup(object):
self.create_cluster_func = None
self.iterations = 0
+def set_ignore_log_patterns(self, other):
+if self._ignore_log_patterns == None:
+self._ignore_log_patterns = default_ignore_log_patterns()
+# iteration is used here to allow [] and () patterns to work...
anything iterable is allowed
+for a in other:
+self._ignore_log_patterns.append(a)
+
+def get_ignore_log_patterns(self):
+if self._ignore_log_patterns == None:
+self._ignore_log_patterns = default_ignore_log_patterns()
+return self._ignore_log_patterns
+
+def del_ignore_log_patterns(self):
+del self._ignore_log_patterns
+
+ignore_log_patterns = property(get_ignore_log_patterns,
set_ignore_log_patterns, del_ignore_log_patterns)
+
def get_test_path(self):
test_path = tempfile.mkdtemp(prefix='dtest-')
@@ -289,11 +311,9 @@ class DTestSetup(object):
def __filter_errors(self, errors):
"""Filter errors, removing those that match self.ignore_log_patterns"""
-if not hasattr(self, 'ignore_log_patterns'):
-self.ignore_log_patterns = []
for e in errors:
for pattern in self.ignore_log_patterns:
-if re.search(pattern, e):
+if re.search(pattern, e) or re.search(pattern, e.replace('\n',
' ')):
break
else:
yield e
diff --git a/repair_tests/repair_test.py b/repair_tests/repair_test.py
index 17e124a3..af536a76
[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:
--
Status: Ready to Commit (was: Review 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: 0.5h
> 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-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=17531948#comment-17531948
]
Caleb Rackliffe commented on CASSANDRA-17594:
-
+1
> 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: 0.5h
> 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
[cassandra-website] branch asf-staging updated (2e6a6690f -> 76f886cf2)
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 2e6a6690f generate docs for c630db6b new 76f886cf2 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 (2e6a6690f) \ N -- N -- N refs/heads/asf-staging (76f886cf2) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17596) Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build
[ https://issues.apache.org/jira/browse/CASSANDRA-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17596: -- Fix Version/s: 4.1 4.0.5 (was: 4.0.x) (was: 4.1.x) > Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build > > > Key: CASSANDRA-17596 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17596 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.1, 4.0.5, 4.x > > > These two arrays are not initialised (1) which means that if I do not set > start nor end, when ClusteringBound.create is called, it will be null, but it > will fail here (2) as values will be null. > The fix consists of check if values are null and if they are, we build that > bound immediately. > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SimpleBuilders.java#L257-L258 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/ClusteringBound.java#L128 -- 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=17531920#comment-17531920
]
David Capwell commented on CASSANDRA-17594:
---
To be more clear, this is the bug with conftest.py
* error is non-empty, so we validate its not "" and re-add to errors array
* we then "break" but this doesn't take us out of the top loop, but just the
inner loop; if error is size 2, we only look at the first error
* we *override* error with next node, which has 0 errors
* we see errors is empty, so mark test success
so I will fix this, just need to update each test to include the new errors
being detected
> 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: 0.5h
> 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-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531916#comment-17531916
]
Michael Semb Wever commented on CASSANDRA-17589:
wrt (7) that [doc
page|https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst]
got moved to the
[cassandra-website|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc]
repo, and new edits were not carried over. Fixing this deserves a new ticket:
CASSANDRA-17599
> 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] [Created] (CASSANDRA-17599) Update how_to_commit documentation with lost updates from in-tree repo
Michael Semb Wever created CASSANDRA-17599: -- Summary: Update how_to_commit documentation with lost updates from in-tree repo Key: CASSANDRA-17599 URL: https://issues.apache.org/jira/browse/CASSANDRA-17599 Project: Cassandra Issue Type: Task Components: Documentation Reporter: Michael Semb Wever When the [how_to_commit.rst|https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst] page got migrated and moved to the [cassandra-website|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc] repo, new edits were not carried over. cassandra-website/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc needs to be updated so it reads like https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst It should also be updated to include latest release branches (ref: CASSANDRA-17589 ) -- 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-17599) Update how_to_commit documentation with lost updates from in-tree repo
[ https://issues.apache.org/jira/browse/CASSANDRA-17599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-17599: --- Change Category: Semantic Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Update how_to_commit documentation with lost updates from in-tree repo > -- > > Key: CASSANDRA-17599 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17599 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Michael Semb Wever >Priority: Normal > > When the > [how_to_commit.rst|https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst] > page got migrated and moved to the > [cassandra-website|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc] > repo, new edits were not carried over. > cassandra-website/site-content/source/modules/ROOT/pages/development/how_to_commit.adoc > > needs to be updated so it reads like > https://github.com/apache/cassandra/blob/1fce84f9833bd62227dbf8f5d063935457dbc18e/doc/source/development/how_to_commit.rst > It should also be updated to include latest release branches (ref: > CASSANDRA-17589 ) -- 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-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=17531860#comment-17531860
]
Brandon Williams edited comment on CASSANDRA-17581 at 5/4/22 7:28 PM:
--
That solution works for me! I've added a test for both ipv4 and ipv6 hosts
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17581] and have
rebased Jermy's patch to run against it:
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1658/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1658/pipeline]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.11]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1659/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1659/pipeline]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1663/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1663/pipeline]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.1]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1666/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1666/pipeline]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-trunk]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1672/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1672/pipeline]|
was (Author: brandon.williams):
That solution works for me! I've added a test for both ipv4 and ipv6 hosts
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17581] and have
rebased Jermy's patch to run against it:
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1658/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1658/pipeline]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.11]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1659/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1659/pipeline]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1663/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1663/pipeline]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.1]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1666/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1666/pipeline]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-trunk]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1667/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1667/pipeline]|
> 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: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.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
[jira] [Comment Edited] (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=17531860#comment-17531860
]
Brandon Williams edited comment on CASSANDRA-17581 at 5/4/22 7:09 PM:
--
That solution works for me! I've added a test for both ipv4 and ipv6 hosts
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17581] and have
rebased Jermy's patch to run against it:
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1658/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1658/pipeline]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.11]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1659/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1659/pipeline]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1663/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1663/pipeline]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.1]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1666/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1666/pipeline]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-trunk]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1667/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1667/pipeline]|
was (Author: brandon.williams):
That solution works for me! I've added a test for both ipv4 and ipv6 hosts
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17581] and have
rebased Jermy's patch to run against it:
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1658/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1658/pipeline]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.11]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1659/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1659/pipeline]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1660/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1660/pipeline]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.1]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1661/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1661/pipeline]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-trunk]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1662/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1662/pipeline]|
> 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: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.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
[jira] [Comment Edited] (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=17531887#comment-17531887
]
David Capwell edited comment on CASSANDRA-17594 at 5/4/22 6:40 PM:
---
fun, if I revert conftest.py I see it logs that there were errors in the log,
but the test is marked as success... so by fixing conftest.py I now cause the
tests to fail !
yay?
{code}
18:39:33,839 repair_tests.repair_test DEBUG Killed node3, now waiting repair to
finish
PASSED
[100%]
--
live log teardown
---
18:39:33,859 conftest ERROR Unexpected error in node1 log, error:
'ERROR [Repair#1:1] 2022-05-04 18:39:20,930 JVMStabilityInspector.java:68 -
Exception in thread
Thread[Repair#1:1,5,Repair#1]\norg.apache.cassandra.repair.SomeRepairFailedException:
null'
--
generated xml file: /parallel-ci/output/pytest_result.xml
---
==
1 passed in 87.70 seconds
===
bash-4.2$
{code}
was (Author: dcapwell):
fun, if I revert conftest.py I see it logs that there were errors in the log,
but the test is marked as success... so by fixing conftest.py I now cause the
tests to fail !
yay?
> 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: 0.5h
> 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-17598) WEBSITE - May 2022 blog "Apache Cassandra Changelog #15"
[ https://issues.apache.org/jira/browse/CASSANDRA-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17598: - Source Control Link: https://github.com/apache/cassandra-website/pull/127/commits/94fc8ffd54ebf67a187f330d7b436ae3e7bd9e6d > WEBSITE - May 2022 blog "Apache Cassandra Changelog #15" > > > Key: CASSANDRA-17598 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17598 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > > This ticket is to capture the work associated with publishing the May 2022 > blog "Apache Cassandra Changelog #15" > If this blog cannot be published by the *May 5, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17598) WEBSITE - May 2022 blog "Apache Cassandra Changelog #15"
[ https://issues.apache.org/jira/browse/CASSANDRA-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17598: - Status: Patch Available (was: Open) > WEBSITE - May 2022 blog "Apache Cassandra Changelog #15" > > > Key: CASSANDRA-17598 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17598 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > > This ticket is to capture the work associated with publishing the May 2022 > blog "Apache Cassandra Changelog #15" > If this blog cannot be published by the *May 5, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17598) WEBSITE - May 2022 blog "Apache Cassandra Changelog #15"
[ https://issues.apache.org/jira/browse/CASSANDRA-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17598: - Status: Open (was: Triage Needed) https://github.com/apache/cassandra-website/pull/127 > WEBSITE - May 2022 blog "Apache Cassandra Changelog #15" > > > Key: CASSANDRA-17598 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17598 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > > This ticket is to capture the work associated with publishing the May 2022 > blog "Apache Cassandra Changelog #15" > If this blog cannot be published by the *May 5, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.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=17531887#comment-17531887
]
David Capwell commented on CASSANDRA-17594:
---
fun, if I revert conftest.py I see it logs that there were errors in the log,
but the test is marked as success... so by fixing conftest.py I now cause the
tests to fail !
yay?
> 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: 0.5h
> 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-17598) WEBSITE - May 2022 blog "Apache Cassandra Changelog #15"
[ https://issues.apache.org/jira/browse/CASSANDRA-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-17598: --- Labels: pull-request-available (was: ) > WEBSITE - May 2022 blog "Apache Cassandra Changelog #15" > > > Key: CASSANDRA-17598 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17598 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > > This ticket is to capture the work associated with publishing the May 2022 > blog "Apache Cassandra Changelog #15" > If this blog cannot be published by the *May 5, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (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:all-tabpanel
]
Brandon Williams updated CASSANDRA-17581:
-
Severity: Critical (was: Normal)
> 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: Urgent
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.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] [Updated] (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:all-tabpanel
]
Brandon Williams updated CASSANDRA-17581:
-
Fix Version/s: 4.1.x
> 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.1.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-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=17531860#comment-17531860
]
Brandon Williams commented on CASSANDRA-17581:
--
That solution works for me! I've added a test for both ipv4 and ipv6 hosts
[here|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17581] and have
rebased Jermy's patch to run against it:
||Branch||CI||
|[3.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1658/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1658/pipeline]|
|[3.11|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-3.11]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1659/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1659/pipeline]|
|[4.0|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.0]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1660/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1660/pipeline]|
|[4.1|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-4.1]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1661/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1661/pipeline]|
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-17581-trunk]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1662/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/1662/pipeline]|
> 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
>
[cassandra] branch CASSANDRA-17581-3.0 deleted (was 68f1936ee2)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch CASSANDRA-17581-3.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git was 68f1936ee2 add elegant solution that is compatible with ipv4 and ipv6 This change permanently discards the following revisions: discard 68f1936ee2 add elegant solution that is compatible with ipv4 and ipv6 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch CASSANDRA-17581-4.0 deleted (was 997b9a557e)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch CASSANDRA-17581-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git was 997b9a557e Merge branch 'CASSANDRA-17581-3.11' into CASSANDRA-17581-4.0 This change permanently discards the following revisions: discard 997b9a557e Merge branch 'CASSANDRA-17581-3.11' into CASSANDRA-17581-4.0 discard fd70b7b00f Merge branch 'CASSANDRA-17581-3.0' into CASSANDRA-17581-3.11 discard 68f1936ee2 add elegant solution that is compatible with ipv4 and ipv6 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch CASSANDRA-17581-3.11 deleted (was fd70b7b00f)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch CASSANDRA-17581-3.11 in repository https://gitbox.apache.org/repos/asf/cassandra.git was fd70b7b00f Merge branch 'CASSANDRA-17581-3.0' into CASSANDRA-17581-3.11 This change permanently discards the following revisions: discard fd70b7b00f Merge branch 'CASSANDRA-17581-3.0' into CASSANDRA-17581-3.11 discard 68f1936ee2 add elegant solution that is compatible with ipv4 and ipv6 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17596) Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build
[ https://issues.apache.org/jira/browse/CASSANDRA-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531837#comment-17531837 ] Stefan Miklosovic commented on CASSANDRA-17596: --- [~bdeggleston] would you mind to take a look? Jenkins CI is way nicer. > Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build > > > Key: CASSANDRA-17596 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17596 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > These two arrays are not initialised (1) which means that if I do not set > start nor end, when ClusteringBound.create is called, it will be null, but it > will fail here (2) as values will be null. > The fix consists of check if values are null and if they are, we build that > bound immediately. > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SimpleBuilders.java#L257-L258 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/ClusteringBound.java#L128 -- 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-17596) Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build
[ https://issues.apache.org/jira/browse/CASSANDRA-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531835#comment-17531835 ] Stefan Miklosovic commented on CASSANDRA-17596: --- 4.0 https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1657/ > Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build > > > Key: CASSANDRA-17596 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17596 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > These two arrays are not initialised (1) which means that if I do not set > start nor end, when ClusteringBound.create is called, it will be null, but it > will fail here (2) as values will be null. > The fix consists of check if values are null and if they are, we build that > bound immediately. > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SimpleBuilders.java#L257-L258 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/ClusteringBound.java#L128 -- 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:
--
Fix Version/s: 4.1
(was: 4.1.x)
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/559b17f71d3207158d34b1dd2414a531e362af20
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> 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
>
>
> 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
[cassandra] branch trunk updated (6c20fbca4a -> 0541e5b078)
This is an automated email from the ASF dual-hosted git repository. dcapwell pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 6c20fbca4a Merge branch 'cassandra-4.1' into trunk new 559b17f71d nodetool enablefullquerylog can NPE when directory has no files new 0541e5b078 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: CHANGES.txt| 2 ++ src/java/org/apache/cassandra/utils/binlog/BinLog.java | 6 -- 2 files changed, 6 insertions(+), 2 deletions(-) - 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: nodetool enablefullquerylog can NPE when directory has no files
This is an automated email from the ASF dual-hosted git repository.
dcapwell 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 559b17f71d nodetool enablefullquerylog can NPE when directory has no
files
559b17f71d is described below
commit 559b17f71d3207158d34b1dd2414a531e362af20
Author: David Capwell
AuthorDate: Tue May 3 14:59:55 2022 -0700
nodetool enablefullquerylog can NPE when directory has no files
patch by David Capwell; reviewed by Jon Meredith for CASSANDRA-17595
---
CHANGES.txt| 1 +
src/java/org/apache/cassandra/utils/binlog/BinLog.java | 6 --
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 050767a943..131b0c980d 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
4.1
+ * nodetool enablefullquerylog can NPE when directory has no files
(CASSANDRA-17595)
* Add auto_snapshot_ttl configuration (CASSANDRA-16790)
* List snapshots of dropped tables (CASSANDRA-16843)
* Add information whether sstables are dropped to SchemaChangeListener
(CASSANDRA-17582)
diff --git a/src/java/org/apache/cassandra/utils/binlog/BinLog.java
b/src/java/org/apache/cassandra/utils/binlog/BinLog.java
index a9bb55ac8d..e2ae1ec09b 100644
--- a/src/java/org/apache/cassandra/utils/binlog/BinLog.java
+++ b/src/java/org/apache/cassandra/utils/binlog/BinLog.java
@@ -486,9 +486,11 @@ public class BinLog implements Runnable
{
if (fileOrDirectory.isDirectory())
{
-for (File f : fileOrDirectory.tryList())
+File[] files = fileOrDirectory.tryList();
+if (files != null)
{
-accumulate = FileUtils.deleteWithConfirm(f, accumulate);
+for (File f : files)
+accumulate = FileUtils.deleteWithConfirm(f, accumulate);
}
}
return FileUtils.deleteWithConfirm(fileOrDirectory, accumulate);
-
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. dcapwell pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 0541e5b078a2fe6cb0199e72f1a735a6f565ef08 Merge: 6c20fbca4a 559b17f71d Author: David Capwell AuthorDate: Wed May 4 09:32:42 2022 -0700 Merge branch 'cassandra-4.1' into trunk CHANGES.txt| 2 ++ src/java/org/apache/cassandra/utils/binlog/BinLog.java | 6 -- 2 files changed, 6 insertions(+), 2 deletions(-) diff --cc CHANGES.txt index dc7f81eec7,131b0c980d..4e1d7da018 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,10 -1,5 +1,12 @@@ -4.1 +4.2 ++Merged from 4.1: + * nodetool enablefullquerylog can NPE when directory has no files (CASSANDRA-17595) +Merged from 4.0: +Merged from 3.11: +Merged from 3.0: + + +4.1 * Add auto_snapshot_ttl configuration (CASSANDRA-16790) * List snapshots of dropped tables (CASSANDRA-16843) * Add information whether sstables are dropped to SchemaChangeListener (CASSANDRA-17582) - 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=17531822#comment-17531822
]
David Capwell commented on CASSANDRA-17595:
---
a few python-dtest tests failed to bind, but they passed under the other
configs...
> 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-17598) WEBSITE - May 2022 blog "Apache Cassandra Changelog #15"
[ https://issues.apache.org/jira/browse/CASSANDRA-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17598: - Authors: Chris Thornett Change Category: Semantic Complexity: Normal Fix Version/s: 4.0.x Impacts: Docs (was: None) Test and Documentation Plan: * Add blog post titled "Apache Cassandra Changelog #15" * Modify blog index page * Add image for blog: "ApacheCon2022banner.png" > WEBSITE - May 2022 blog "Apache Cassandra Changelog #15" > > > Key: CASSANDRA-17598 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17598 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Fix For: 4.0.x > > > This ticket is to capture the work associated with publishing the May 2022 > blog "Apache Cassandra Changelog #15" > If this blog cannot be published by the *May 5, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17598) WEBSITE - May 2022 blog "Apache Cassandra Changelog #15"
Diogenese Topper created CASSANDRA-17598: Summary: WEBSITE - May 2022 blog "Apache Cassandra Changelog #15" Key: CASSANDRA-17598 URL: https://issues.apache.org/jira/browse/CASSANDRA-17598 Project: Cassandra Issue Type: Task Components: Documentation/Blog Reporter: Diogenese Topper This ticket is to capture the work associated with publishing the May 2022 blog "Apache Cassandra Changelog #15" If this blog cannot be published by the *May 5, 2022 publish date*, please contact me, suggest changes, or correct the date when possible in the pull request for the appropriate time that the blog will go live (on both the blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-6936) Make all byte representations of types comparable by their unsigned byte representation only
[ https://issues.apache.org/jira/browse/CASSANDRA-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-6936: --- Reviewers: Benjamin Lerer, Caleb Rackliffe (was: Benjamin Lerer) > Make all byte representations of types comparable by their unsigned byte > representation only > > > Key: CASSANDRA-6936 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6936 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Core >Reporter: Benedict Elliott Smith >Assignee: Branimir Lambov >Priority: Normal > Labels: compaction, performance > Fix For: 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > This could be a painful change, but is necessary for implementing a > trie-based index, and settling for less would be suboptimal; it also should > make comparisons cheaper all-round, and since comparison operations are > pretty much the majority of C*'s business, this should be easily felt (see > CASSANDRA-6553 and CASSANDRA-6934 for an example of some minor changes with > major performance impacts). No copying/special casing/slicing should mean > fewer opportunities to introduce performance regressions as well. > Since I have slated for 3.0 a lot of non-backwards-compatible sstable > changes, hopefully this shouldn't be too much more of a burden. -- 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 ] Benjamin Lerer updated CASSANDRA-17563: --- Fix Version/s: 4.1 (was: 4.1.x) Since Version: 4.0 Source Control Link: https://github.com/apache/cassandra/commit/523d38095f6c7f33c602616db3a7373bbeb0cde9 Resolution: Fixed Status: Resolved (was: Ready to Commit) > 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 ] Benjamin Lerer updated CASSANDRA-17563: --- Status: Ready to Commit (was: Review In Progress) > 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-17579) WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" + Liquibase case study
[ https://issues.apache.org/jira/browse/CASSANDRA-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17579: - Epic Link: CASSANDRA-16761 > WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" > + Liquibase case study > > > Key: CASSANDRA-17579 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17579 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > Attachments: c17579-01-blog-index.png, c17579-02-blog-post.png, > c17579-03-case_studies-index.png, c17579-04-case_study.png > > > This ticket is to capture the work associated with publishing the April 2022 > blog "Liquibase is Ready to Support Cassandra 4.0 Users" and adding the > Liquidbase case study to the website. > If this blog + case study cannot be published by the *April 28, 2022 publish > date*, please contact me, suggest changes, or correct the date when possible > in the pull request for the appropriate time that the blog will go live (on > both the blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17580) Clients using JMX are unable to handle non-standard java types but we leak this into our Exceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-17580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531789#comment-17531789 ] Ekaterina Dimitrova commented on CASSANDRA-17580: - Marking 4.1.x as per [https://lists.apache.org/thread/wo3o86ntpg59r4fy2qhsh1j6fgntxf67,] confirmed with PMC > Clients using JMX are unable to handle non-standard java types but we leak > this into our Exceptions > --- > > Key: CASSANDRA-17580 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17580 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Observability, Observability/JMX >Reporter: David Capwell >Priority: Normal > Fix For: 4.1.x > > > This is an extension of CASSANDRA-17527. > When we throw in JMX the exception gets serialized and sent over the wire, > and if the client doesn’t have the same class path it fails and the exception > is lost and replaced with a ClassNotFoundException. This is bad as the user > has no idea what the issue is so unable to resolve it. -- 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-17580) Clients using JMX are unable to handle non-standard java types but we leak this into our Exceptions
[ https://issues.apache.org/jira/browse/CASSANDRA-17580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17580: Fix Version/s: 4.1.x (was: 4.1) > Clients using JMX are unable to handle non-standard java types but we leak > this into our Exceptions > --- > > Key: CASSANDRA-17580 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17580 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Observability, Observability/JMX >Reporter: David Capwell >Priority: Normal > Fix For: 4.1.x > > > This is an extension of CASSANDRA-17527. > When we throw in JMX the exception gets serialized and sent over the wire, > and if the client doesn’t have the same class path it fails and the exception > is lost and replaced with a ClassNotFoundException. This is bad as the user > has no idea what the issue is so unable to resolve it. -- 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=17531785#comment-17531785 ] Brandon Williams commented on CASSANDRA-16999: -- I don't think so. > 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] [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 ] Andres de la Peña updated CASSANDRA-17592: -- Reviewers: Aleksey Yeschenko, Andres de la Peña (was: Aleksey Yeschenko) > 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-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=17531776#comment-17531776
]
Andres de la Peña commented on CASSANDRA-17592:
---
Looks good to me. I'd also add the missed entry in [the list of guardrails in
{{NEWS.txt}}|https://github.com/apache/cassandra/blob/79343f194d5bd7a1a5df00b455d0c1f2646f2a00/NEWS.txt#L70-L90].
> 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-16761) New Cassandra Website and Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-16761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16761: --- Source Control Link: See tickets in epic for patch links. Resolution: Fixed Status: Resolved (was: Ready to Commit) > New Cassandra Website and Documentation > --- > > Key: CASSANDRA-16761 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16761 > Project: Cassandra > Issue Type: Epic > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > Fix For: 4.0.x > > > This epic captures the work associated with the development of the new > Cassandra website and documentation. > Work to create the new website and documentation will be broken up as follows: > * Proof of concept - CASSANDRA-16029 > * Website concept and design - CASSANDRA-16115 > * Develop tooling to render new website and documentation - CASSANDRA-16066 > * Create website content that will be rendered by new tooling - > CASSANDRA-16762 > * Create Cassandra documentation content that will be rendered by new > tooling - CASSANDRA-16763 > It is expected that the new website and documentation will be in asciidoc > format and rendered using Antora. > Antora is purpose built for rendering versioned documentation to HTML. In > addition it allows rendering customisations via Java Script which may be > useful when rending the website. -- 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-16761) New Cassandra Website and Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-16761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16761: --- Mentor: Michael Semb Wever Status: Review In Progress (was: Patch Available) > New Cassandra Website and Documentation > --- > > Key: CASSANDRA-16761 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16761 > Project: Cassandra > Issue Type: Epic > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > Fix For: 4.0.x > > > This epic captures the work associated with the development of the new > Cassandra website and documentation. > Work to create the new website and documentation will be broken up as follows: > * Proof of concept - CASSANDRA-16029 > * Website concept and design - CASSANDRA-16115 > * Develop tooling to render new website and documentation - CASSANDRA-16066 > * Create website content that will be rendered by new tooling - > CASSANDRA-16762 > * Create Cassandra documentation content that will be rendered by new > tooling - CASSANDRA-16763 > It is expected that the new website and documentation will be in asciidoc > format and rendered using Antora. > Antora is purpose built for rendering versioned documentation to HTML. In > addition it allows rendering customisations via Java Script which may be > useful when rending the website. -- 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-16761) New Cassandra Website and Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-16761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16761: --- Status: Ready to Commit (was: Review In Progress) > New Cassandra Website and Documentation > --- > > Key: CASSANDRA-16761 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16761 > Project: Cassandra > Issue Type: Epic > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > Fix For: 4.0.x > > > This epic captures the work associated with the development of the new > Cassandra website and documentation. > Work to create the new website and documentation will be broken up as follows: > * Proof of concept - CASSANDRA-16029 > * Website concept and design - CASSANDRA-16115 > * Develop tooling to render new website and documentation - CASSANDRA-16066 > * Create website content that will be rendered by new tooling - > CASSANDRA-16762 > * Create Cassandra documentation content that will be rendered by new > tooling - CASSANDRA-16763 > It is expected that the new website and documentation will be in asciidoc > format and rendered using Antora. > Antora is purpose built for rendering versioned documentation to HTML. In > addition it allows rendering customisations via Java Script which may be > useful when rending the website. -- 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-16761) New Cassandra Website and Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-16761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16761: --- Test and Documentation Plan: N/A. Tickets in epic are already tested and resolved. Status: Patch Available (was: In Progress) > New Cassandra Website and Documentation > --- > > Key: CASSANDRA-16761 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16761 > Project: Cassandra > Issue Type: Epic > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > Fix For: 4.0.x > > > This epic captures the work associated with the development of the new > Cassandra website and documentation. > Work to create the new website and documentation will be broken up as follows: > * Proof of concept - CASSANDRA-16029 > * Website concept and design - CASSANDRA-16115 > * Develop tooling to render new website and documentation - CASSANDRA-16066 > * Create website content that will be rendered by new tooling - > CASSANDRA-16762 > * Create Cassandra documentation content that will be rendered by new > tooling - CASSANDRA-16763 > It is expected that the new website and documentation will be in asciidoc > format and rendered using Antora. > Antora is purpose built for rendering versioned documentation to HTML. In > addition it allows rendering customisations via Java Script which may be > useful when rending the website. -- 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-17521) WEBSITE - April 2022 blog "Apache Cassandra Changelog #14"
[ https://issues.apache.org/jira/browse/CASSANDRA-17521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17521: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - April 2022 blog "Apache Cassandra Changelog #14" > -- > > Key: CASSANDRA-17521 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17521 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17521-01-blog-index.png, c17521-02-blog-post.png > > > This ticket is to capture the work associated with publishing the April 2022 > blog "Apache Cassandra Changelog #14" > If this blog cannot be published by the *April 7, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17579) WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" + Liquibase case study
[ https://issues.apache.org/jira/browse/CASSANDRA-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17579: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" > + Liquibase case study > > > Key: CASSANDRA-17579 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17579 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > Attachments: c17579-01-blog-index.png, c17579-02-blog-post.png, > c17579-03-case_studies-index.png, c17579-04-case_study.png > > > This ticket is to capture the work associated with publishing the April 2022 > blog "Liquibase is Ready to Support Cassandra 4.0 Users" and adding the > Liquidbase case study to the website. > If this blog + case study cannot be published by the *April 28, 2022 publish > date*, please contact me, suggest changes, or correct the date when possible > in the pull request for the appropriate time that the blog will go live (on > both the blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17511) WEBSITE - Kinetic Data case study and blog formatting edits
[ https://issues.apache.org/jira/browse/CASSANDRA-17511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17511: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Kinetic Data case study and blog formatting edits > --- > > Key: CASSANDRA-17511 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17511 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17511-01-blog-post.png, c17511-02-case_study.png > > > This ticket is to capture the work associated with addressing formatting > issues on the Kinetic Data case study and blog. -- 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-17555) WEBSITE - April 2022 blog "Inside Cassandra: An Interview with Project Contributor, Aleksandr Sorokoumov"
[ https://issues.apache.org/jira/browse/CASSANDRA-17555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17555: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - April 2022 blog "Inside Cassandra: An Interview with Project > Contributor, Aleksandr Sorokoumov" > - > > Key: CASSANDRA-17555 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17555 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17555-01-blog-index.png, c17555-02-blog-post.png > > > This ticket is to capture the work associated with publishing the April 2022 > blog "Inside Cassandra: An Interview with Project Contributor, Aleksandr > Sorokoumov" > If this blog cannot be published by the *April 14, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17497) WEBSITE - March 2022 blog "Kinetic Data chooses Apache Cassandra to deliver workflow automation solution"
[ https://issues.apache.org/jira/browse/CASSANDRA-17497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17497: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - March 2022 blog "Kinetic Data chooses Apache Cassandra to deliver > workflow automation solution" > - > > Key: CASSANDRA-17497 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17497 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17497-01-blog-index.png, c17497-02-blog-post.png > > > This ticket is to capture the work associated with publishing the March 2022 > blog "Kinetic Data chooses Apache Cassandra to deliver workflow automation > solution" > If this blog cannot be published by the *March 31, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17468) WEBSITE - Blog corrections and fixes, March 2022
[ https://issues.apache.org/jira/browse/CASSANDRA-17468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17468: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Blog corrections and fixes, March 2022 > > > Key: CASSANDRA-17468 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17468 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17468-01-blog-changelog_12.png, > c17468-02-blog-java_11_support.png, c17468-03-blog-behind_the_scenes.png, > c17468-04-blog-using_operators.png > > > This ticket is to capture the work associated with updating/fixing the Apache > Cassandra website with text/formatting/link edits. -- 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-17479) WEBSITE - Case Studies - Add Kinetic Data, fix Backblaze
[ https://issues.apache.org/jira/browse/CASSANDRA-17479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17479: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Case Studies - Add Kinetic Data, fix Backblaze > > > Key: CASSANDRA-17479 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17479 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17479-01-blog-index.png, c17479-02-blog-post.png > > > This ticket is to capture the work associated with adding a new case study to > the website and entry on the Case Studies page. > * Add Kinetic Data case study > * Add Kinetic Data card to Case Studies page > * Add Kinetic Data logo to images: kinetic_data.svg > * Fix Backblaze case study typo -- 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-17483) WEBSITE - Homepage and Case Studies page edits
[ https://issues.apache.org/jira/browse/CASSANDRA-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17483: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Homepage and Case Studies page edits > -- > > Key: CASSANDRA-17483 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17483 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Priority: Normal > Fix For: NA > > > This ticket is to capture the work associated with updates to the Apache > Cassandra homepage, Case Studies page, and blog posts to address typos and > formatting issues. -- 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-17409) WEBSITE - March 2022 blog "Can Apache Cassandra take my PEM keys?"
[ https://issues.apache.org/jira/browse/CASSANDRA-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17409: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - March 2022 blog "Can Apache Cassandra take my PEM keys?" > -- > > Key: CASSANDRA-17409 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17409 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Maulin Vasavada >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17409-01-blog-index.png, c17409-02-blog-post.png, > c17409-03-blog-index-v2.png > > > This ticket is to capture the work associated with publishing the March 2022 > blog "Can Apache Cassandra take my PEM keys?" > If this blog cannot be published by the *March 10, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17446) DOC - Update 3.11 Backups page to use nodetool refresh instead of import
[ https://issues.apache.org/jira/browse/CASSANDRA-17446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17446: --- Epic Link: (was: CASSANDRA-16761) > DOC - Update 3.11 Backups page to use nodetool refresh instead of import > > > Key: CASSANDRA-17446 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17446 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Chien-Fu Chen >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.12 > > Time Spent: 10m > Remaining Estimate: 0h > > I've found a typo shown in official Cassandra website when I was looking for > Cassandra backup & restore solution. I believe there's no nodetool import > option available. It might be nodetool refresh? > [https://cassandra.apache.org/doc/3.11/cassandra/operating/backups.html] > h2. [Restoring from Incremental Backups and > Snapshots|https://cassandra.apache.org/doc/3.11/cassandra/operating/backups.html#restoring-from-incremental-backups-and-snapshots] > The two main tools/commands for restoring a table after it has been dropped > are: > * sstableloader > * nodetool import > Ref: > [https://cassandra.apache.org/doc/3.11/cassandra/tools/nodetool/refresh.html] -- 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-17441) WEBSITE - March 2022 blog "Inside Cassandra: An Interview with Project Contributor, Lorina Poland"
[ https://issues.apache.org/jira/browse/CASSANDRA-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17441: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - March 2022 blog "Inside Cassandra: An Interview with Project > Contributor, Lorina Poland" > -- > > Key: CASSANDRA-17441 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17441 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17441-01-bad_render.png, c17441-02-blog-index.png, > c17441-03-blog-post.png > > > This ticket is to capture the work associated with publishing the March 2022 > blog "Inside Cassandra: An Interview with Project Contributor, Lorina Poland" > If this blog cannot be published by the *March 17, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17395) WEBSITE - Homepage quotes + spotlight updates, March 2022
[ https://issues.apache.org/jira/browse/CASSANDRA-17395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17395: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Homepage quotes + spotlight updates, March 2022 > - > > Key: CASSANDRA-17395 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17395 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17395-01-homepage-quote-witfoo.png, > c17395-02-homepage-quote-netflix.png, c17395-03-blog-C_is_here.png > > > This ticket is to capture the work associated with updating the Apache > Cassandra homepage and a few edits to blog posts to fix incorrect dates and > text. -- 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-17398) WEBSITE - February 2022 blog "Apache Cassandra and Java SE 11 support"
[ https://issues.apache.org/jira/browse/CASSANDRA-17398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17398: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - February 2022 blog "Apache Cassandra and Java SE 11 support" > -- > > Key: CASSANDRA-17398 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17398 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Chris Thornett >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17398-01-blog-index.png, c17398-02-blog-post.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Apache Cassandra and Java SE 11 support" > If this blog cannot be published by the *February 24, 2022 publish date*, > please contact me on ASF Slack or suggest/make changes when possible in the > pull request for the appropriate time that the blog will go live (on > blog.adoc and in the blog post .adoc). -- 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-17375) generate in-tree doc/antora.yml
[ https://issues.apache.org/jira/browse/CASSANDRA-17375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17375: --- Epic Link: (was: CASSANDRA-16761) > generate in-tree doc/antora.yml > --- > > Key: CASSANDRA-17375 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17375 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Michael Semb Wever >Assignee: Anthony Grasso >Priority: Normal > > This file contains only metadata that can be auto-generated. > Currently we can't build the website with > ``` > ANTORA_CONTENT_SOURCES_CASSANDRA_TAGS="cassandra-4.0.1 cassandra-3.11.12" > ``` > because the antora.yml files in those tags are clashing with their release > branches. -- 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-17406) WEBSITE - March 2022 blog "Apache Cassandra Changelog #13"
[ https://issues.apache.org/jira/browse/CASSANDRA-17406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17406: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - March 2022 blog "Apache Cassandra Changelog #13" > -- > > Key: CASSANDRA-17406 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17406 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Chris Thornett >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17406-01-blog-index.png, c17406-02-blog-post.png > > > This ticket is to capture the work associated with publishing the March 2022 > changelog blog #13 > If this blog cannot be published by the *March 3, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17394) WEBSITE - February 2022 blog "Upgrade Advisory: 3.0, 3.11, 4.0 Possible for Remote Code Execution for Scripted UDFs"
[ https://issues.apache.org/jira/browse/CASSANDRA-17394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17394: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - February 2022 blog "Upgrade Advisory: 3.0, 3.11, 4.0 Possible for > Remote Code Execution for Scripted UDFs" > > > Key: CASSANDRA-17394 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17394 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Urgent > Labels: pull-request-available > Fix For: 3.0.0, 3.0.11, 4.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This ticket is to capture the work associated with publishing the February > 2022 blog "Upgrade Advisory: 3.0, 3.11, 4.0 Possible for Remote Code > Execution for Scripted UDFs" > If this blog cannot be published by the *February 18, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- 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-17384) WEBSITE - February 2022 blog "Behind the scenes of an Apache Cassandra Release"
[ https://issues.apache.org/jira/browse/CASSANDRA-17384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17384: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - February 2022 blog "Behind the scenes of an Apache Cassandra > Release" > --- > > Key: CASSANDRA-17384 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17384 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Josh McKenzie >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17384-01-blog-index.png, c17384-02-blog-post.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Behind the scenes of an Apache Cassandra Release" > If this blog cannot be published by the *February 17, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- 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-17374) cassandra-website run.sh needs to move and prep files for content/ folder
[ https://issues.apache.org/jira/browse/CASSANDRA-17374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17374: --- Epic Link: (was: CASSANDRA-16761) > cassandra-website run.sh needs to move and prep files for content/ folder > - > > Key: CASSANDRA-17374 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17374 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Michael Semb Wever >Assignee: Anthony Grasso >Priority: Normal > Fix For: NA > > > See manual steps still required here: > https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1273-R1291 > -- 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-17373) WEBSITE - February 2022 blog "Tightening Security for Apache Cassandra Part: 3"
[ https://issues.apache.org/jira/browse/CASSANDRA-17373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17373: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - February 2022 blog "Tightening Security for Apache Cassandra Part: > 3" > --- > > Key: CASSANDRA-17373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17373 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez (deprecated) >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.2 > > Attachments: c17373-01-blog-index.png, c17373-02-blog-post.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Tightening Security for Apache Cassandra Part: 3" > If this blog cannot be published by the *February 14, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- 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-17343) WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2"
[ https://issues.apache.org/jira/browse/CASSANDRA-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17343: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2" > -- > > Key: CASSANDRA-17343 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17343 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17343-02-blog-post.png, c17343-examples-formatting.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Tightening Security for Apache Cassandra Part: 2" > If this blog cannot be published by the *February 4, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- 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-17317) WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 1"
[ https://issues.apache.org/jira/browse/CASSANDRA-17317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17317: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 1" > -- > > Key: CASSANDRA-17317 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17317 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17317-01-blog_index.png, c17317-02-blog_post.png, > c17317-03-blog_index.png, c17317-04-blog_post.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Tightening Security for Apache Cassandra Part: 1" > If this blog cannot be published by the *January 31, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- 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-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17356: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez (deprecated) >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17356-01-blog-index.png, c17356-02-blog-post.png > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.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 (6495a722e -> 2e6a6690f)
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 6495a722e generate docs for c630db6b new 2e6a6690f 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 (6495a722e) \ N -- N -- N refs/heads/asf-staging (2e6a6690f) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Aleksey Yeschenko updated CASSANDRA-17592: -- Status: Ready to Commit (was: Review In Progress) +1 > 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 ] Aleksey Yeschenko updated CASSANDRA-17592: -- Reviewers: Aleksey Yeschenko Status: Review In Progress (was: Patch Available) > 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] [Assigned] (CASSANDRA-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
[
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi reassigned CASSANDRA-17461:
---
Assignee: (was: Berenguer Blasi)
> Test Failure:
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}}
> for trunk:
> *
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> *
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> *
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> *
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed
> out: received 1 of 2 required responses after 0 contention retries
> at
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
> at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
> at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan
> these urls:
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
> file:/home/cassandra/cassandra/build/classes/fqltool/,
> file:/home/cassandra/cassandra/build/test/classes/,
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node1_isolatedExecutor:10] node1
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging
> service to quiesce
> INFO [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node2_isolatedExecutor:8] node2 2022-03-19
> 16:21:55,222 MessagingService.java:519 - Waiting for messaging service to
> quiesce
> {code}
> Failures can also be repeatedly hit with CircleCI test multiplexer:
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/1394/workflows/8d40d44b-7ccb-40fe-82d5-37db0bb228a3].
> The same
[jira] [Commented] (CASSANDRA-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
[
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531664#comment-17531664
]
Berenguer Blasi commented on CASSANDRA-17461:
-
Gave it a go hoping increased timeouts would help but only do for some cases,
not for the whole class. Need to look further in...
> Test Failure:
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}}
> for trunk:
> *
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> *
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> *
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> *
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed
> out: received 1 of 2 required responses after 0 contention retries
> at
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
> at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
> at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan
> these urls:
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
> file:/home/cassandra/cassandra/build/classes/fqltool/,
> file:/home/cassandra/cassandra/build/test/classes/,
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node1_isolatedExecutor:10] node1
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging
> service to quiesce
> INFO [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node2_isolatedExecutor:8] node2 2022-03-19
> 16:21:55,222 MessagingService.java:519 - Waiting for messaging service to
> quiesce
> {code}
> Failures can also be repeatedly hit with CircleCI test multiplexer:
>
[cassandra-website] branch asf-staging updated (84eb89d3f -> 6495a722e)
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 84eb89d3f generate docs for c630db6b new 6495a722e 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 (84eb89d3f) \ N -- N -- N refs/heads/asf-staging (6495a722e) 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-17589) Create release branch cassandra-4.1
[
https://issues.apache.org/jira/browse/CASSANDRA-17589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531651#comment-17531651
]
Michael Semb Wever commented on CASSANDRA-17589:
Remaining actions:
- publish the docker images ( waiting on CASSANDRA-17581 )
- (7)
> 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-17597) ant mvn-install fails on invalid javadoc
[ https://issues.apache.org/jira/browse/CASSANDRA-17597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531637#comment-17531637 ] Stefan Miklosovic edited comment on CASSANDRA-17597 at 5/4/22 9:56 AM: --- the right combo seems to be: "ant realclean && ant artifacts && ant mvn-install" BUILD FAILED /home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-4.1/build.xml:1884: The following error occurred while executing this line: /home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-4.1/build.xml:309: javadoc failed What is superstrange is that the failure on these commands is flaky. was (Author: smiklosovic): the right combo seems to be: "ant realclean && ant artifacts && ant mvn-install" BUILD FAILED /home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-4.1/build.xml:1884: The following error occurred while executing this line: /home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-4.1/build.xml:309: javadoc failed > ant mvn-install fails on invalid javadoc > > > Key: CASSANDRA-17597 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17597 > Project: Cassandra > Issue Type: Bug > Components: Build, Documentation/Javadoc >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > > ant mvn-install fails to produce Maven artifacts as it fails to process > Javadocs. -- 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-17597) ant mvn-install fails on invalid javadoc
[ https://issues.apache.org/jira/browse/CASSANDRA-17597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531637#comment-17531637 ] Stefan Miklosovic commented on CASSANDRA-17597: --- the right combo seems to be: "ant realclean && ant artifacts && ant mvn-install" BUILD FAILED /home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-4.1/build.xml:1884: The following error occurred while executing this line: /home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-4.1/build.xml:309: javadoc failed > ant mvn-install fails on invalid javadoc > > > Key: CASSANDRA-17597 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17597 > Project: Cassandra > Issue Type: Bug > Components: Build, Documentation/Javadoc >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > > ant mvn-install fails to produce Maven artifacts as it fails to process > Javadocs. -- 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-17597) ant mvn-install fails on invalid javadoc
[ https://issues.apache.org/jira/browse/CASSANDRA-17597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17597: -- Description: ant mvn-install fails to produce Maven artifacts as it fails to process Javadocs. (was: ant mvn-install fails to produce Maven artifacts as it fails to process Javadocs. This affects 4.1 and hence trunk.) > ant mvn-install fails on invalid javadoc > > > Key: CASSANDRA-17597 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17597 > Project: Cassandra > Issue Type: Bug > Components: Build, Documentation/Javadoc >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > > ant mvn-install fails to produce Maven artifacts as it fails to process > Javadocs. -- 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-17597) ant mvn-install fails on invalid javadoc
[ https://issues.apache.org/jira/browse/CASSANDRA-17597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531636#comment-17531636 ] Stefan Miklosovic commented on CASSANDRA-17597: --- I will watch this more closely as I can not reproduced this anymore. I got failed local build once as Javadoc were errorneous but I can not get it anymore. It was some combination of mvn-install / mvn-realclean / artifacts and I hit this code: https://github.com/apache/cassandra/blob/trunk/build.xml#L309 > ant mvn-install fails on invalid javadoc > > > Key: CASSANDRA-17597 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17597 > Project: Cassandra > Issue Type: Bug > Components: Build, Documentation/Javadoc >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > > ant mvn-install fails to produce Maven artifacts as it fails to process > Javadocs. > This affects 4.1 and hence trunk. -- 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-17597) ant mvn-install fails on invalid javadoc
Stefan Miklosovic created CASSANDRA-17597: - Summary: ant mvn-install fails on invalid javadoc Key: CASSANDRA-17597 URL: https://issues.apache.org/jira/browse/CASSANDRA-17597 Project: Cassandra Issue Type: Bug Components: Build, Documentation/Javadoc Reporter: Stefan Miklosovic Assignee: Stefan Miklosovic ant mvn-install fails to produce Maven artifacts as it fails to process Javadocs. This affects 4.1 and hence trunk. -- 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-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
[
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi reassigned CASSANDRA-17461:
---
Assignee: Berenguer Blasi
> Test Failure:
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.x
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}}
> for trunk:
> *
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> *
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> *
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> *
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed
> out: received 1 of 2 required responses after 0 contention retries
> at
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
> at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
> at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan
> these urls:
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
> file:/home/cassandra/cassandra/build/classes/fqltool/,
> file:/home/cassandra/cassandra/build/test/classes/,
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node1_isolatedExecutor:10] node1
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging
> service to quiesce
> INFO [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node2_isolatedExecutor:8] node2 2022-03-19
> 16:21:55,222 MessagingService.java:519 - Waiting for messaging service to
> quiesce
> {code}
> Failures can also be repeatedly hit with CircleCI test multiplexer:
>
[jira] [Updated] (CASSANDRA-17461) Test Failure: org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
[
https://issues.apache.org/jira/browse/CASSANDRA-17461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-17461:
Complexity: Normal
Discovered By: Unit Test
Severity: Normal
Status: Open (was: Triage Needed)
> Test Failure:
> org.apache.cassandra.distributed.test.CASTest.testConflictingWritesWithStaleRingInformation
> -
>
> Key: CASSANDRA-17461
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17461
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Andres de la Peña
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.x
>
>
> Intermittent failures on {{org.apache.cassandra.distributed.test.CASTest}}
> for trunk:
> *
> [testConflictingWritesWithStaleRingInformation|https://ci-cassandra.apache.org/job/Cassandra-trunk/1024/testReport/org.apache.cassandra.distributed.test/CASTest/testConflictingWritesWithStaleRingInformation_3/]
> *
> [testSuccessfulWriteBeforeRangeMovement|https://ci-cassandra.apache.org/job/Cassandra-trunk/1025/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteBeforeRangeMovement/]
> *
> [testSuccessfulWriteDuringRangeMovementFollowedByConflicting|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSuccessfulWriteDuringRangeMovementFollowedByConflicting/]
> *
> [testSucccessfulWriteDuringRangeMovementFollowedByRead|https://ci-cassandra.apache.org/job/Cassandra-trunk/1020/testReport/org.apache.cassandra.distributed.test/CASTest/testSucccessfulWriteDuringRangeMovementFollowedByRead/]
> All four seem to have the same aspect:
> {code}
> Failed 2 times in the last 5 runs. Flakiness: 50%, Stability: 60%
> Error Message
> CAS operation timed out: received 1 of 2 required responses after 0
> contention retries
> Stacktrace
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed
> out: received 1 of 2 required responses after 0 contention retries
> at
> org.apache.cassandra.service.paxos.Paxos$MaybeFailure.markAndThrowAsTimeoutOrFailure(Paxos.java:547)
> at org.apache.cassandra.service.paxos.Paxos.begin(Paxos.java:1048)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:659)
> at org.apache.cassandra.service.paxos.Paxos.cas(Paxos.java:618)
> at org.apache.cassandra.service.StorageProxy.cas(StorageProxy.java:307)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeWithCondition(ModificationStatement.java:500)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:467)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:122)
> at
> org.apache.cassandra.distributed.impl.Coordinator.unsafeExecuteInternal(Coordinator.java:103)
> at
> org.apache.cassandra.distributed.impl.Coordinator.lambda$executeWithResult$0(Coordinator.java:66)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> Standard Output
> DEBUG [main] 2022-03-19 16:20:42,868 Reflections.java:198 - going to scan
> these urls:
> [jar:file:/home/cassandra/cassandra/build/apache-cassandra-4.1-SNAPSHOT.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/simulator-bootstrap.jar!/,
>
> jar:file:/home/cassandra/cassandra/build/test/lib/jars/dtest-api-0.0.12.jar!/,
> file:/home/cassandra/cassandra/build/classes/fqltool/,
> file:/home/cassandra/cassandra/build/test/classes/,
> file:/home/cassandra/cassandra/build/classes/main/, file:/home/cass
> ...[truncated 4929659 chars]...
> gService.java:519 - Waiting for messaging service to quiesce
> INFO [node1_isolatedExecutor:10] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node1_isolatedExecutor:10] node1
> 2022-03-19 16:21:55,221 MessagingService.java:519 - Waiting for messaging
> service to quiesce
> INFO [node2_isolatedExecutor:8] 2022-03-19 16:21:55,223
> SubstituteLogger.java:169 - INFO [node2_isolatedExecutor:8] node2 2022-03-19
> 16:21:55,222 MessagingService.java:519 - Waiting for messaging service to
> quiesce
> {code}
> Failures can also be repeatedly hit with CircleCI test multiplexer:
>
[jira] [Commented] (CASSANDRA-17596) Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build
[ https://issues.apache.org/jira/browse/CASSANDRA-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531613#comment-17531613 ] Stefan Miklosovic commented on CASSANDRA-17596: --- I ve got interesting errors on 4.0 build in circle, they seem to be completely unrelated. I am looking into it. > Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build > > > Key: CASSANDRA-17596 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17596 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > These two arrays are not initialised (1) which means that if I do not set > start nor end, when ClusteringBound.create is called, it will be null, but it > will fail here (2) as values will be null. > The fix consists of check if values are null and if they are, we build that > bound immediately. > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SimpleBuilders.java#L257-L258 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/ClusteringBound.java#L128 -- 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 (eeac0aa28 -> 84eb89d3f)
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 eeac0aa28 generate docs for c630db6b new 84eb89d3f 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 (eeac0aa28) \ N -- N -- N refs/heads/asf-staging (84eb89d3f) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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=17531533#comment-17531533
]
Michael Semb Wever commented on CASSANDRA-17589:
dawdle duckling: website CI needs to be updated to also trigger off a 4.1
build; committed as
[1fc9b5ee71dc37e1145f276ead5c680c6b3fe3db|https://github.com/apache/cassandra-builds/commit/1fc9b5ee71dc37e1145f276ead5c680c6b3fe3db].
> 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] branch trunk updated: ninja-fix: cassandra-website CI to trigger off cassandra-4.1 builds as well
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
The following commit(s) were added to refs/heads/trunk by this push:
new 1fc9b5e ninja-fix: cassandra-website CI to trigger off cassandra-4.1
builds as well
1fc9b5e is described below
commit 1fc9b5ee71dc37e1145f276ead5c680c6b3fe3db
Author: Mick Semb Wever
AuthorDate: Wed May 4 09:26:20 2022 +0200
ninja-fix: cassandra-website CI to trigger off cassandra-4.1 builds as well
---
jenkins-dsl/cassandra_job_dsl_seed.groovy | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/jenkins-dsl/cassandra_job_dsl_seed.groovy
b/jenkins-dsl/cassandra_job_dsl_seed.groovy
index ff0ce71..cb13cbf 100644
--- a/jenkins-dsl/cassandra_job_dsl_seed.groovy
+++ b/jenkins-dsl/cassandra_job_dsl_seed.groovy
@@ -1356,7 +1356,7 @@ job('cassandra-website') {
}
}
triggers {
-upstream('Cassandra-3.11,Cassandra-4.0,Cassandra-trunk', 'UNSTABLE')
+upstream('Cassandra-3.11,Cassandra-4.0,Cassandra-4.1,Cassandra-trunk',
'UNSTABLE')
scm('H/5 * * * *')
}
steps {
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17596) Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build
[ https://issues.apache.org/jira/browse/CASSANDRA-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531520#comment-17531520 ] Stefan Miklosovic edited comment on CASSANDRA-17596 at 5/4/22 7:02 AM: --- https://github.com/apache/cassandra/pull/1602 4.0 https://app.circleci.com/pipelines/github/instaclustr/cassandra?branch=CASSANDRA-17596 was (Author: smiklosovic): https://github.com/apache/cassandra/pull/1602 > Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build > > > Key: CASSANDRA-17596 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17596 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > These two arrays are not initialised (1) which means that if I do not set > start nor end, when ClusteringBound.create is called, it will be null, but it > will fail here (2) as values will be null. > The fix consists of check if values are null and if they are, we build that > bound immediately. > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SimpleBuilders.java#L257-L258 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/ClusteringBound.java#L128 -- 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-17596) Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build
[ https://issues.apache.org/jira/browse/CASSANDRA-17596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17596: -- Test and Documentation Plan: unit test Status: Patch Available (was: Open) https://github.com/apache/cassandra/pull/1602 > Fix NPE in SimpleBuilders.ParititionUpdateBulder.RTBuilder.build > > > Key: CASSANDRA-17596 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17596 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > These two arrays are not initialised (1) which means that if I do not set > start nor end, when ClusteringBound.create is called, it will be null, but it > will fail here (2) as values will be null. > The fix consists of check if values are null and if they are, we build that > bound immediately. > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SimpleBuilders.java#L257-L258 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/ClusteringBound.java#L128 -- 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
