[jira] [Updated] (CASSANDRA-17581) Failed to retrieve RMIServer stub: Malformed IPv6 address at index 7

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17581:
--
Description: 
 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 
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205)
 ~[jersey-server-2.25.1.jar:?]
    at 
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
 ~[jersey-server-2.25.1.jar:?]
    at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
 ~[jersey-server-2.25.1.jar:?]
    at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
 ~[jersey-server-2.25.1.jar:?]
    at 
org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
 ~[jersey-server-2.25.1.jar:?]
    at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) 
~[jersey-server-2.25.1.jar:?]
    at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) 
~[jersey-common-2.25.1.jar:?]
    at org.glass

[jira] [Updated] (CASSANDRA-17581) nodetool with Java 8u331 returns "URISyntaxException: 'Malformed IPv6 address at index 7: rmi://[127.0.0.1]:7199'"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17581:
--
Summary: nodetool with Java 8u331 returns "URISyntaxException: 'Malformed 
IPv6 address at index 7: rmi://[127.0.0.1]:7199'"  (was: Failed to retrieve 
RMIServer stub: Malformed IPv6 address at index 7)

> 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
>Priority: Normal
>  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 
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDis

[jira] [Updated] (CASSANDRA-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Petrov updated CASSANDRA-17582:

Status: Patch Available  (was: In Progress)

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Task
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
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-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Petrov updated CASSANDRA-17582:

Status: In Progress  (was: Patch Available)

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Task
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
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-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Petrov updated CASSANDRA-17582:

Issue Type: Improvement  (was: Task)

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
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-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Petrov updated CASSANDRA-17582:

Status: Ready to Commit  (was: Review In Progress)

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Task
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
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-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Petrov updated CASSANDRA-17582:

Reviewers: Alex Petrov
   Status: Review In Progress  (was: Patch Available)

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Task
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
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: Update Cassandra build CI script for new website

[mck]

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 d126ede  Update Cassandra build CI script for new website
d126ede is described below

commit d126edec3fea77e3c0123a2327f01f6ab5697b15
Author: Mick Semb Wever 
AuthorDate: Thu Aug 5 11:44:03 2021 +0200

Update Cassandra build CI script for new website

 patch by Mick Semb Wever; reviewed by Anthony Grasso for CASSANDRA-16765
---
 jenkins-dsl/cassandra_job_dsl_seed.groovy | 27 ++-
 1 file changed, 18 insertions(+), 9 deletions(-)

diff --git a/jenkins-dsl/cassandra_job_dsl_seed.groovy 
b/jenkins-dsl/cassandra_job_dsl_seed.groovy
index 83e44f9..eaa3b1a 100644
--- a/jenkins-dsl/cassandra_job_dsl_seed.groovy
+++ b/jenkins-dsl/cassandra_job_dsl_seed.groovy
@@ -1321,6 +1321,9 @@ job('cassandra-website') {
 numToKeep(10)
 artifactNumToKeep(10)
 }
+throttleConcurrentBuilds {
+maxTotal(1)
+}
 wrappers {
 preBuildCleanup()
 timeout {
@@ -1350,21 +1353,27 @@ job('cassandra-website') {
 }
 }
 triggers {
+upstream('Cassandra-3.11,Cassandra-4.0,Cassandra-trunk', 'UNSTABLE')
 scm('H/5 * * * *')
 }
 steps {
 buildDescription('', buildDescStr)
-// the chmod below is a hack for INFRA-20814
 // for debugging it can be useful to add a `git show --stat HEAD` 
before the push
 shell("""
-git checkout asf-staging ;
-git reset --hard origin/trunk ;
-docker-compose build --build-arg UID=`id -u` --build-arg 
GID=`id -g` cassandra-website ;
-chmod -R 777 src content ;
-docker-compose run cassandra-website ;
-git add content/ src/doc/ ;
-git commit -a -m "generate docs for `git rev-parse --short 
HEAD`" ;
-git push -f origin asf-staging ;
+git checkout asf-staging ;
+git reset --hard origin/trunk ;
+
+# HACK for INFRA-20814 ;
+mkdir -p content/doc ;
+chmod -R ag+rw site-* content ;
+
+./run.sh website-ui bundle -a BUILD_USER_ARG:`whoami` -a 
UID_ARG:`id -u` -a GID_ARG:`id -g` ;
+./run.sh website container -a BUILD_USER_ARG:`whoami` -a 
UID_ARG:`id -u` -a GID_ARG:`id -g` ;
+./run.sh website build -g ;
+
+git add content ;
+git commit -a -m "generate docs for `git rev-parse --short HEAD`" ;
+git push -f origin asf-staging ;
   """)
 }
 }


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Petrov updated CASSANDRA-17582:

Status: Patch Available  (was: Open)

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
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-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Petrov updated CASSANDRA-17582:

Status: Patch Available  (was: Ready to Commit)

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
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-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Petrov updated CASSANDRA-17582:

Status: Review In Progress  (was: Patch Available)

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17581) nodetool with Java 8u331 returns "URISyntaxException: 'Malformed IPv6 address at index 7: rmi://[127.0.0.1]:7199'"

[Erick Ramirez (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528608#comment-17528608
 ] 

Erick Ramirez commented on CASSANDRA-17581:
---

Thanks for logging this ticket as I've requested in PR #1586 [~jermy] . 🍻

> 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
>Priority: Normal
>  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 
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvi

[jira] [Updated] (CASSANDRA-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Petrov updated CASSANDRA-17582:

Status: Ready to Commit  (was: Review In Progress)

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
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-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528609#comment-17528609
 ] 

Alex Petrov commented on CASSANDRA-17582:
-

+1, LGTM

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
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-17582) Add missing information about whether to drop sstables or not when dropping schema objects

[Alex Petrov (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Petrov updated CASSANDRA-17582:

Status: Open  (was: Patch Available)

> Add missing information about whether to drop sstables or not when dropping 
> schema objects
> --
>
> Key: CASSANDRA-17582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.x
>
>
> This is the missed piece in SchemaChangeListener - when the implementation of 
> SchemaUpdateHandler decides to say drop a table but keep sstables, that 
> information about not-dropping sstables is not propagated to the 
> SchemaChangeListener



--
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'"

[Erick Ramirez (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528608#comment-17528608
 ] 

Erick Ramirez edited comment on CASSANDRA-17581 at 4/27/22 7:46 AM:


Thanks for logging this ticket as I've requested in [PR 
#1586|https://github.com/apache/cassandra/pull/1586], [~jermy] . 🍻


was (Author: JIRAUSER285101):
Thanks for logging this ticket as I've requested in PR #1586 [~jermy] . 🍻

> 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
>Priority: Normal
>  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(AbstractJavaResourceMethod

[jira] [Updated] (CASSANDRA-16765) Update Cassandra build CI script for new website

[Michael Semb Wever (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Semb Wever updated CASSANDRA-16765:
---
  Fix Version/s: NA
Source Control Link: 
https://github.com/apache/cassandra-builds/commit/d126edec3fea77e3c0123a2327f01f6ab5697b15
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

Committed as 
[d126edec3fea77e3c0123a2327f01f6ab5697b15|https://github.com/apache/cassandra-builds/commit/d126edec3fea77e3c0123a2327f01f6ab5697b15].

> Update Cassandra build CI script for new website
> 
>
> Key: CASSANDRA-16765
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16765
> Project: Cassandra
>  Issue Type: Task
>  Components: Build, CI, Documentation/Website
>Reporter: Anthony Grasso
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: NA
>
>
> Update the apache/cassandra-build repository has [.groovy job 
> script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy]
>  to use the new tooling to build the website.
> The apache/cassandra-build repository has [.groovy job 
> script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy].
>  It [builds and deploys the 
> website|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L1255-L1268]
>  to cassandra-website staging when the cassandra-website is updated.
> We need to change the commands in the .groovy script to at least rebuild the 
> site when a change happens in the cassandra-website repository.
> It would be also good to build the docs when a change happens to doc/source 
> directory in the cassandra repository.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17581) nodetool with Java 8u331 returns "URISyntaxException: 'Malformed IPv6 address at index 7: rmi://[127.0.0.1]:7199'"

[Erick Ramirez (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528612#comment-17528612
 ] 

Erick Ramirez commented on CASSANDRA-17581:
---

The URL parser for JNDI providers which includes RMI (used by JMX) has been 
improved in Oracle Java 8u331 and brackets are only allowed around IPv6 
addresses 
([JDK-8278972|https://www.oracle.com/java/technologies/javase/8u331-relnotes.html]).

Attempts to run {{nodetool}} with Java 8u331 breaks because the host in the RMI 
URL is enclosed in square brackets (from 
[NodeProbe.java|https://github.com/apache/cassandra/blob/cassandra-4.0.3/src/java/org/apache/cassandra/tools/NodeProbe.java#L108]
 class):
{noformat}
private static final String fmtUrl = 
"service:jmx:rmi:///jndi/rmi://[%s]:%d/jmxrmi";
{noformat}
Workarounds provided by 
[fruch|https://community.datastax.com/users/6521/fruch.html] and 
[penky28|https://community.datastax.com/users/4944/penky28-147901.html] in 
[https://community.datastax.com/questions/13764/] are:

OPTION 1 - Add the "legacy" parsing flag when running {{{}nodetool{}}}, for 
example:

{noformat}$ nodetool -Dcom.sun.jndi.rmiURLParsing=legacy status{noformat}

OPTION 2 - Specify the hostname with an IPv6 subnet prefix, for example:

{noformat}$ nodetool -h :::127.0.0.1 status{noformat}

> 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
>Priority: Normal
>  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

[cassandra-website] branch asf-staging updated (9488e03a -> 2045fd07)

[git-site-role]

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 9488e03a generate docs for 8fd077a6
 new 2045fd07 generate docs for 8fd077a6

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   (9488e03a)
\
 N -- N -- N   refs/heads/asf-staging (2045fd07)

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] [Assigned] (CASSANDRA-17581) nodetool with Java 8u331 returns "URISyntaxException: 'Malformed IPv6 address at index 7: rmi://[127.0.0.1]:7199'"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez reassigned CASSANDRA-17581:
-

Assignee: Jermy Li

> 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: Jermy Li
>Priority: Normal
>  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 
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205)
>  ~[jersey-server-2.25.1.jar:?]
>     at 
> org.glassfi

[jira] [Assigned] (CASSANDRA-17501) Security admin separation of duties

[Berenguer Blasi (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Berenguer Blasi reassigned CASSANDRA-17501:
---

Assignee: Berenguer Blasi

> Security admin separation of duties
> ---
>
> Key: CASSANDRA-17501
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17501
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Authorization
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.x
>
>
> This ticket is about enabling a sort of security admin role.
> Think of a hospital with patient data which is very sensitive information. IT 
> should be able to grant/revoke/restrict access to the data without having 
> access to the data itself. This is the clear separation of duties between 
> admins and users of the database we're after.
> An example is along the lines:
> {noformat}
> As a superuser:
> CREATE KEYSPACE patientdata …;
> CREATE ROLE security_admin;
> GRANT security_admin TO admin_guy;
> GRANT AUTHORIZE FOR SELECT, MODIFY, EXECUTE ON patientdata TO security_admin;
> RESTRICT SELECT, MODIFY, EXECUTE ON KEYSPACE patientdata TO security_admin;
> As a security admin:
> GRANT SELECT ON patientdata TO new_nurse;
> GRANT SELECT, MODIFY ON patientdata TO doctor_house;
> {noformat}
>  Original idea of [~snazy]



--
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'"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17581:
--
 Bug Category: Parent values: Code(13163)
   Complexity: Low Hanging Fruit
Discovered By: User Report
Fix Version/s: 3.0.x
   3.11.x
   4.0.x
 Severity: Normal
   Status: Open  (was: Triage Needed)

> 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: Jermy Li
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.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(AbstractJavaResourceMet

[jira] [Updated] (CASSANDRA-17501) Security admin separation of duties

[Berenguer Blasi (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Berenguer Blasi updated CASSANDRA-17501:

Test and Documentation Plan: See PR
 Status: Patch Available  (was: In Progress)

> Security admin separation of duties
> ---
>
> Key: CASSANDRA-17501
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17501
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Authorization
>Reporter: Berenguer Blasi
>Priority: Normal
> Fix For: 4.x
>
>
> This ticket is about enabling a sort of security admin role.
> Think of a hospital with patient data which is very sensitive information. IT 
> should be able to grant/revoke/restrict access to the data without having 
> access to the data itself. This is the clear separation of duties between 
> admins and users of the database we're after.
> An example is along the lines:
> {noformat}
> As a superuser:
> CREATE KEYSPACE patientdata …;
> CREATE ROLE security_admin;
> GRANT security_admin TO admin_guy;
> GRANT AUTHORIZE FOR SELECT, MODIFY, EXECUTE ON patientdata TO security_admin;
> RESTRICT SELECT, MODIFY, EXECUTE ON KEYSPACE patientdata TO security_admin;
> As a security admin:
> GRANT SELECT ON patientdata TO new_nurse;
> GRANT SELECT, MODIFY ON patientdata TO doctor_house;
> {noformat}
>  Original idea of [~snazy]



--
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-17501) Security admin separation of duties

[Berenguer Blasi (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Berenguer Blasi updated CASSANDRA-17501:

Authors:   (was: Berenguer Blasi)

> Security admin separation of duties
> ---
>
> Key: CASSANDRA-17501
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17501
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Authorization
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.x
>
>
> This ticket is about enabling a sort of security admin role.
> Think of a hospital with patient data which is very sensitive information. IT 
> should be able to grant/revoke/restrict access to the data without having 
> access to the data itself. This is the clear separation of duties between 
> admins and users of the database we're after.
> An example is along the lines:
> {noformat}
> As a superuser:
> CREATE KEYSPACE patientdata …;
> CREATE ROLE security_admin;
> GRANT security_admin TO admin_guy;
> GRANT AUTHORIZE FOR SELECT, MODIFY, EXECUTE ON patientdata TO security_admin;
> RESTRICT SELECT, MODIFY, EXECUTE ON KEYSPACE patientdata TO security_admin;
> As a security admin:
> GRANT SELECT ON patientdata TO new_nurse;
> GRANT SELECT, MODIFY ON patientdata TO doctor_house;
> {noformat}
>  Original idea of [~snazy]



--
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'"

[Erick Ramirez (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-17581:
--
Impacts: Clients  (was: None)

> 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: Jermy Li
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.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 
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205)
>  ~[j

[cassandra-builds] branch trunk updated: Revert "ninja-fix – disable arm64 builds until INFRA-22930 is resolved properly"

[mck]

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 b830c21  Revert "ninja-fix – disable arm64 builds until INFRA-22930 is 
resolved properly"
b830c21 is described below

commit b830c21bed0fc7f5f6e59fbc4774f856530eb980
Author: Mick Semb Wever 
AuthorDate: Wed Apr 27 10:49:45 2022 +0200

Revert "ninja-fix – disable arm64 builds until INFRA-22930 is resolved 
properly"

This reverts commit a0b2355c34823c2e4183fbb50957ec61206213cf.
---
 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 eaa3b1a..c2e27a7 100644
--- a/jenkins-dsl/cassandra_job_dsl_seed.groovy
+++ b/jenkins-dsl/cassandra_job_dsl_seed.groovy
@@ -24,7 +24,7 @@ if(binding.hasVariable("CASSANDRA_JDK_LABEL")) {
 
 // architectures. blank is amd64
 def archs = ['', '-arm64']
-arm64_enabled = false
+arm64_enabled = true
 arm64_test_label_enabled = false
 def use_arm64_test_label() { return arm64_enabled && arm64_test_label_enabled }
 


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17581) nodetool with Java 8u331 returns "URISyntaxException: 'Malformed IPv6 address at index 7: rmi://[127.0.0.1]:7199'"

[Jermy Li (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528666#comment-17528666
 ] 

Jermy Li commented on CASSANDRA-17581:
--

We have tried the OPTION 2 (using IPv4-mapped IPv6 address), but still got 
another error:
{code:java}
Exception creating connection to: ::127.0.0.1; nested exception is: 
java.net.SocketException: Network is unreachable (connect failed)]{code}
It may require starting cassandra server with a listening IPv6 socket. 

For more error details please see:

[https://github.com/apache/incubator-hugegraph/pull/1844#issuecomment-1107799113]

 

> 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: Jermy Li
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.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.AbstractJavaResource

[jira] [Commented] (CASSANDRA-17581) nodetool with Java 8u331 returns "URISyntaxException: 'Malformed IPv6 address at index 7: rmi://[127.0.0.1]:7199'"

[Erick Ramirez (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528672#comment-17528672
 ] 

Erick Ramirez commented on CASSANDRA-17581:
---

It looks like you tried with {color:#ff8b00}{{::127.0.0.1}}{color}. Just to be 
clear, have you tried {color:#ff8b00}{{:::127.0.0.1}}{color} instead? 🙂

> 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: Jermy Li
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.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.

[jira] [Commented] (CASSANDRA-16310) Track top partitions (by size and tombstone count) and display in nodetool tablestats

[Berenguer Blasi (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528685#comment-17528685
 ] 

Berenguer Blasi commented on CASSANDRA-16310:
-

Hi All,

I noticed some new failures such as 
{{dtest-large-novnode.materialized_views_test.TestMaterializedViews.test_add_node_after_wide_mv_with_range_deletions}}
 and I think it bisects to this ticket. I can see failures locally for 
545809616c92a91e4c39d1eedfa65800f25a2a93 but passing for 
49cc352916f8dad23533b5328638aeb05ac04ea1 i.e.

#justfyi

> Track top partitions (by size and tombstone count) and display in nodetool 
> tablestats
> -
>
> Key: CASSANDRA-16310
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16310
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Other
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 4.1
>
>
> We should track the top partitions by size and tombstone count and display in 
> {{nodetool tablestats}}



--
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-16718) Changing listen_address with prefer_local may lead to issues

[Jan Karlsson (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528707#comment-17528707
 ] 

Jan Karlsson commented on CASSANDRA-16718:
--

[~brandon.williams] The ticket has been quiet for awhile now. What is the 
status on this?

> Changing listen_address with prefer_local may lead to issues
> 
>
> Key: CASSANDRA-16718
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16718
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/Config
>Reporter: Jan Karlsson
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.11.x, 4.0.x
>
>
> Many container based solution function by assigning new listen_addresses when 
> nodes are stopped. Changing the listen_address is usually as simple as 
> turning off the node and changing the yaml file. 
> However, if prefer_local is enabled, I observed that nodes were unable to 
> join the cluster and fail with 'Unable to gossip with any seeds'. 
> Trace shows that the changing node will try to communicate with the existing 
> node but the response is never received. I assume it is because the existing 
> node attempts to communicate with the local address during the shadow round.
>  



--
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-16718) Changing listen_address with prefer_local may lead to issues

[Jan Karlsson (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528707#comment-17528707
 ] 

Jan Karlsson edited comment on CASSANDRA-16718 at 4/27/22 9:57 AM:
---

[~brandon.williams] The ticket has been quiet for awhile now. What is the 
status on this? Are we waiting for a reviewer?


was (Author: jan karlsson):
[~brandon.williams] The ticket has been quiet for awhile now. What is the 
status on this?

> Changing listen_address with prefer_local may lead to issues
> 
>
> Key: CASSANDRA-16718
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16718
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/Config
>Reporter: Jan Karlsson
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.11.x, 4.0.x
>
>
> Many container based solution function by assigning new listen_addresses when 
> nodes are stopped. Changing the listen_address is usually as simple as 
> turning off the node and changing the yaml file. 
> However, if prefer_local is enabled, I observed that nodes were unable to 
> join the cluster and fail with 'Unable to gossip with any seeds'. 
> Trace shows that the changing node will try to communicate with the existing 
> node but the response is never received. I assume it is because the existing 
> node attempts to communicate with the local address during the shadow round.
>  



--
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-16310) Track top partitions (by size and tombstone count) and display in nodetool tablestats

[Marcus Eriksson (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528713#comment-17528713
 ] 

Marcus Eriksson commented on CASSANDRA-16310:
-

thanks. will check

> Track top partitions (by size and tombstone count) and display in nodetool 
> tablestats
> -
>
> Key: CASSANDRA-16310
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16310
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Other
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 4.1
>
>
> We should track the top partitions by size and tombstone count and display in 
> {{nodetool tablestats}}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17581) nodetool with Java 8u331 returns "URISyntaxException: 'Malformed IPv6 address at index 7: rmi://[127.0.0.1]:7199'"

[Jermy Li (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528714#comment-17528714
 ] 

Jermy Li commented on CASSANDRA-17581:
--

I will also try {color:#ff8b00}{{:::127.0.0.1}}{color} instead

> 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: Jermy Li
>Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.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 
> org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvide

[cassandra-dtest] branch trunk updated (5e06a1f5 -> 062ebe5a)

[smiklosovic]

This is an automated email from the ASF dual-hosted git repository.

smiklosovic pushed a change to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git


from 5e06a1f5 CONTAINS and CONTAINS KEY support for Lightweight Transactions
 add 062ebe5a modified test_cqlsh.py test for CASSANDRA-16456

No new revisions were added by this update.

Summary of changes:
 cqlsh_tests/test_cqlsh.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] branch trunk updated: add plugin support for CQLSH

[smiklosovic]

This is an automated email from the ASF dual-hosted git repository.

smiklosovic pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git


The following commit(s) were added to refs/heads/trunk by this push:
 new 381c2a4fa8 add plugin support for CQLSH
381c2a4fa8 is described below

commit 381c2a4fa82db80543fd67da6669de022d7576c4
Author: Bhouse99 
AuthorDate: Wed Mar 30 13:37:22 2022 -0700

add plugin support for CQLSH

patch by Brian Houser; reviewed by Stefan Miklosovic and Brandon Williams 
for CASSANDRA-16456
---
 .gitignore |   1 +
 CHANGES.txt|   1 +
 bin/cqlsh.py   |  68 
 build.xml  |   5 +-
 conf/cqlshrc.sample|   8 +
 conf/credentials.sample|   2 +-
 lib/puresasl-internal-only-0.6.2.zip   | Bin 0 -> 9085 bytes
 pylib/cqlshlib/authproviderhandling.py | 176 +++
 pylib/cqlshlib/test/test_authproviderhandling.py   | 190 +
 .../complex_auth_provider  |  10 ++
 .../complex_auth_provider_creds|   3 +
 .../complex_auth_provider_with_pass|  11 ++
 .../test_authproviderhandling_config/empty_example |   2 +
 .../full_plain_text_example|  10 ++
 .../illegal_example|   5 +
 .../no_classname_example   |   5 +
 .../partial_example|   8 +
 .../plain_text_full_creds  |   3 +
 .../plain_text_partial_creds   |   2 +
 .../plain_text_partial_example |   8 +
 pylib/cqlshlib/util.py |  19 ++-
 21 files changed, 501 insertions(+), 36 deletions(-)

diff --git a/.gitignore b/.gitignore
index a99fd14310..c8e79b312a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -14,6 +14,7 @@ lib/
 pylib/src/
 **/cqlshlib.xml
 !lib/cassandra-driver-internal-only-*.zip
+!lib/puresasl-*.zip
 
 # C* debs
 build-stamp
diff --git a/CHANGES.txt b/CHANGES.txt
index 4ae12a7c97..7850ca8e5b 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 4.1
+ * Add plugin support for CQLSH (CASSANDRA-16456)
  * Add guardrail to disallow querying with ALLOW FILTERING (CASSANDRA-17370)
  * Enhance SnakeYAML properties to be reusable outside of YAML parsing, 
support camel case conversion to snake case, and add support to ignore 
properties (CASSANDRA-17166)
  * nodetool compact should support using a key string to find the range to 
avoid operators having to manually do this (CASSANDRA-17537)
diff --git a/bin/cqlsh.py b/bin/cqlsh.py
index c412d20ddf..637c95e70a 100755
--- a/bin/cqlsh.py
+++ b/bin/cqlsh.py
@@ -113,7 +113,7 @@ if cql_zip:
 sys.path.insert(0, os.path.join(cql_zip, 'cassandra-driver-' + ver))
 
 # the driver needs dependencies
-third_parties = ('six-')
+third_parties = ('six-', 'puresasl-')
 
 for lib in third_parties:
 lib_zip = find_zip(lib)
@@ -145,7 +145,7 @@ cqlshlibdir = os.path.join(CASSANDRA_PATH, 'pylib')
 if os.path.isdir(cqlshlibdir):
 sys.path.insert(0, cqlshlibdir)
 
-from cqlshlib import cql3handling, pylexotron, sslhandling, cqlshhandling
+from cqlshlib import cql3handling, pylexotron, sslhandling, cqlshhandling, 
authproviderhandling
 from cqlshlib.copyutil import ExportTask, ImportTask
 from cqlshlib.displaying import (ANSI_RESET, BLUE, COLUMN_NAME_COLORS, CYAN,
  RED, WHITE, FormattedValue, colorme)
@@ -154,6 +154,8 @@ from cqlshlib.formatting import (DEFAULT_DATE_FORMAT, 
DEFAULT_NANOTIME_FORMAT,
  format_by_type)
 from cqlshlib.tracing import print_trace, print_trace_session
 from cqlshlib.util import get_file_encoding_bomsize
+from cqlshlib.util import is_file_secure
+
 
 DEFAULT_HOST = '127.0.0.1'
 DEFAULT_PORT = 9042
@@ -426,7 +428,7 @@ class Shell(cmd.Cmd):
 default_page_size = 100
 
 def __init__(self, hostname, port, color=False,
- username=None, password=None, encoding=None, stdin=None, 
tty=True,
+ username=None, encoding=None, stdin=None, tty=True,
  completekey=DEFAULT_COMPLETEKEY, browser=None, use_conn=None,
  cqlver=None, keyspace=None,
  tracing_enabled=False, expand_enabled=False,
@@ -442,16 +444,21 @@ class Shell(cmd.Cmd):
  request_timeout=DEFAULT_REQUEST_TIMEOUT_SECONDS,
  protocol_version=None,
  connect_timeout=DEFAULT_CONNECT_TIMEOUT_SECONDS,
- is_subshell=False):
+ is_subshell=False,
+ auth_provider=None):
 cmd.Cmd.__init__(self, completekey=completekey)
 self.hostname = hostname
 self.port = port
-self.auth_provider = None
-

[jira] [Updated] (CASSANDRA-16456) Add Plugin Support for CQLSH

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-16456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-16456:
--
  Fix Version/s: 4.1
Source Control Link: 
https://github.com/apache/cassandra/commit/381c2a4fa82db80543fd67da6669de022d7576c4
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

thanks [~bhouser] !

> Add Plugin Support for CQLSH
> 
>
> Key: CASSANDRA-16456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16456
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Tool/cqlsh
>Reporter: Brian Houser
>Assignee: Brian Houser
>Priority: Normal
>  Labels: gsoc2021, mentor
> Fix For: 4.1
>
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> Currently the Cassandra drivers offer a plugin authenticator architecture for 
> the support of different authentication methods. This has been leveraged to 
> provide support for LDAP, Kerberos, and Sigv4 authentication. Unfortunately, 
> cqlsh, the included CLI tool, does not offer such support. Switching to a new 
> enhanced authentication scheme thus means being cut off from using cqlsh in 
> normal operation.
> We should have a means of using the same plugins and authentication providers 
> as the Python Cassandra driver.
> Here's a link to an initial draft of 
> [CEP|https://docs.google.com/document/d/1_G-OZCAEmDyuQuAN2wQUYUtZBEJpMkHWnkYELLhqvKc/edit?usp=sharing].



--
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-16456) Add Plugin Support for CQLSH

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-16456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-16456:
--
Status: Ready to Commit  (was: Review In Progress)

> Add Plugin Support for CQLSH
> 
>
> Key: CASSANDRA-16456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16456
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Tool/cqlsh
>Reporter: Brian Houser
>Assignee: Brian Houser
>Priority: Normal
>  Labels: gsoc2021, mentor
>  Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> Currently the Cassandra drivers offer a plugin authenticator architecture for 
> the support of different authentication methods. This has been leveraged to 
> provide support for LDAP, Kerberos, and Sigv4 authentication. Unfortunately, 
> cqlsh, the included CLI tool, does not offer such support. Switching to a new 
> enhanced authentication scheme thus means being cut off from using cqlsh in 
> normal operation.
> We should have a means of using the same plugins and authentication providers 
> as the Python Cassandra driver.
> Here's a link to an initial draft of 
> [CEP|https://docs.google.com/document/d/1_G-OZCAEmDyuQuAN2wQUYUtZBEJpMkHWnkYELLhqvKc/edit?usp=sharing].



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17558) Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser accounts

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528743#comment-17528743
 ] 

Stefan Miklosovic commented on CASSANDRA-17558:
---

[~jmckenzie] can I make you a favor and rebase / merge this? Seems to be quite 
straightforward patch.

> Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser 
> accounts
> 
>
> Key: CASSANDRA-17558
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17558
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Guardrails
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
>
> While this can also be accomplished via roles, there's value in having a 
> cluster-wide "all role ban" on specific operations that operators can 
> configure for clusters that have need of those settings.
> In this case, we want the ability to completely disallow DROP or TRUNCATE 
> TABLE commands so users cannot inadvertently throw away data and operators 
> don't have to runbook managing roles to ensure that this functionality 
> doesn't leak through.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16718) Changing listen_address with prefer_local may lead to issues

[Brandon Williams (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528744#comment-17528744
 ] 

Brandon Williams commented on CASSANDRA-16718:
--

Yes and I don't imagine we will get one at this point until after 4.1 releases. 
 After that I will come back to this and see if it can be driven forward.

> Changing listen_address with prefer_local may lead to issues
> 
>
> Key: CASSANDRA-16718
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16718
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/Config
>Reporter: Jan Karlsson
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.11.x, 4.0.x
>
>
> Many container based solution function by assigning new listen_addresses when 
> nodes are stopped. Changing the listen_address is usually as simple as 
> turning off the node and changing the yaml file. 
> However, if prefer_local is enabled, I observed that nodes were unable to 
> join the cluster and fail with 'Unable to gossip with any seeds'. 
> Trace shows that the changing node will try to communicate with the existing 
> node but the response is never received. I assume it is because the existing 
> node attempts to communicate with the local address during the shadow round.
>  



--
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-17503) Request to port the DSE rebuild options to Cassandra

[Paul Ayers (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Ayers updated CASSANDRA-17503:
---
Resolution: Duplicate
Status: Resolved  (was: Open)

> Request to port the DSE rebuild options to Cassandra
> 
>
> Key: CASSANDRA-17503
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17503
> Project: Cassandra
>  Issue Type: New Feature
>Reporter: Paul Ayers
>Priority: High
> Fix For: 4.x
>
>
> Testing rebuild in C* 4.0.1, I ran into a scenario where 'nodetool rebuild' 
> was ran without any options in a new DC and the system.available_ranges_v2 
> table was populated such that every subsequent run of 'nodetool rebuild 
> ' streamed no data.
> The problem was that the first run looked at only the new DC so no data was 
> streamed, then the next run that provided the correct source DC still 
> resulted in no streamed data.
> Once the system.available_ranges_v2 table was truncated, rebuild worked as 
> expected.
> The request here is to include the same code that allows the following 
> options to be used in DSE so one could easily resolve this by using '-m 
> reset' in a similar scenario:
> -m, --mode mode
>  * normal - conventional behavior, streams only ranges that are not already 
> locally available
>  * refetch - resets locally available ranges, streams all ranges but leaves 
> current data untouched
>  * reset - resets the locally available ranges, removes all locally present 
> data (like a TRUNCATE), streams all ranges
>  * reset-no-snapshot - (like reset) resets the locally available ranges, 
> removes all locally present data (like a TRUNCATE), streams all ranges but 
> prevents a snapshot even if auto_snapshot is enabled
> Protecting against updating the available_ranges table if a local DC was 
> chosen might also be a good idea.



--
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-17571) Config upper bound should be handled earlier

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528792#comment-17528792
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17571:
-

Working to migrate the parameters to the extended classes so we can do upper 
bound (former int type Config parameters and overflow of big value bigger unit 
to smaller supported internally) checks in the constructors. Might be not most 
beautiful but at least we will be more consistent and less error-prone then 
utility methods in the DD. 

> Config upper bound should be handled earlier
> 
>
> Key: CASSANDRA-17571
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17571
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/Config
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.1
>
>
> Config upper bound should be handled on startup/config setup and not during 
> conversion



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-16310) Track top partitions (by size and tombstone count) and display in nodetool tablestats

[Marcus Eriksson (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528826#comment-17528826
 ] 

Marcus Eriksson commented on CASSANDRA-16310:
-

seems system schema mutation got > 20kb after top partitions table was added:
https://github.com/apache/cassandra-dtest/pull/189

https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1637/

[~bereng] could you review?

> Track top partitions (by size and tombstone count) and display in nodetool 
> tablestats
> -
>
> Key: CASSANDRA-16310
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16310
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Other
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 4.1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We should track the top partitions by size and tombstone count and display in 
> {{nodetool tablestats}}



--
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-17453) flaky in jvm CasCriticalSectionTest.criticalSectionTest

[Brandon Williams (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528827#comment-17528827
 ] 

Brandon Williams commented on CASSANDRA-17453:
--

+1

> flaky in jvm CasCriticalSectionTest.criticalSectionTest
> ---
>
> Key: CASSANDRA-17453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17453
> Project: Cassandra
>  Issue Type: Bug
>  Components: CI
>Reporter: Stefan Miklosovic
>Priority: Normal
>
> From CI, there are variations of this error:
> {code:java}
> org.apache.cassandra.exceptions.CasWriteTimeoutException: CAS operation timed 
> out: received 0 of 3 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.cas(Paxos.java:732) 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) {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-17583) Fix flaky test - org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest

[Brandon Williams (Jira)]

Brandon Williams created CASSANDRA-17583:


 Summary: Fix flaky test - 
org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest
 Key: CASSANDRA-17583
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17583
 Project: Cassandra
  Issue Type: Bug
Reporter: Brandon Williams


h3. Error Message

/127.0.0.3 appending to commitlog traces expected:<100> but was:<98>
h3. Stacktrace

junit.framework.AssertionFailedError: /127.0.0.3 appending to commitlog traces 
expected:<100> but was:<98> at 
org.apache.cassandra.distributed.test.MessageForwardingTest.lambda$mutationsForwardedToAllReplicasTest$8(MessageForwardingTest.java:92)
 at java.base/java.util.HashMap.forEach(HashMap.java:1336) at 
org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest(MessageForwardingTest.java:91)
 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method) at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)



--
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-17583) Fix flaky test - org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest

[Brandon Williams (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-17583:
-
Description: 
h3. Error Message

/127.0.0.3 appending to commitlog traces expected:<100> but was:<98>
h3. Stacktrace
{noformat}
junit.framework.AssertionFailedError: /127.0.0.3 appending to commitlog traces 
expected:<100> but was:<98> at 
org.apache.cassandra.distributed.test.MessageForwardingTest.lambda$mutationsForwardedToAllReplicasTest$8(MessageForwardingTest.java:92)
 at java.base/java.util.HashMap.forEach(HashMap.java:1336) at 
org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest(MessageForwardingTest.java:91)
 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method) at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
{noformat}

  was:
h3. Error Message

/127.0.0.3 appending to commitlog traces expected:<100> but was:<98>
h3. Stacktrace

junit.framework.AssertionFailedError: /127.0.0.3 appending to commitlog traces 
expected:<100> but was:<98> at 
org.apache.cassandra.distributed.test.MessageForwardingTest.lambda$mutationsForwardedToAllReplicasTest$8(MessageForwardingTest.java:92)
 at java.base/java.util.HashMap.forEach(HashMap.java:1336) at 
org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest(MessageForwardingTest.java:91)
 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method) at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)


> Fix flaky test - 
> org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest
> 
>
> Key: CASSANDRA-17583
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17583
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Brandon Williams
>Priority: Normal
>
> h3. Error Message
> /127.0.0.3 appending to commitlog traces expected:<100> but was:<98>
> h3. Stacktrace
> {noformat}
> junit.framework.AssertionFailedError: /127.0.0.3 appending to commitlog 
> traces expected:<100> but was:<98> at 
> org.apache.cassandra.distributed.test.MessageForwardingTest.lambda$mutationsForwardedToAllReplicasTest$8(MessageForwardingTest.java:92)
>  at java.base/java.util.HashMap.forEach(HashMap.java:1336) at 
> org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest(MessageForwardingTest.java:91)
>  at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method) at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}



--
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-17583) Fix flaky test - org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest

[Brandon Williams (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-17583:
-
 Bug Category: Parent values: Correctness(12982)Level 1 values: Test 
Failure(12990)
   Complexity: Normal
  Component/s: Messaging/Internode
Discovered By: Unit Test
Fix Version/s: 4.x
 Severity: Normal
   Status: Open  (was: Triage Needed)

> Fix flaky test - 
> org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest
> 
>
> Key: CASSANDRA-17583
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17583
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Internode
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.x
>
>
> h3. Error Message
> /127.0.0.3 appending to commitlog traces expected:<100> but was:<98>
> h3. Stacktrace
> {noformat}
> junit.framework.AssertionFailedError: /127.0.0.3 appending to commitlog 
> traces expected:<100> but was:<98> at 
> org.apache.cassandra.distributed.test.MessageForwardingTest.lambda$mutationsForwardedToAllReplicasTest$8(MessageForwardingTest.java:92)
>  at java.base/java.util.HashMap.forEach(HashMap.java:1336) at 
> org.apache.cassandra.distributed.test.MessageForwardingTest.mutationsForwardedToAllReplicasTest(MessageForwardingTest.java:91)
>  at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method) at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}



--
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 (2045fd07 -> 03e74866)

[git-site-role]

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 2045fd07 generate docs for 8fd077a6
 new 03e74866 generate docs for 8fd077a6

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   (2045fd07)
\
 N -- N -- N   refs/heads/asf-staging (03e74866)

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] [Created] (CASSANDRA-17584) Fix flay test - org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions

[Brandon Williams (Jira)]

Brandon Williams created CASSANDRA-17584:


 Summary: Fix flay test - 
org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions
 Key: CASSANDRA-17584
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17584
 Project: Cassandra
  Issue Type: Bug
  Components: Feature/Virtual Tables
Reporter: Brandon Williams


h3. Error Message

['LOAD' is expected to be null] expected: but was:
h3. Stacktrace

junit.framework.AssertionFailedError: ['LOAD' is expected to be null] 
expected: but was: at 
org.apache.cassandra.db.virtual.GossipInfoTableTest.assertValue(GossipInfoTableTest.java:174)
 at 
org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions(GossipInfoTableTest.java:96)



--
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-17584) Fix flay test - org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions

[Brandon Williams (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-17584:
-
 Bug Category: Parent values: Correctness(12982)Level 1 values: Test 
Failure(12990)
   Complexity: Normal
Discovered By: Unit Test
Fix Version/s: 4.x
 Severity: Normal
   Status: Open  (was: Triage Needed)

> Fix flay test - 
> org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions
> -
>
> Key: CASSANDRA-17584
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17584
> Project: Cassandra
>  Issue Type: Bug
>  Components: Feature/Virtual Tables
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.x
>
>
> h3. Error Message
> ['LOAD' is expected to be null] expected: but was:
> h3. Stacktrace
> junit.framework.AssertionFailedError: ['LOAD' is expected to be null] 
> expected: but was: at 
> org.apache.cassandra.db.virtual.GossipInfoTableTest.assertValue(GossipInfoTableTest.java:174)
>  at 
> org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions(GossipInfoTableTest.java:96)



--
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-17584) Fix flaky test - org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions

[Brandon Williams (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-17584:
-
Summary: Fix flaky test - 
org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions
  (was: Fix flay test - 
org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions)

> Fix flaky test - 
> org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions
> --
>
> Key: CASSANDRA-17584
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17584
> Project: Cassandra
>  Issue Type: Bug
>  Components: Feature/Virtual Tables
>Reporter: Brandon Williams
>Priority: Normal
> Fix For: 4.x
>
>
> h3. Error Message
> ['LOAD' is expected to be null] expected: but was:
> h3. Stacktrace
> junit.framework.AssertionFailedError: ['LOAD' is expected to be null] 
> expected: but was: at 
> org.apache.cassandra.db.virtual.GossipInfoTableTest.assertValue(GossipInfoTableTest.java:174)
>  at 
> org.apache.cassandra.db.virtual.GossipInfoTableTest.testSelectAllWithStateTransitions(GossipInfoTableTest.java:96)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17558) Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser accounts

[Josh McKenzie (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528848#comment-17528848
 ] 

Josh McKenzie commented on CASSANDRA-17558:
---

On my todo list to merge today; thanks though.

> Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser 
> accounts
> 
>
> Key: CASSANDRA-17558
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17558
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Guardrails
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
>
> While this can also be accomplished via roles, there's value in having a 
> cluster-wide "all role ban" on specific operations that operators can 
> configure for clusters that have need of those settings.
> In this case, we want the ability to completely disallow DROP or TRUNCATE 
> TABLE commands so users cannot inadvertently throw away data and operators 
> don't have to runbook managing roles to ensure that this functionality 
> doesn't leak through.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Updated] (CASSANDRA-17456) Test Failures: write_failures_test.TestMultiDCWriteFailures.test_oversized_mutation

[Josh McKenzie (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh McKenzie updated CASSANDRA-17456:
--
Status: Ready to Commit  (was: Review In Progress)

> Test Failures: 
> write_failures_test.TestMultiDCWriteFailures.test_oversized_mutation
> ---
>
> Key: CASSANDRA-17456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17456
> Project: Cassandra
>  Issue Type: Bug
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Aleksandr Sorokoumov
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1002/testReport/dtest-offheap.write_failures_test/TestMultiDCWriteFailures/test_oversized_mutation/
> {code:java}
> Error Message
> AssertionError: assert 0 == 8  +  where 8 =  JolokiaAgent.read_attribute of  0x7f1fca78dac0>>('org.apache.cassandra.metrics:type=Storage,name=TotalHints', 
> 'Count')  +where  > = 
> .read_attribute  +
> and   'org.apache.cassandra.metrics:type=Storage,name=TotalHints' = 
> make_mbean('metrics', type='Storage', name='TotalHints')
> Stacktrace
> self = 
> def test_oversized_mutation(self):
> """
> Test that multi-DC write failures return operation failed rather 
> than a timeout.
> @jira_ticket CASSANDRA-16334.
> """
> 
> cluster = self.cluster
> cluster.populate([2, 2])
> cluster.set_configuration_options(values={'max_mutation_size_in_kb': 
> 128})
> cluster.start()
> 
> node1 = cluster.nodelist()[0]
> session = self.patient_exclusive_cql_connection(node1)
> 
> session.execute("CREATE KEYSPACE k WITH replication = {'class': 
> 'NetworkTopologyStrategy', 'dc1': 2, 'dc2': 2}")
> session.execute("CREATE TABLE k.t (key int PRIMARY KEY, val blob)")
> 
> payload = '1' * 1024 * 256
> query = "INSERT INTO k.t (key, val) VALUES (1, 
> textAsBlob('{}'))".format(payload)
> 
> assert_write_failure(session, query, ConsistencyLevel.LOCAL_ONE)
> assert_write_failure(session, query, ConsistencyLevel.ONE)
> 
> # verify that no hints are created
> with JolokiaAgent(node1) as jmx:
> >   assert 0 == jmx.read_attribute(make_mbean('metrics', 
> > type='Storage', name='TotalHints'), 'Count')
> E   AssertionError: assert 0 == 8
> E+  where 8 =   0x7f1fca78dac0>>('org.apache.cassandra.metrics:type=Storage,name=TotalHints', 
> 'Count')
> E+where  > = 
> .read_attribute
> E+and   
> 'org.apache.cassandra.metrics:type=Storage,name=TotalHints' = 
> make_mbean('metrics', type='Storage', name='TotalHints')
> write_failures_test.py:277: AssertionError
> REST API
> CloudBees CI Client Controller 2.319.3.4-rolling
> {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17456) Test Failures: write_failures_test.TestMultiDCWriteFailures.test_oversized_mutation

[Josh McKenzie (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528861#comment-17528861
 ] 

Josh McKenzie commented on CASSANDRA-17456:
---

+1 here. We should maybe consider adding an entry to NEWS.txt to indicate the 
change from {{RuntimeException}} on {{MutationExceededMaxSizeException}} to 
{{{}InvalidRequestException{}}}.
 
I can't really imagine there's a lot of tooling in place out in the world that 
relies on the exception type being thrown on mutations exceeding max allowable 
sizes but stranger things have happened.

> Test Failures: 
> write_failures_test.TestMultiDCWriteFailures.test_oversized_mutation
> ---
>
> Key: CASSANDRA-17456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17456
> Project: Cassandra
>  Issue Type: Bug
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Aleksandr Sorokoumov
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1002/testReport/dtest-offheap.write_failures_test/TestMultiDCWriteFailures/test_oversized_mutation/
> {code:java}
> Error Message
> AssertionError: assert 0 == 8  +  where 8 =  JolokiaAgent.read_attribute of  0x7f1fca78dac0>>('org.apache.cassandra.metrics:type=Storage,name=TotalHints', 
> 'Count')  +where  > = 
> .read_attribute  +
> and   'org.apache.cassandra.metrics:type=Storage,name=TotalHints' = 
> make_mbean('metrics', type='Storage', name='TotalHints')
> Stacktrace
> self = 
> def test_oversized_mutation(self):
> """
> Test that multi-DC write failures return operation failed rather 
> than a timeout.
> @jira_ticket CASSANDRA-16334.
> """
> 
> cluster = self.cluster
> cluster.populate([2, 2])
> cluster.set_configuration_options(values={'max_mutation_size_in_kb': 
> 128})
> cluster.start()
> 
> node1 = cluster.nodelist()[0]
> session = self.patient_exclusive_cql_connection(node1)
> 
> session.execute("CREATE KEYSPACE k WITH replication = {'class': 
> 'NetworkTopologyStrategy', 'dc1': 2, 'dc2': 2}")
> session.execute("CREATE TABLE k.t (key int PRIMARY KEY, val blob)")
> 
> payload = '1' * 1024 * 256
> query = "INSERT INTO k.t (key, val) VALUES (1, 
> textAsBlob('{}'))".format(payload)
> 
> assert_write_failure(session, query, ConsistencyLevel.LOCAL_ONE)
> assert_write_failure(session, query, ConsistencyLevel.ONE)
> 
> # verify that no hints are created
> with JolokiaAgent(node1) as jmx:
> >   assert 0 == jmx.read_attribute(make_mbean('metrics', 
> > type='Storage', name='TotalHints'), 'Count')
> E   AssertionError: assert 0 == 8
> E+  where 8 =   0x7f1fca78dac0>>('org.apache.cassandra.metrics:type=Storage,name=TotalHints', 
> 'Count')
> E+where  > = 
> .read_attribute
> E+and   
> 'org.apache.cassandra.metrics:type=Storage,name=TotalHints' = 
> make_mbean('metrics', type='Storage', name='TotalHints')
> write_failures_test.py:277: AssertionError
> REST API
> CloudBees CI Client Controller 2.319.3.4-rolling
> {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] branch trunk updated: Add guardrail to disallow TRUNCATE and DROP TABLE commands

[jmckenzie]

This is an automated email from the ASF dual-hosted git repository.

jmckenzie pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git


The following commit(s) were added to refs/heads/trunk by this push:
 new 6bd373f5d2 Add guardrail to disallow TRUNCATE and DROP TABLE commands
6bd373f5d2 is described below

commit 6bd373f5d27754f80384caa31d1b2a4cfc43bc19
Author: Josh McKenzie 
AuthorDate: Mon Apr 18 14:53:17 2022 -0400

Add guardrail to disallow TRUNCATE and DROP TABLE commands

Patch by Josh McKenzie; reviewed by Aleksey Yeschenko for CASSANDRA-17558
---
 CHANGES.txt|  1 +
 conf/cassandra.yaml|  2 +
 src/java/org/apache/cassandra/config/Config.java   |  1 +
 .../apache/cassandra/config/GuardrailsOptions.java | 14 
 .../cql3/statements/TruncateStatement.java |  2 +
 .../cql3/statements/schema/DropTableStatement.java |  3 +
 .../apache/cassandra/db/guardrails/Guardrails.java | 17 
 .../cassandra/db/guardrails/GuardrailsConfig.java  |  7 ++
 .../cassandra/db/guardrails/GuardrailsMBean.java   | 12 +++
 .../db/guardrails/GuardrailTruncateDropTest.java   | 91 ++
 10 files changed, 150 insertions(+)

diff --git a/CHANGES.txt b/CHANGES.txt
index 7850ca8e5b..8a4e661719 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 4.1
+ * Add guardrail to disallow TRUNCATE and DROP TABLE commands (CASSANDRA-17558)
  * Add plugin support for CQLSH (CASSANDRA-16456)
  * Add guardrail to disallow querying with ALLOW FILTERING (CASSANDRA-17370)
  * Enhance SnakeYAML properties to be reusable outside of YAML parsing, 
support camel case conversion to snake case, and add support to ignore 
properties (CASSANDRA-17166)
diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index f6f0a3ccad..c3e183fbd3 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -1626,6 +1626,8 @@ drop_compact_storage_enabled: false
 # user_timestamps_enabled: true
 # Guardrail to allow/disallow GROUP BY functionality.
 # group_by_enabled: true
+# Guardrail to allow/disallow TRUNCATE and DROP statements
+# truncate_drop_enabled: true
 # Guardrail to warn or fail when using a page size greater than threshold.
 # The two thresholds default to -1 to disable.
 # page_size_warn_threshold: -1
diff --git a/src/java/org/apache/cassandra/config/Config.java 
b/src/java/org/apache/cassandra/config/Config.java
index a3d6348fa1..1c277cf0c7 100644
--- a/src/java/org/apache/cassandra/config/Config.java
+++ b/src/java/org/apache/cassandra/config/Config.java
@@ -808,6 +808,7 @@ public class Config
 public volatile Set write_consistency_levels_disallowed 
= Collections.emptySet();
 public volatile boolean user_timestamps_enabled = true;
 public volatile boolean group_by_enabled = true;
+public volatile boolean truncate_drop_enabled = true;
 public volatile boolean secondary_indexes_enabled = true;
 public volatile boolean uncompressed_tables_enabled = true;
 public volatile boolean compact_tables_enabled = true;
diff --git a/src/java/org/apache/cassandra/config/GuardrailsOptions.java 
b/src/java/org/apache/cassandra/config/GuardrailsOptions.java
index d32f3b1bc6..6654b4fc74 100644
--- a/src/java/org/apache/cassandra/config/GuardrailsOptions.java
+++ b/src/java/org/apache/cassandra/config/GuardrailsOptions.java
@@ -329,6 +329,20 @@ public class GuardrailsOptions implements GuardrailsConfig
   x -> config.group_by_enabled = x);
 }
 
+@Override
+public boolean getTruncateDropEnabled()
+{
+return config.truncate_drop_enabled;
+}
+
+public void setTruncateDropEnabled(boolean enabled)
+{
+updatePropertyWithLogging("truncate_drop_enabled",
+  enabled,
+  () -> config.truncate_drop_enabled,
+  x -> config.truncate_drop_enabled = x);
+}
+
 @Override
 public boolean getSecondaryIndexesEnabled()
 {
diff --git 
a/src/java/org/apache/cassandra/cql3/statements/TruncateStatement.java 
b/src/java/org/apache/cassandra/cql3/statements/TruncateStatement.java
index 2c1c9941ce..bdd4c7b870 100644
--- a/src/java/org/apache/cassandra/cql3/statements/TruncateStatement.java
+++ b/src/java/org/apache/cassandra/cql3/statements/TruncateStatement.java
@@ -25,6 +25,7 @@ import org.apache.cassandra.auth.Permission;
 import org.apache.cassandra.cql3.*;
 import org.apache.cassandra.db.ColumnFamilyStore;
 import org.apache.cassandra.db.Keyspace;
+import org.apache.cassandra.db.guardrails.Guardrails;
 import org.apache.cassandra.db.virtual.VirtualKeyspaceRegistry;
 import org.apache.cassandra.exceptions.*;
 import org.apache.cassandra.schema.Schema;
@@ -57,6 +58,7 @@ public class TruncateStatement extends QualifiedStatement 
implements CQLStatemen
 public void validate(ClientState state) throws InvalidRequestExcep

[jira] [Updated] (CASSANDRA-17558) Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser accounts

[Josh McKenzie (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh McKenzie updated CASSANDRA-17558:
--
  Fix Version/s: 4.1
Source Control Link: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=commit;h=6bd373f5d27754f80384caa31d1b2a4cfc43bc19
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

> Add guardrail to disallow DROP or TRUNCATE TABLE commands for non superuser 
> accounts
> 
>
> Key: CASSANDRA-17558
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17558
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Feature/Guardrails
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.1
>
>
> While this can also be accomplished via roles, there's value in having a 
> cluster-wide "all role ban" on specific operations that operators can 
> configure for clusters that have need of those settings.
> In this case, we want the ability to completely disallow DROP or TRUNCATE 
> TABLE commands so users cannot inadvertently throw away data and operators 
> don't have to runbook managing roles to ensure that this functionality 
> doesn't leak through.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17563) Fix CircleCI Midres config

[Josh McKenzie (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528869#comment-17528869
 ] 

Josh McKenzie commented on CASSANDRA-17563:
---

When I diff MIDRES pre and post {{20175bf77e2c6f72c25240ee445b583805a37630}} I 
get the following (along with vnode in-jvm changes I'd expect):
{code:java}
-  set -eo pipefail && circleci tests glob 
"$HOME/cassandra/test/distributed/**/*.java" 
"$HOME/cassandra/test/simulator/test/**/*.java" > /tmp/all_java_unit_tests.txt
+  set -eo pipefail && circleci tests glob 
"$HOME/cassandra/test/distributed/**/*.java" > /tmp/all_java_unit_tests.txt
{code}
Is this change (dropping simulator tests from all test enumeration, assuming 
I'm understanding this correctly) intentional?

> 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-17579) WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" + Liquidbase case study

[Diogenese Topper (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Diogenese Topper updated CASSANDRA-17579:
-
Test and Documentation Plan: 
* Add blog post titled "Liquibase is Ready to Support Cassandra 4.0 Users"
* Add entry to Blog page
* Add image for blog: 
"liquibase-is-ready-to-support-cassandra-4.0-users-unsplash-eden-constantino.jpg"
* Add Liquidbase case study
* Add entry to Cassandra Case Studies page
* Add Liquibase logo to images: "liquibase.svg"

  was:
* Add blog post titled "Liquibase is Ready to Support Cassandra 4.0 Users"
* Modify blog index page
* Add Liquidbase case study
* Modify case studies page


> WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" 
> + Liquidbase 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
>Priority: Normal
> Fix For: 4.0.x
>
>
> 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-17579) WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" + Liquibase case study

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated CASSANDRA-17579:
---
Labels: pull-request-available  (was: )

> 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
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0.x
>
>
> 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-17579) WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" + Liquibase case study

[Diogenese Topper (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Diogenese Topper updated CASSANDRA-17579:
-
Summary: WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 
4.0 Users" + Liquibase case study  (was: WEBSITE - April 2022 blog "Liquibase 
is Ready to Support Cassandra 4.0 Users" + Liquidbase case study)

> 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
>Priority: Normal
> Fix For: 4.0.x
>
>
> 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-17563) Fix CircleCI Midres config

[Ekaterina Dimitrova (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528884#comment-17528884
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17563:
-

They should be returned too. Only change from that patch should be adding the 
new in-jvm job with resources matching the ones used for the original in-jvm 
job on every level - lowres, midres and highres

> 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] [Commented] (CASSANDRA-17456) Test Failures: write_failures_test.TestMultiDCWriteFailures.test_oversized_mutation

[Josh McKenzie (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528893#comment-17528893
 ] 

Josh McKenzie commented on CASSANDRA-17456:
---

Follow up thought - this moves our check up the stack in terms of where we look 
for oversized mutations. Maybe we should add back in the size check in the 
{{CommitLog.add}} call as a kind of "last protection" (with a new log message 
to reflect the unexpected nature of seeing a large mutation there) in case of 
current unexpected paths or future changes that may introduce large mutations 
into the system?

> Test Failures: 
> write_failures_test.TestMultiDCWriteFailures.test_oversized_mutation
> ---
>
> Key: CASSANDRA-17456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17456
> Project: Cassandra
>  Issue Type: Bug
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Aleksandr Sorokoumov
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1002/testReport/dtest-offheap.write_failures_test/TestMultiDCWriteFailures/test_oversized_mutation/
> {code:java}
> Error Message
> AssertionError: assert 0 == 8  +  where 8 =  JolokiaAgent.read_attribute of  0x7f1fca78dac0>>('org.apache.cassandra.metrics:type=Storage,name=TotalHints', 
> 'Count')  +where  > = 
> .read_attribute  +
> and   'org.apache.cassandra.metrics:type=Storage,name=TotalHints' = 
> make_mbean('metrics', type='Storage', name='TotalHints')
> Stacktrace
> self = 
> def test_oversized_mutation(self):
> """
> Test that multi-DC write failures return operation failed rather 
> than a timeout.
> @jira_ticket CASSANDRA-16334.
> """
> 
> cluster = self.cluster
> cluster.populate([2, 2])
> cluster.set_configuration_options(values={'max_mutation_size_in_kb': 
> 128})
> cluster.start()
> 
> node1 = cluster.nodelist()[0]
> session = self.patient_exclusive_cql_connection(node1)
> 
> session.execute("CREATE KEYSPACE k WITH replication = {'class': 
> 'NetworkTopologyStrategy', 'dc1': 2, 'dc2': 2}")
> session.execute("CREATE TABLE k.t (key int PRIMARY KEY, val blob)")
> 
> payload = '1' * 1024 * 256
> query = "INSERT INTO k.t (key, val) VALUES (1, 
> textAsBlob('{}'))".format(payload)
> 
> assert_write_failure(session, query, ConsistencyLevel.LOCAL_ONE)
> assert_write_failure(session, query, ConsistencyLevel.ONE)
> 
> # verify that no hints are created
> with JolokiaAgent(node1) as jmx:
> >   assert 0 == jmx.read_attribute(make_mbean('metrics', 
> > type='Storage', name='TotalHints'), 'Count')
> E   AssertionError: assert 0 == 8
> E+  where 8 =   0x7f1fca78dac0>>('org.apache.cassandra.metrics:type=Storage,name=TotalHints', 
> 'Count')
> E+where  > = 
> .read_attribute
> E+and   
> 'org.apache.cassandra.metrics:type=Storage,name=TotalHints' = 
> make_mbean('metrics', type='Storage', name='TotalHints')
> write_failures_test.py:277: AssertionError
> REST API
> CloudBees CI Client Controller 2.319.3.4-rolling
> {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-13365) Nodes entering GC loop, does not recover

[Doug Whitfield (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528902#comment-17528902
 ] 

Doug Whitfield commented on CASSANDRA-13365:


Do we know if this is a problem in the 4.x series?

Also, I don't see any reference to a version after 3.11.3 and the last comment 
was in 2018. Do we think maybe this got fixed by accident with some of the 
other improvements?

> Nodes entering GC loop, does not recover
> 
>
> Key: CASSANDRA-13365
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13365
> Project: Cassandra
>  Issue Type: Bug
>  Components: Legacy/Core
> Environment: 34-node cluster over 4 DCs
> Linux CentOS 7.2 x86
> Mix of 64GB/128GB RAM / node
> Mix of 32/40 hardware threads / node, Xeon ~2.4Ghz
> High read volume, low write volume, occasional sstable bulk loading
>Reporter: Mina Naguib
>Priority: Normal
>
> Over the last week we've been observing two related problems affecting our 
> Cassandra cluster
> Problem 1: 1-few nodes per DC entering GC loop, not recovering
> Checking the heap usage stats, there's a sudden jump of 1-3GB. Some nodes 
> recover, but some don't and log this:
> {noformat}
> 2017-03-21T11:23:02.957-0400: 54099.519: [Full GC (Allocation Failure)  
> 13G->11G(14G), 29.4127307 secs]
> 2017-03-21T11:23:45.270-0400: 54141.833: [Full GC (Allocation Failure)  
> 13G->12G(14G), 28.1561881 secs]
> 2017-03-21T11:24:20.307-0400: 54176.869: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.7019501 secs]
> 2017-03-21T11:24:50.528-0400: 54207.090: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.1372267 secs]
> 2017-03-21T11:25:19.190-0400: 54235.752: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.0703975 secs]
> 2017-03-21T11:25:46.711-0400: 54263.273: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.3187768 secs]
> 2017-03-21T11:26:15.419-0400: 54291.981: [Full GC (Allocation Failure)  
> 13G->13G(14G), 26.9493405 secs]
> 2017-03-21T11:26:43.399-0400: 54319.961: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.5222085 secs]
> 2017-03-21T11:27:11.383-0400: 54347.945: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.1769581 secs]
> 2017-03-21T11:27:40.174-0400: 54376.737: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.4639031 secs]
> 2017-03-21T11:28:08.946-0400: 54405.508: [Full GC (Allocation Failure)  
> 13G->13G(14G), 30.3480523 secs]
> 2017-03-21T11:28:40.117-0400: 54436.680: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.8220513 secs]
> 2017-03-21T11:29:08.459-0400: 54465.022: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.4691271 secs]
> 2017-03-21T11:29:37.114-0400: 54493.676: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.0275733 secs]
> 2017-03-21T11:30:04.635-0400: 54521.198: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.1902627 secs]
> 2017-03-21T11:30:32.114-0400: 54548.676: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.8872850 secs]
> 2017-03-21T11:31:01.430-0400: 54577.993: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.1609706 secs]
> 2017-03-21T11:31:29.024-0400: 54605.587: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.3635138 secs]
> 2017-03-21T11:31:57.303-0400: 54633.865: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.4143510 secs]
> 2017-03-21T11:32:25.110-0400: 54661.672: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.8595986 secs]
> 2017-03-21T11:32:53.922-0400: 54690.485: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.5242543 secs]
> 2017-03-21T11:33:21.867-0400: 54718.429: [Full GC (Allocation Failure)  
> 13G->13G(14G), 30.8930130 secs]
> 2017-03-21T11:33:53.712-0400: 54750.275: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.6523013 secs]
> 2017-03-21T11:34:21.760-0400: 54778.322: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.3030198 secs]
> 2017-03-21T11:34:50.073-0400: 54806.635: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.1594154 secs]
> 2017-03-21T11:35:17.743-0400: 54834.306: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.3766949 secs]
> 2017-03-21T11:35:45.797-0400: 54862.360: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.5756770 secs]
> 2017-03-21T11:36:13.816-0400: 54890.378: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.5541813 secs]
> 2017-03-21T11:36:41.926-0400: 54918.488: [Full GC (Allocation Failure)  
> 13G->13G(14G), 33.7510103 secs]
> 2017-03-21T11:37:16.132-0400: 54952.695: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.4856611 secs]
> 2017-03-21T11:37:44.454-0400: 54981.017: [Full GC (Allocation Failure)  
> 13G->13G(14G), 28.1269335 secs]
> 2017-03-21T11:38:12.774-0400: 55009.337: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.7830448 secs]
> 2017-03-21T11:38:40.840-0400: 55037.402: [Full GC (Allocation Failure)  
> 13G->13G(14G), 27.3527326 secs]
> 2017-03-21T11

[jira] [Commented] (CASSANDRA-17180) Implement startup check to prevent Cassandra start to spread zombie data

[Josh McKenzie (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528907#comment-17528907
 ] 

Josh McKenzie commented on CASSANDRA-17180:
---

{quote}I was thinking about enablement by default and I do not want to enable 
it by default yet.
{quote}
My .02: I agree w/you re: keeping this disabled by default.

Ultimately a marker file that we use to parse if a node did anything within 
gc_grace is all just a symptom of a bigger problem: us relying on gc_grace to 
determine a window of time after which it's safe to delete tombstones. The 
fundamental design is deeply, _deeply_ flawed. While this ticket here will 
provide an optional band-aid for operators for certain use-cases to prevent 
zombie data, I'd like to see us tackle this design in a more holistic fashion 
that makes tickets like this unnecessary and makes purging more deterministic.

Been on my mind for a bit and I planned to bring it up on the ML after 4.1 
branch and test burn down.

> Implement startup check to prevent Cassandra start to spread zombie data
> 
>
> Key: CASSANDRA-17180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17180
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Legacy/Observability
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1
>
>  Time Spent: 11h 20m
>  Remaining Estimate: 0h
>
> As already discussed on ML, it would be nice to have a service which would 
> periodically write timestamp to a file signalling it is up / running.
> Then, on the startup, we would read this file and we would determine if there 
> is some table which gc grace is behind this time and we would fail the start 
> so we would prevent zombie data to be likely spread around a cluster.
> https://lists.apache.org/thread/w4w5t2hlcrvqhgdwww61hgg58qz13glw



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17456) Test Failures: write_failures_test.TestMultiDCWriteFailures.test_oversized_mutation

[Benedict Elliott Smith (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528932#comment-17528932
 ] 

Benedict Elliott Smith commented on CASSANDRA-17456:


I haven't looked at the patch, but worth noting we should not remove the size 
check on CommitLog without permitting the allocation of a dedicated segment for 
the record.

> Test Failures: 
> write_failures_test.TestMultiDCWriteFailures.test_oversized_mutation
> ---
>
> Key: CASSANDRA-17456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17456
> Project: Cassandra
>  Issue Type: Bug
>  Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Aleksandr Sorokoumov
>Priority: Normal
> Fix For: 4.x
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1002/testReport/dtest-offheap.write_failures_test/TestMultiDCWriteFailures/test_oversized_mutation/
> {code:java}
> Error Message
> AssertionError: assert 0 == 8  +  where 8 =  JolokiaAgent.read_attribute of  0x7f1fca78dac0>>('org.apache.cassandra.metrics:type=Storage,name=TotalHints', 
> 'Count')  +where  > = 
> .read_attribute  +
> and   'org.apache.cassandra.metrics:type=Storage,name=TotalHints' = 
> make_mbean('metrics', type='Storage', name='TotalHints')
> Stacktrace
> self = 
> def test_oversized_mutation(self):
> """
> Test that multi-DC write failures return operation failed rather 
> than a timeout.
> @jira_ticket CASSANDRA-16334.
> """
> 
> cluster = self.cluster
> cluster.populate([2, 2])
> cluster.set_configuration_options(values={'max_mutation_size_in_kb': 
> 128})
> cluster.start()
> 
> node1 = cluster.nodelist()[0]
> session = self.patient_exclusive_cql_connection(node1)
> 
> session.execute("CREATE KEYSPACE k WITH replication = {'class': 
> 'NetworkTopologyStrategy', 'dc1': 2, 'dc2': 2}")
> session.execute("CREATE TABLE k.t (key int PRIMARY KEY, val blob)")
> 
> payload = '1' * 1024 * 256
> query = "INSERT INTO k.t (key, val) VALUES (1, 
> textAsBlob('{}'))".format(payload)
> 
> assert_write_failure(session, query, ConsistencyLevel.LOCAL_ONE)
> assert_write_failure(session, query, ConsistencyLevel.ONE)
> 
> # verify that no hints are created
> with JolokiaAgent(node1) as jmx:
> >   assert 0 == jmx.read_attribute(make_mbean('metrics', 
> > type='Storage', name='TotalHints'), 'Count')
> E   AssertionError: assert 0 == 8
> E+  where 8 =   0x7f1fca78dac0>>('org.apache.cassandra.metrics:type=Storage,name=TotalHints', 
> 'Count')
> E+where  > = 
> .read_attribute
> E+and   
> 'org.apache.cassandra.metrics:type=Storage,name=TotalHints' = 
> make_mbean('metrics', type='Storage', name='TotalHints')
> write_failures_test.py:277: AssertionError
> REST API
> CloudBees CI Client Controller 2.319.3.4-rolling
> {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] branch cassandra-3.0 updated: Schema mutations may not be completed on drain

[jonmeredith]

This is an automated email from the ASF dual-hosted git repository.

jonmeredith pushed a commit to branch cassandra-3.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git


The following commit(s) were added to refs/heads/cassandra-3.0 by this push:
 new 2fdbda6ac9 Schema mutations may not be completed on drain
2fdbda6ac9 is described below

commit 2fdbda6ac98f161513f80e7bbab4ea8ca1c8528a
Author: Jon Meredith 
AuthorDate: Tue Apr 26 10:16:07 2022 -0600

Schema mutations may not be completed on drain

patch by Jon Meredith; reviewed by Caleb Rackliffe for CASSANDRA-17524
---
 CHANGES.txt   | 1 +
 src/java/org/apache/cassandra/service/StorageService.java | 6 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/CHANGES.txt b/CHANGES.txt
index c481d73fd2..e74b2cba35 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 3.0.27
+ * Schema mutations may not be completed on drain (CASSANDRA-17524)
  * Fix data corruption in AbstractCompositeType due to static boolean byte 
buffers (CASSANDRA-14752)
  * Add procps dependency to RPM/Debian packages (CASSANDRA-17516)
  * Suppress CVE-2021-44521 (CASSANDRA-17492)
diff --git a/src/java/org/apache/cassandra/service/StorageService.java 
b/src/java/org/apache/cassandra/service/StorageService.java
index 22040c1fed..c78bb0803c 100644
--- a/src/java/org/apache/cassandra/service/StorageService.java
+++ b/src/java/org/apache/cassandra/service/StorageService.java
@@ -4334,10 +4334,12 @@ public class StorageService extends 
NotificationBroadcasterSupport implements IE
 ExecutorService counterMutationStage = 
StageManager.getStage(Stage.COUNTER_MUTATION);
 ExecutorService viewMutationStage = 
StageManager.getStage(Stage.VIEW_MUTATION);
 ExecutorService mutationStage = StageManager.getStage(Stage.MUTATION);
+ExecutorService gossipStage = StageManager.getStage(Stage.GOSSIP);
 
 if (mutationStage.isTerminated()
 && counterMutationStage.isTerminated()
-&& viewMutationStage.isTerminated())
+&& viewMutationStage.isTerminated()
+&& gossipStage.isTerminated())
 {
 if (!isFinalShutdown)
 logger.warn("Cannot drain node (did it already happen?)");
@@ -4380,9 +4382,11 @@ public class StorageService extends 
NotificationBroadcasterSupport implements IE
 viewMutationStage.shutdown();
 counterMutationStage.shutdown();
 mutationStage.shutdown();
+gossipStage.shutdown();
 viewMutationStage.awaitTermination(3600, TimeUnit.SECONDS);
 counterMutationStage.awaitTermination(3600, TimeUnit.SECONDS);
 mutationStage.awaitTermination(3600, TimeUnit.SECONDS);
+gossipStage.awaitTermination(3600, TimeUnit.SECONDS);
 
 StorageProxy.instance.verifyNoHintsInProgress();
 


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] branch cassandra-4.0 updated (018c8e0d5e -> 2405d523fa)

[jonmeredith]

This is an automated email from the ASF dual-hosted git repository.

jonmeredith pushed a change to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git


from 018c8e0d5e Optimise BTree build, update and transform operations
 new 2fdbda6ac9 Schema mutations may not be completed on drain
 new 804098e68b Merge branch 'cassandra-3.0' into cassandra-3.11
 new 2405d523fa Merge branch 'cassandra-3.11' into cassandra-4.0

The 3 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 +
 .../org/apache/cassandra/concurrent/Stage.java | 55 --
 .../config/CassandraRelevantProperties.java|  7 +++
 .../apache/cassandra/service/StorageService.java   | 19 ++--
 .../distributed/test/ring/AutoBootstrapTest.java   |  5 +-
 5 files changed, 58 insertions(+), 30 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] 01/01: Merge branch 'cassandra-3.0' into cassandra-3.11

[jonmeredith]

This is an automated email from the ASF dual-hosted git repository.

jonmeredith pushed a commit to branch cassandra-3.11
in repository https://gitbox.apache.org/repos/asf/cassandra.git

commit 804098e68be0f60e495715f745987b364a2e82d9
Merge: eeb89ea53b 2fdbda6ac9
Author: Jon Meredith 
AuthorDate: Wed Apr 27 11:59:52 2022 -0600

Merge branch 'cassandra-3.0' into cassandra-3.11

 CHANGES.txt   | 1 +
 src/java/org/apache/cassandra/service/StorageService.java | 6 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --cc CHANGES.txt
index 18ff521946,e74b2cba35..66b114a379
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,11 -1,5 +1,12 @@@
 -3.0.27
 +3.11.13
 + * Upgrade slf4j to 1.7.25 (CASSANDRA-17474)
 + * Upgrade jackson to 2.13.2 (CASSANDRA-17492)
 + * emit warning on keyspace creation when replication factor is bigger than 
the number of nodes (CASSANDRA-16747)
 + * Fix snapshot true size calculation (CASSANDRA-17267)
 + * Validate existence of DCs when repairing (CASSANDRA-17407)
 + * dropping of a materialized view creates a snapshot with dropped- prefix 
(CASSANDRA-17415)
 +Merged from 3.0:
+  * Schema mutations may not be completed on drain (CASSANDRA-17524)
   * Fix data corruption in AbstractCompositeType due to static boolean byte 
buffers (CASSANDRA-14752)
   * Add procps dependency to RPM/Debian packages (CASSANDRA-17516)
   * Suppress CVE-2021-44521 (CASSANDRA-17492)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] branch cassandra-3.11 updated (eeb89ea53b -> 804098e68b)

[jonmeredith]

This is an automated email from the ASF dual-hosted git repository.

jonmeredith pushed a change to branch cassandra-3.11
in repository https://gitbox.apache.org/repos/asf/cassandra.git


from eeb89ea53b Merge branch 'cassandra-3.0' into cassandra-3.11
 new 2fdbda6ac9 Schema mutations may not be completed on drain
 new 804098e68b Merge branch 'cassandra-3.0' into cassandra-3.11

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   | 1 +
 src/java/org/apache/cassandra/service/StorageService.java | 6 +-
 2 files changed, 6 insertions(+), 1 deletion(-)


-
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-3.11' into cassandra-4.0

[jonmeredith]

This is an automated email from the ASF dual-hosted git repository.

jonmeredith pushed a commit to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git

commit 2405d523fa44d1379b4dd1df0874919299b00c44
Merge: 018c8e0d5e 804098e68b
Author: Jon Meredith 
AuthorDate: Wed Apr 27 12:01:42 2022 -0600

Merge branch 'cassandra-3.11' into cassandra-4.0

 CHANGES.txt|  2 +
 .../org/apache/cassandra/concurrent/Stage.java | 55 --
 .../config/CassandraRelevantProperties.java|  7 +++
 .../apache/cassandra/service/StorageService.java   | 19 ++--
 .../distributed/test/ring/AutoBootstrapTest.java   |  5 +-
 5 files changed, 58 insertions(+), 30 deletions(-)

diff --cc CHANGES.txt
index 7a83979055,66b114a379..8b59569491
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,25 -1,12 +1,27 @@@
 -3.11.13
 - * Upgrade slf4j to 1.7.25 (CASSANDRA-17474)
 - * Upgrade jackson to 2.13.2 (CASSANDRA-17492)
 +4.0.5
 + * Optimise BTree build,update and transform operations (CASSANDRA-15510)
++Merged from 3.0:
++ * Schema mutations may not be completed on drain (CASSANDRA-17524)
 +
 +4.0.4
 + * Clean up schema migration coordinator and tests (CASSANDRA-17533)
 + * Shut repair task executor down without interruption to avoid compromising 
shared channel proxies (CASSANDRA-17466)
 + * Generate valid KEYSPACE / MATERIALIZED VIEW for CQL for views 
(CASSANDRA-17266)
 + * Fix timestamp tz parsing (CASSANDRA-17467)
 + * Suppress CVE-2021-44521 from driver (CASSANDRA-17459)
 + * Upgrade jackson to 2.13.2 (CASSANDRA-17460)
 + * Make sstableloader honour native port option (CASSANDRA-17210)
 + * Reject snapshot names with special character (CASSANDRA-15297)
 + * Fix ObjectSizes implementation and usages (CASSANDRA-17402)
 + * Fix race condition bug during local session repair (CASSANDRA-17335)
 + * Fix ignored streaming encryption settings in sstableloader 
(CASSANDRA-17367)
 + * Streaming tasks handle empty SSTables correctly (CASSANDRA-16349)
 + * Prevent SSTableLoader from doing unnecessary work (CASSANDRA-16349)
   * emit warning on keyspace creation when replication factor is bigger than 
the number of nodes (CASSANDRA-16747)
   * Fix snapshot true size calculation (CASSANDRA-17267)
 - * Validate existence of DCs when repairing (CASSANDRA-17407)
   * dropping of a materialized view creates a snapshot with dropped- prefix 
(CASSANDRA-17415)
 + * Validate existence of DCs when repairing (CASSANDRA-17407)
  Merged from 3.0:
 - * Schema mutations may not be completed on drain (CASSANDRA-17524)
   * Fix data corruption in AbstractCompositeType due to static boolean byte 
buffers (CASSANDRA-14752)
   * Add procps dependency to RPM/Debian packages (CASSANDRA-17516)
   * Suppress CVE-2021-44521 (CASSANDRA-17492)
diff --cc src/java/org/apache/cassandra/concurrent/Stage.java
index e00da7b0cc,ccb156501e..5efaf16cf6
--- a/src/java/org/apache/cassandra/concurrent/Stage.java
+++ b/src/java/org/apache/cassandra/concurrent/Stage.java
@@@ -49,229 -24,60 +49,256 @@@ import static java.util.stream.Collecto
  
  public enum Stage
  {
- READ  ("ReadStage", "request",  
DatabaseDescriptor::getConcurrentReaders,
DatabaseDescriptor::setConcurrentReaders,
Stage::multiThreadedLowSignalStage),
- MUTATION  ("MutationStage", "request",  
DatabaseDescriptor::getConcurrentWriters,
DatabaseDescriptor::setConcurrentWriters,
Stage::multiThreadedLowSignalStage),
- COUNTER_MUTATION  ("CounterMutationStage",  "request",  
DatabaseDescriptor::getConcurrentCounterWriters, 
DatabaseDescriptor::setConcurrentCounterWriters, 
Stage::multiThreadedLowSignalStage),
- VIEW_MUTATION ("ViewMutationStage", "request",  
DatabaseDescriptor::getConcurrentViewWriters,
DatabaseDescriptor::setConcurrentViewWriters,
Stage::multiThreadedLowSignalStage),
- GOSSIP("GossipStage",   "internal", () -> 1,  
   null,
Stage::singleThreadedStage),
- REQUEST_RESPONSE  ("RequestResponseStage",  "request",  
FBUtilities::getAvailableProcessors, null,  
  Stage::multiThreadedLowSignalStage),
- ANTI_ENTROPY  ("AntiEntropyStage",  "internal", () -> 1,  
   null,
Stage::singleThreadedStage),
- MIGRATION ("MigrationStage","internal", () -> 1,  
   null,
Stage::singleThreadedStage),
- MISC  ("MiscStage", "internal", () -> 1,  
   null,
Stage::singleThreadedStage),
- TRACING   ("TracingStage",  "internal", () -> 1,  

[cassandra] branch trunk updated (6bd373f5d2 -> 0c37176673)

[jonmeredith]

This is an automated email from the ASF dual-hosted git repository.

jonmeredith pushed a change to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git


from 6bd373f5d2 Add guardrail to disallow TRUNCATE and DROP TABLE commands
 new 2fdbda6ac9 Schema mutations may not be completed on drain
 new 804098e68b Merge branch 'cassandra-3.0' into cassandra-3.11
 new 2405d523fa Merge branch 'cassandra-3.11' into cassandra-4.0
 new 0c37176673 Merge branch 'cassandra-4.0' into trunk

The 4 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|  1 +
 .../org/apache/cassandra/concurrent/Stage.java | 55 --
 .../config/CassandraRelevantProperties.java|  5 ++
 .../apache/cassandra/service/StorageService.java   | 19 ++--
 .../distributed/test/ring/AutoBootstrapTest.java   |  5 +-
 5 files changed, 55 insertions(+), 30 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra] 01/01: Merge branch 'cassandra-4.0' into trunk

[jonmeredith]

This is an automated email from the ASF dual-hosted git repository.

jonmeredith pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git

commit 0c37176673ca71a75990a26e421b5991db6eefe1
Merge: 6bd373f5d2 2405d523fa
Author: Jon Meredith 
AuthorDate: Wed Apr 27 12:03:44 2022 -0600

Merge branch 'cassandra-4.0' into trunk

 CHANGES.txt|  1 +
 .../org/apache/cassandra/concurrent/Stage.java | 55 --
 .../config/CassandraRelevantProperties.java|  5 ++
 .../apache/cassandra/service/StorageService.java   | 19 ++--
 .../distributed/test/ring/AutoBootstrapTest.java   |  5 +-
 5 files changed, 55 insertions(+), 30 deletions(-)

diff --cc CHANGES.txt
index 8a4e661719,8b59569491..3f3a782cc3
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -216,25 -75,7 +216,26 @@@ Merged from 3.11
   * Add key validation to ssstablescrub (CASSANDRA-16969)
   * Update Jackson from 2.9.10 to 2.12.5 (CASSANDRA-16851)
   * Make assassinate more resilient to missing tokens (CASSANDRA-16847)
 + * Validate SASI tokenizer options before adding index to schema 
(CASSANDRA-15135)
 + * Fixup scrub output when no data post-scrub and clear up old use of row, 
which really means partition (CASSANDRA-16835)
 + * Reduce thread contention in CommitLogSegment and HintsBuffer 
(CASSANDRA-16072)
 + * Make cqlsh use the same set of reserved keywords than the server uses 
(CASSANDRA-15663)
 + * Optimize bytes skipping when reading SSTable files (CASSANDRA-14415)
 + * Enable tombstone compactions when unchecked_tombstone_compaction is set in 
TWCS (CASSANDRA-14496)
 + * Read only the required SSTables for single partition queries 
(CASSANDRA-16737)
  Merged from 3.0:
++ * Schema mutations may not be completed on drain (CASSANDRA-17524)
 + * Fix data corruption in AbstractCompositeType due to static boolean byte 
buffers (CASSANDRA-14752)
 + * Add procps dependency to RPM/Debian packages (CASSANDRA-17516)
 + * Suppress CVE-2021-44521 (CASSANDRA-17492)
 + * ConnectionLimitHandler may leaks connection count if remote connection 
drops (CASSANDRA-17252)
 + * Require ant >= 1.10 (CASSANDRA-17428)
 + * Disallow CONTAINS for UPDATE and DELETE (CASSANDRA-15266)
 + * Suppress inapplicable CVEs (CASSANDRA-17368)
 + * Fix flaky test - test_cqlsh_completion.TestCqlshCompletion 
(CASSANDRA-17338)
 + * Fixed TestCqlshOutput failing tests (CASSANDRA-17386)
 + * Lazy transaction log replica creation allows incorrect replica content 
divergence during anticompaction (CASSANDRA-17273)
 + * LeveledCompactionStrategy disk space check improvements (CASSANDRA-17272)
   * Fix conversion from megabits to bytes in streaming rate limiter 
(CASSANDRA-17243)
   * Upgrade logback to 1.2.9 (CASSANDRA-17204)
   * Avoid race in AbstractReplicationStrategy endpoint caching 
(CASSANDRA-16673)
diff --cc src/java/org/apache/cassandra/concurrent/Stage.java
index 1c15e4505a,5efaf16cf6..ac609aa774
--- a/src/java/org/apache/cassandra/concurrent/Stage.java
+++ b/src/java/org/apache/cassandra/concurrent/Stage.java
@@@ -42,29 -49,35 +42,36 @@@ import static org.apache.cassandra.conc
  
  public enum Stage
  {
- READ  ("ReadStage", "request",  
DatabaseDescriptor::getConcurrentReaders,
DatabaseDescriptor::setConcurrentReaders,
Stage::multiThreadedLowSignalStage),
- MUTATION  ("MutationStage", "request",  
DatabaseDescriptor::getConcurrentWriters,
DatabaseDescriptor::setConcurrentWriters,
Stage::multiThreadedLowSignalStage),
- COUNTER_MUTATION  ("CounterMutationStage",  "request",  
DatabaseDescriptor::getConcurrentCounterWriters, 
DatabaseDescriptor::setConcurrentCounterWriters, 
Stage::multiThreadedLowSignalStage),
- VIEW_MUTATION ("ViewMutationStage", "request",  
DatabaseDescriptor::getConcurrentViewWriters,
DatabaseDescriptor::setConcurrentViewWriters,
Stage::multiThreadedLowSignalStage),
- GOSSIP("GossipStage",   "internal", () -> 1,  
   null,
Stage::singleThreadedStage),
- REQUEST_RESPONSE  ("RequestResponseStage",  "request",  
FBUtilities::getAvailableProcessors, null,  
  Stage::multiThreadedLowSignalStage),
- ANTI_ENTROPY  ("AntiEntropyStage",  "internal", () -> 1,  
   null,
Stage::singleThreadedStage),
- MIGRATION ("MigrationStage","internal", () -> 1,  
   null,
Stage::migrationStage),
- MISC  ("MiscStage", "internal", () -> 1,  
   null,
Stage::singleThreadedStage),
- TRACING   ("TracingStage",  "internal"

[jira] [Updated] (CASSANDRASC-36) Support for ErrorHandler route in Sidecar

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRASC-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated CASSANDRASC-36:
--
Labels: pull-request-available  (was: )

> Support for ErrorHandler route in Sidecar
> -
>
> Key: CASSANDRASC-36
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-36
> Project: Sidecar for Apache Cassandra
>  Issue Type: Improvement
>  Components: Configuration
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
>  Labels: pull-request-available
>
> Add a default {{Route#failureHandler()}} that returns a {{JSON}} 
> representation of the error for {{io.vertx.ext.web.handler.HttpException}}  
> as well as {{REQUEST_TIMEOUT}} errors.
> Additionally, we need to allow for custom implementations of the 
> {{ErrorHandler}} interface to be injected. Downstream projects can provide 
> custom implementations of the {{ErrorHandler}} to fit the needs of the 
> project.



--
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-17524) Schema mutations may not be completed on drain

[Jon Meredith (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jon Meredith updated CASSANDRA-17524:
-
  Fix Version/s: 3.0.27
 3.11.13
 4.0.4
 (was: 3.0.x)
 (was: 3.11.x)
 (was: 4.0.x)
  Since Version: 3.0.0
Source Control Link: 
https://github.com/apache/cassandra/commit/651876f5165072a41ab3e40c474500bfa8b73a7a
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

> Schema mutations may not be completed on drain
> --
>
> Key: CASSANDRA-17524
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17524
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/Startup and Shutdown
>Reporter: Jon Meredith
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 3.0.27, 3.11.13, 4.1, 4.0.4
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> The drain logic (invoked explicitly with nodetool or from the JVM
> shutdown hook) closes down executor stages that can create mutations (counter,
> view, mutation) before closing down the commitlog. The gossip
> stage also commits schema mutations, and should be treated the same way.
> The messaging service is shut down as part of drain, so there should be
> no new Gossip messages received, however any messages still queued
> in the executor could still run after the commitlog allocator is shut down as
> part of drain, causing the gossip stage thread to hang indefinitely waiting
> for a new segment that never arrives.
> Here is an example from an in-JVM dtest, showing an update to the peers table 
> as it shuts down.
> {code:java}
> park:-1, Unsafe (jdk.internal.misc)
> park:323, LockSupport (java.util.concurrent.locks)
> await:289, WaitQueue$Standard$AbstractSignal 
> (org.apache.cassandra.utils.concurrent)
> await:282, WaitQueue$Standard$AbstractSignal 
> (org.apache.cassandra.utils.concurrent)
> awaitUninterruptibly:186, Awaitable$Defaults 
> (org.apache.cassandra.utils.concurrent)
> awaitUninterruptibly:259, Awaitable$AbstractAwaitable 
> (org.apache.cassandra.utils.concurrent)
> awaitAvailableSegment:283, AbstractCommitLogSegmentManager 
> (org.apache.cassandra.db.commitlog)
> advanceAllocatingFrom:257, AbstractCommitLogSegmentManager 
> (org.apache.cassandra.db.commitlog)
> allocate:55, CommitLogSegmentManagerStandard 
> (org.apache.cassandra.db.commitlog)
> add:282, CommitLog (org.apache.cassandra.db.commitlog)
> beginWrite:50, CassandraKeyspaceWriteHandler (org.apache.cassandra.db)
> applyInternal:622, Keyspace (org.apache.cassandra.db)
> apply:506, Keyspace (org.apache.cassandra.db)
> apply:215, Mutation (org.apache.cassandra.db)
> apply:220, Mutation (org.apache.cassandra.db)
> apply:229, Mutation (org.apache.cassandra.db)
> executeInternalWithoutCondition:644, ModificationStatement 
> (org.apache.cassandra.cql3.statements)
> executeLocally:635, ModificationStatement 
> (org.apache.cassandra.cql3.statements)
> executeInternal:431, QueryProcessor (org.apache.cassandra.cql3)
> updateTokens:804, SystemKeyspace (org.apache.cassandra.db)
> updateTokenMetadata:2941, StorageService (org.apache.cassandra.service)
> handleStateNormal:3057, StorageService (org.apache.cassandra.service)
> onChange:2498, StorageService (org.apache.cassandra.service)
> markAsShutdown:607, Gossiper (org.apache.cassandra.gms)
> doVerb:39, GossipShutdownVerbHandler (org.apache.cassandra.gms)
> lambda$new$0:78, InboundSink (org.apache.cassandra.net)
> accept:-1, 581110313 (org.apache.cassandra.net.InboundSink$$Lambda$2638)
> accept:64, InboundSink$Filtered (org.apache.cassandra.net)
> accept:50, InboundSink$Filtered (org.apache.cassandra.net)
> accept:97, InboundSink (org.apache.cassandra.net)
> accept:45, InboundSink (org.apache.cassandra.net)
> run:433, InboundMessageHandler$ProcessMessage (org.apache.cassandra.net)
> run:124, ExecutionFailure$1 (org.apache.cassandra.concurrent)
> runWorker:1128, ThreadPoolExecutor (java.util.concurrent)
> run:628, ThreadPoolExecutor$Worker (java.util.concurrent)
> run:30, FastThreadLocalRunnable (io.netty.util.concurrent)
> run:829, Thread (java.lang)
> {code}
> This causes an exception during shutdown for the in-JVM dtest as it is
> unable to shutdown {{{}Stage.GOSSIP{}}}, but does not prevent regular
> shutdown for Cassandra as the executors are not stopped. The schema update
> would be lost, despite requesting a graceful shutdown.



--
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-14582) Add a system property to set the cassandra hostId if not yet initialized

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-14582:
--
Resolution: (was: Fixed)
Status: Open  (was: Resolved)

> Add a system property to set the cassandra hostId if not yet initialized
> 
>
> Key: CASSANDRA-14582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config
>Reporter: vincent royer
>Assignee: Abuli Palagashvili
>Priority: Low
>  Labels: lhf
> Fix For: 4.1
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Add a system property *cassandra.host_id* to set the cassandra hostId if not 
> yet initialized.
> This allow to push the cassandra host ID when provisioning new cassandra 
> nodes rather than to retreive it after the first start.



--
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-14582) Add a system property to set the cassandra hostId if not yet initialized

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic reassigned CASSANDRA-14582:
-

Assignee: Stefan Miklosovic  (was: Abuli Palagashvili)

> Add a system property to set the cassandra hostId if not yet initialized
> 
>
> Key: CASSANDRA-14582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config
>Reporter: vincent royer
>Assignee: Stefan Miklosovic
>Priority: Low
>  Labels: lhf
> Fix For: 4.1
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Add a system property *cassandra.host_id* to set the cassandra hostId if not 
> yet initialized.
> This allow to push the cassandra host ID when provisioning new cassandra 
> nodes rather than to retreive it after the first start.



--
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-14582) Add a system property to set the cassandra hostId if not yet initialized

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529001#comment-17529001
 ] 

Stefan Miklosovic commented on CASSANDRA-14582:
---

Based on the discussion on mailing list, we agreed on reverting this commit as 
it renders to be not robust enough and it may bring potentially more harm than 
good.

https://lists.apache.org/thread/osv4xvypfz9cy7g3zylv075kgxbzphj5

> Add a system property to set the cassandra hostId if not yet initialized
> 
>
> Key: CASSANDRA-14582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config
>Reporter: vincent royer
>Assignee: Stefan Miklosovic
>Priority: Low
>  Labels: lhf
> Fix For: 4.1
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Add a system property *cassandra.host_id* to set the cassandra hostId if not 
> yet initialized.
> This allow to push the cassandra host ID when provisioning new cassandra 
> nodes rather than to retreive it after the first start.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Commented] (CASSANDRA-17563) Fix CircleCI Midres config

[Josh McKenzie (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529005#comment-17529005
 ] 

Josh McKenzie commented on CASSANDRA-17563:
---

bq. Only change from that patch should be adding the new in-jvm job
There's quite a bit more going on in [this 
PR|https://github.com/apache/cassandra/pull/1579] than a simple revert of 
resource allocation in midres. What am I reviewing here? :)

> 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-14582) Add a system property to set the cassandra hostId if not yet initialized

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-14582:
--
Status: Patch Available  (was: Open)

> Add a system property to set the cassandra hostId if not yet initialized
> 
>
> Key: CASSANDRA-14582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config
>Reporter: vincent royer
>Assignee: Stefan Miklosovic
>Priority: Low
>  Labels: lhf
> Fix For: 4.1
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Add a system property *cassandra.host_id* to set the cassandra hostId if not 
> yet initialized.
> This allow to push the cassandra host ID when provisioning new cassandra 
> nodes rather than to retreive it after the first start.



--
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-14582) Add a system property to set the cassandra hostId if not yet initialized

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529007#comment-17529007
 ] 

Stefan Miklosovic commented on CASSANDRA-14582:
---

PR: [https://github.com/apache/cassandra/pull/1592]
dtest: [https://github.com/apache/cassandra-dtest/pull/190]
build: 
[https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1639/]

> Add a system property to set the cassandra hostId if not yet initialized
> 
>
> Key: CASSANDRA-14582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config
>Reporter: vincent royer
>Assignee: Stefan Miklosovic
>Priority: Low
>  Labels: lhf
> Fix For: 4.1
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Add a system property *cassandra.host_id* to set the cassandra hostId if not 
> yet initialized.
> This allow to push the cassandra host ID when provisioning new cassandra 
> nodes rather than to retreive it after the first start.



--
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-14582) Add a system property to set the cassandra hostId if not yet initialized

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-14582:
--
Reviewers: Paulo Motta  (was: Paulo Motta, Stefan Miklosovic)

> Add a system property to set the cassandra hostId if not yet initialized
> 
>
> Key: CASSANDRA-14582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config
>Reporter: vincent royer
>Assignee: Stefan Miklosovic
>Priority: Low
>  Labels: lhf
> Fix For: 4.1
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Add a system property *cassandra.host_id* to set the cassandra hostId if not 
> yet initialized.
> This allow to push the cassandra host ID when provisioning new cassandra 
> nodes rather than to retreive it after the first start.



--
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-14582) Add a system property to set the cassandra hostId if not yet initialized

[Paulo Motta (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paulo Motta updated CASSANDRA-14582:

Reviewers: beobal  (was: Paulo Motta)

> Add a system property to set the cassandra hostId if not yet initialized
> 
>
> Key: CASSANDRA-14582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config
>Reporter: vincent royer
>Assignee: Stefan Miklosovic
>Priority: Low
>  Labels: lhf
> Fix For: 4.1
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Add a system property *cassandra.host_id* to set the cassandra hostId if not 
> yet initialized.
> This allow to push the cassandra host ID when provisioning new cassandra 
> nodes rather than to retreive it after the first start.



--
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-14582) Add a system property to set the cassandra hostId if not yet initialized

[Paulo Motta (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529012#comment-17529012
 ] 

Paulo Motta commented on CASSANDRA-14582:
-

I think you could have kept this ticket closed and created a new one for the 
revert, to keep the original history. 

I will not have time to review this revert soon so I'll assign to [~beobal].

> Add a system property to set the cassandra hostId if not yet initialized
> 
>
> Key: CASSANDRA-14582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config
>Reporter: vincent royer
>Assignee: Stefan Miklosovic
>Priority: Low
>  Labels: lhf
> Fix For: 4.1
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Add a system property *cassandra.host_id* to set the cassandra hostId if not 
> yet initialized.
> This allow to push the cassandra host ID when provisioning new cassandra 
> nodes rather than to retreive it after the first start.



--
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-14582) Add a system property to set the cassandra hostId if not yet initialized

[Brandon Williams (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529016#comment-17529016
 ] 

Brandon Williams commented on CASSANDRA-14582:
--

Revert lgtm, +1 if CI is happy enough.

> Add a system property to set the cassandra hostId if not yet initialized
> 
>
> Key: CASSANDRA-14582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config
>Reporter: vincent royer
>Assignee: Stefan Miklosovic
>Priority: Low
>  Labels: lhf
> Fix For: 4.1
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Add a system property *cassandra.host_id* to set the cassandra hostId if not 
> yet initialized.
> This allow to push the cassandra host ID when provisioning new cassandra 
> nodes rather than to retreive it after the first start.



--
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-14582) Add a system property to set the cassandra hostId if not yet initialized

[Paulo Motta (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paulo Motta updated CASSANDRA-14582:

Reviewers: Brandon Williams  (was: beobal)

> Add a system property to set the cassandra hostId if not yet initialized
> 
>
> Key: CASSANDRA-14582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14582
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Config
>Reporter: vincent royer
>Assignee: Stefan Miklosovic
>Priority: Low
>  Labels: lhf
> Fix For: 4.1
>
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> Add a system property *cassandra.host_id* to set the cassandra hostId if not 
> yet initialized.
> This allow to push the cassandra host ID when provisioning new cassandra 
> nodes rather than to retreive it after the first start.



--
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-17180) Implement startup check to prevent Cassandra start to spread zombie data

[Stefan Miklosovic (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Miklosovic updated CASSANDRA-17180:
--
Status: Patch Available  (was: Open)

PR is here, I think I am done with it as it is. 
https://github.com/apache/cassandra/pull/1351

I am not sure what your comment means [~jmckenzie], so are we going to do this 
or not? I have mixed signals here.

> Implement startup check to prevent Cassandra start to spread zombie data
> 
>
> Key: CASSANDRA-17180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17180
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Legacy/Observability
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1
>
>  Time Spent: 11h 20m
>  Remaining Estimate: 0h
>
> As already discussed on ML, it would be nice to have a service which would 
> periodically write timestamp to a file signalling it is up / running.
> Then, on the startup, we would read this file and we would determine if there 
> is some table which gc grace is behind this time and we would fail the start 
> so we would prevent zombie data to be likely spread around a cluster.
> https://lists.apache.org/thread/w4w5t2hlcrvqhgdwww61hgg58qz13glw



--
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 (03e74866 -> a641c227)

[git-site-role]

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 03e74866 generate docs for 8fd077a6
 new a641c227 generate docs for 8fd077a6

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   (03e74866)
\
 N -- N -- N   refs/heads/asf-staging (a641c227)

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:
 .../cassandra/configuration/cass_yaml_file.html|  12 
 .../cassandra/configuration/cass_yaml_file.html|  12 
 .../cassandra/configuration/cass_yaml_file.html|  12 
 content/search-index.js|   2 +-
 site-ui/build/ui-bundle.zip| Bin 4740078 -> 4740078 
bytes
 5 files changed, 37 insertions(+), 1 deletion(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Comment Edited] (CASSANDRA-17180) Implement startup check to prevent Cassandra start to spread zombie data

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529022#comment-17529022
 ] 

Stefan Miklosovic edited comment on CASSANDRA-17180 at 4/27/22 8:01 PM:


PR is here, I think I am done with it as it is. 
https://github.com/apache/cassandra/pull/1351

I am not sure what your comment means [~jmckenzie], so are we going to do this 
or not? I have mixed signals here.

I would go with this solution for time-being. If it is optional / not enabled 
by default it does not hurt to be there. We do not know what the other solution 
looks like yet and if we even deliver it in 4.2 etc ... I do not think this is 
"half-baked". It fixes the problem just fine. Our operators would definitely 
appreciate it without having to wait for _the solution_. It brings the value 
already and it is very easy to get rid of if we decide so.


was (Author: smiklosovic):
PR is here, I think I am done with it as it is. 
https://github.com/apache/cassandra/pull/1351

I am not sure what your comment means [~jmckenzie], so are we going to do this 
or not? I have mixed signals here.

> Implement startup check to prevent Cassandra start to spread zombie data
> 
>
> Key: CASSANDRA-17180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17180
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Legacy/Observability
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1
>
>  Time Spent: 11h 20m
>  Remaining Estimate: 0h
>
> As already discussed on ML, it would be nice to have a service which would 
> periodically write timestamp to a file signalling it is up / running.
> Then, on the startup, we would read this file and we would determine if there 
> is some table which gc grace is behind this time and we would fail the start 
> so we would prevent zombie data to be likely spread around a cluster.
> https://lists.apache.org/thread/w4w5t2hlcrvqhgdwww61hgg58qz13glw



--
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-16843) List snapshots of dropped tables

[Stefan Miklosovic (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529036#comment-17529036
 ] 

Stefan Miklosovic commented on CASSANDRA-16843:
---

Is this ready to be reviewed? I am not sure if this is still indeed in "in 
progress".

> List snapshots of dropped tables
> 
>
> Key: CASSANDRA-16843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16843
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/Snapshots
>Reporter: James Brown
>Assignee: Paulo Motta
>Priority: Normal
> Fix For: 4.1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Auto snapshots from dropped tables don't seem to show up in {{nodetool 
> listsnapshots}} (even though they do get cleared by {{nodetool 
> clearsnapshot}}). This makes them kind of annoying to clean up, since you 
> need to muck about in the data directory to find them.
> Erick on the mailing list said that this seems to be an oversight and that 
> clearsnapshot was fixed by 
> [CASSANDRA-6418|https://issues.apache.org/jira/browse/CASSANDRA-6418].
> I reproduced this both on 3.11.11 and 4.0.0.



--
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-16843) List snapshots of dropped tables

[Paulo Motta (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-16843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529043#comment-17529043
 ] 

Paulo Motta commented on CASSANDRA-16843:
-

It's in progress, not ready for review yet.

> List snapshots of dropped tables
> 
>
> Key: CASSANDRA-16843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16843
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local/Snapshots
>Reporter: James Brown
>Assignee: Paulo Motta
>Priority: Normal
> Fix For: 4.1
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Auto snapshots from dropped tables don't seem to show up in {{nodetool 
> listsnapshots}} (even though they do get cleared by {{nodetool 
> clearsnapshot}}). This makes them kind of annoying to clean up, since you 
> need to muck about in the data directory to find them.
> Erick on the mailing list said that this seems to be an oversight and that 
> clearsnapshot was fixed by 
> [CASSANDRA-6418|https://issues.apache.org/jira/browse/CASSANDRA-6418].
> I reproduced this both on 3.11.11 and 4.0.0.



--
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 (a641c227 -> 59e47749)

[git-site-role]

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 a641c227 generate docs for 8fd077a6
 new 59e47749 generate docs for 8fd077a6

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   (a641c227)
\
 N -- N -- N   refs/heads/asf-staging (59e47749)

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-17180) Implement startup check to prevent Cassandra start to spread zombie data

[Josh McKenzie (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529121#comment-17529121
 ] 

Josh McKenzie commented on CASSANDRA-17180:
---

No criticism of this work, just asking that we leave it disabled by default.

> Implement startup check to prevent Cassandra start to spread zombie data
> 
>
> Key: CASSANDRA-17180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17180
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Legacy/Observability
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 4.1
>
>  Time Spent: 11h 20m
>  Remaining Estimate: 0h
>
> As already discussed on ML, it would be nice to have a service which would 
> periodically write timestamp to a file signalling it is up / running.
> Then, on the startup, we would read this file and we would determine if there 
> is some table which gc grace is behind this time and we would fail the start 
> so we would prevent zombie data to be likely spread around a cluster.
> https://lists.apache.org/thread/w4w5t2hlcrvqhgdwww61hgg58qz13glw



--
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-17564) Add synchronization to wait for outstanding tasks in the compaction executor and nonPeriodicTasks during CassandraDaemon setup

[Haoze Wu (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529141#comment-17529141
 ] 

Haoze Wu commented on CASSANDRA-17564:
--

[~smiklosovic] 

Thanks for the fix you proposed. I appreciate that. I'm still investigating 
whether your fix works in all scenarios.

My observation is that some tidier tasks can bring up more tidier tasks. And 
they can't be aborted by simply disabling compaction. A possible scenario I can 
currently imagine is that some tidier tasks are created relatively late (after 
the setupCompleted flag is set) and then suddenly got some exception when 
deleting file. With your fix, event the global ref is released, the system is 
not aware of this status and keeps running. On the other hand, before setting 
the setupCompleted flag, the system should crash in this scenario.

> Add synchronization to wait for outstanding tasks in the compaction executor 
> and nonPeriodicTasks during CassandraDaemon setup
> --
>
> Key: CASSANDRA-17564
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17564
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Local/Compaction
>Reporter: Haoze Wu
>Priority: Normal
> Fix For: 3.11.x, 4.0.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We have been testing Cassandra 3.11.10 for a while. During a node start, we 
> found that a synchronization guarantee implied by the code comments is not 
> enforced. Specifically, in the `invalidate` method called in this call stack 
> (in version 3.11.10):
> {code:java}
> org.apache.cassandra.service.CassandraDaemon#main:786
> org.apache.cassandra.service.CassandraDaemon#activate:633
> org.apache.cassandra.service.CassandraDaemon#setup:261
> org.apache.cassandra.schema.LegacySchemaMigrator#migrate:83
> org.apache.cassandra.schema.LegacySchemaMigrator#unloadLegacySchemaTables:137
> java.lang.Iterable#forEach:75
> org.apache.cassandra.schema.LegacySchemaMigrator#lambda$unloadLegacySchemaTables$1:137
> org.apache.cassandra.db.ColumnFamilyStore#invalidate:542 {code}
> In line 564~570 within `public void invalidate(boolean expectMBean)`:
> {code:java}
>         latencyCalculator.cancel(false);
>         compactionStrategyManager.shutdown();
>         SystemKeyspace.removeTruncationRecord(metadata.cfId);  // line 566
>         data.dropSSTables();                                   // line 568
>         LifecycleTransaction.waitForDeletions();               // line 569
>         indexManager.invalidateAllIndexesBlocking();
> {code}
> According to the code and the comments, we suppose `data.dropSSTables()` in 
> line 568 will submit some tidier tasks to the `nonPeriodicTasks` thread pool. 
> Call stack in version 3.11.10:
> {code:java}
> org.apache.cassandra.db.lifecycle.Tracker#dropSSTables:233
> org.apache.cassandra.db.lifecycle.Tracker#dropSSTables:238
> org.apache.cassandra.db.lifecycle.Tracker#dropSSTables:267
> org.apache.cassandra.utils.concurrent.Refs#release:241
> org.apache.cassandra.utils.concurrent.Ref#release:119
> org.apache.cassandra.utils.concurrent.Ref#release:225
> org.apache.cassandra.utils.concurrent.Ref#release:326
> org.apache.cassandra.io.sstable.format.SSTableReader$InstanceTidier#tidy:2205 
> {code}
> Then, `LifecycleTransaction.waitForDeletions()` in line 569 is
> {code:java}
>     /**
>      * Deletions run on the nonPeriodicTasks executor, (both failedDeletions 
> or global tidiers in SSTableReader)
>      * so by scheduling a new empty task and waiting for it we ensure any 
> prior deletion has completed.
>      */
>     public static void waitForDeletions()
>     {
>         LogTransaction.waitForDeletions();
>     }
> {code}
> And then call `waitForDeletions` in `LogTransaction`:
> {code:java}
>     static void waitForDeletions()
>     {
>         
> FBUtilities.waitOnFuture(ScheduledExecutors.nonPeriodicTasks.schedule(Runnables.doNothing(),
>  0, TimeUnit.MILLISECONDS));
>     }
> {code}
> From the comments, we think it ensures that all existing tasks in 
> `nonPeriodicTasks` are drained. However, we found some tidier tasks are still 
> running in `nonPeriodicTasks` thread pool.
> We suspect that those tidier tasks should be guaranteed to finish during 
> server setup, because of its exception handling. In version 3.11.10, these 
> tidier tasks are submitted to `nonPeriodicTasks` in 
> `SSTableReader$InstanceTidier#tidy:2205`, and have the exception handling 
> `FileUtils.handleFSErrorAndPropagate(new FSWriteError(e, file))` (within the 
> call stack `SSTableReader$InstanceTidier$1#run:2223` => 
> `LogTransaction$SSTableTidier#run:386` => `LogTransaction#delete:261`).
> The `FileUtils.handleFSErrorAndPropagate` handles this `FSWri

[cassandra-website] branch asf-staging updated (59e47749 -> 134aac8e)

[git-site-role]

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 59e47749 generate docs for 8fd077a6
 new 134aac8e generate docs for 8fd077a6

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   (59e47749)
\
 N -- N -- N   refs/heads/asf-staging (134aac8e)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 content/search-index.js |   2 +-
 site-ui/build/ui-bundle.zip | Bin 4740078 -> 4740078 bytes
 2 files changed, 1 insertion(+), 1 deletion(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[cassandra-website] branch asf-staging updated (134aac8e -> 77e03dab)

[git-site-role]

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 134aac8e generate docs for 8fd077a6
 new 77e03dab generate docs for 8fd077a6

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   (134aac8e)
\
 N -- N -- N   refs/heads/asf-staging (77e03dab)

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-17221) Add Math functions

[Simon Chess (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529171#comment-17529171
 ] 

Simon Chess commented on CASSANDRA-17221:
-

Hi [~e.dimitrova], I have added documentation for the functions, please let me 
know if there is anything I should change concerning syntax or something else.

> Add Math functions 
> ---
>
> Key: CASSANDRA-17221
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17221
> Project: Cassandra
>  Issue Type: Improvement
>  Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Simon Chess
>Priority: Normal
>  Labels: AdventCalendar2021, lhf
> Fix For: 4.x
>
>
> We should add native Maths functions for the most common operations:
> * {{abs\(x)}} returns the absolute value of the x
> * {{exp\(x)}} returns the value of e (the base of natural logarithms) raised 
> to the power of x
> * {{log\(x)}} returns the natural logarithm (base e) of x
> * {{log10\(x)}} returns the base-10 logarithm of x
> * {{round\(x)}} returns the closest integer to x
> +Additional information for newcomers:+
> The new functions should be put in a new class {{MathFcts}} similar to 
> {{TimeFcts}}.
> The {{MathsFcts.all()}} method should be called in 
> {{SystemKeyspace.functions}}
> The unit tests for the functions should be put in a {{MathFctsTest}} similar 
> to {{TimeFctsTest}} 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

[jira] [Created] (CASSANDRA-17585) Save sstable id as string in activity table

[Jacek Lewandowski (Jira)]

Jacek Lewandowski created CASSANDRA-17585:
-

 Summary: Save sstable id as string in activity table
 Key: CASSANDRA-17585
 URL: https://issues.apache.org/jira/browse/CASSANDRA-17585
 Project: Cassandra
  Issue Type: Task
Reporter: Jacek Lewandowski
Assignee: Jacek Lewandowski






--
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-17585) Save sstable id as string in activity table

[Jacek Lewandowski (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacek Lewandowski updated CASSANDRA-17585:
--
Change Category: Semantic
 Complexity: Low Hanging Fruit
Component/s: Local/SSTable
 Status: Open  (was: Triage Needed)

> Save sstable id as string in activity table
> ---
>
> Key: CASSANDRA-17585
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17585
> Project: Cassandra
>  Issue Type: Task
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
>




--
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-17585) Save sstable id as string in activity table

[Jacek Lewandowski (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacek Lewandowski updated CASSANDRA-17585:
--
Fix Version/s: (was: 4.1)

> Save sstable id as string in activity table
> ---
>
> Key: CASSANDRA-17585
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17585
> Project: Cassandra
>  Issue Type: Task
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
>




--
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-17585) Save sstable id as string in activity table

[Jacek Lewandowski (Jira)]

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-17585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacek Lewandowski updated CASSANDRA-17585:
--
Fix Version/s: 4.1

> Save sstable id as string in activity table
> ---
>
> Key: CASSANDRA-17585
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17585
> Project: Cassandra
>  Issue Type: Task
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 4.1
>
>




--
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-17585) Save sstable id as string in activity table

[Jacek Lewandowski (Jira)]

[ 
https://issues.apache.org/jira/browse/CASSANDRA-17585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529184#comment-17529184
 ] 

Jacek Lewandowski edited comment on CASSANDRA-17585 at 4/28/22 4:29 AM:


https://github.com/apache/cassandra/pull/1593

https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/218/workflows/7b0121f2-0220-4fca-8b3e-ac07ea7821e3


was (Author: jlewandowski):
https://github.com/apache/cassandra/pull/1593


> Save sstable id as string in activity table
> ---
>
> Key: CASSANDRA-17585
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17585
> Project: Cassandra
>  Issue Type: Task
>  Components: Local/SSTable
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
>




--
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