[jira] [Updated] (CASSANDRA-15421) CVE-2017-5929 in 3.11.x (QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components.)
[ https://issues.apache.org/jira/browse/CASSANDRA-15421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivo Dujmovic updated CASSANDRA-15421: - Fix Version/s: 3.11.x > CVE-2017-5929 in 3.11.x (QOS.ch Logback before 1.2.0 has a serialization > vulnerability affecting the SocketServer and ServerSocketReceiver components.) > --- > > Key: CASSANDRA-15421 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15421 > Project: Cassandra > Issue Type: Bug >Reporter: Abhishek Singh >Priority: Urgent > Fix For: 3.11.x > > > *Description :**Description :* *Severity :* CVE CVSS 2.0: 7.5Sonatype CVSS 3: > 9.8 > > *Weakness :* CVE CWE: 502 > > *Source :* National Vulnerability Database > > *Categories :* Data > *Description from CVE :* QOS.ch Logback before 1.2.0 has a serialization > vulnerability affecting the SocketServer and ServerSocketReceiver components. > > *Explanation :* The RemoteStreamAppenderClient class in logback-classic and > the SocketNode classes in logback-classic and logback-access allow data to be > deserialized over a Java Socket, via an ObjectInputStream, without validating > the data beforehand.When data is received from the Socket, to be logged, it > is deserialized into Java objects.An attacker can exploit this vulnerability > by sending malicious, serialized Java objects over the connection to the > Socket, which may result in execution of arbitrary code when those objects > are deserialized.Note that although logback-core is implicated by the Logback > project here, the Sonatype Security Research team discovered that the > vulnerability is actually present in the logback-classic and logback-access > components. versions prior to 1.2.0, as stated in the advisory. > *Detection :* The application is vulnerable by using this component. > *Recommendation :* We recommend upgrading to a version of this component > that is not vulnerable to this specific issue. > *Root Cause :* > apache-cassandra-3.11.4-bin.tar.gzch/qos/logback/classic/net/SocketNode.class > : [1.0.12,1.2.0] > > *Advisories :* Project: https://logback.qos.ch/news.html > > *CVSS Details :* CVE CVSS 2.0: 7.5CVSS Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P > *Occurences (Paths) :* ["apache-cassandra.zip" ; "apache-cassandra.zip"] > *CVE :* CVE-2017-5929 > *URL :* http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929 > *Remediation :* This component does not have any non-vulnerable Version. > Please contact the vendor to get this vulnerability fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15421) CVE-2017-5929 in 3.11.x (QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components.)
[ https://issues.apache.org/jira/browse/CASSANDRA-15421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivo Dujmovic updated CASSANDRA-15421: - Bug Category: Parent values: Security(12985)Level 1 values: Remote Code Execution(13002) Impacts: Security (was: None) Severity: Critical > CVE-2017-5929 in 3.11.x (QOS.ch Logback before 1.2.0 has a serialization > vulnerability affecting the SocketServer and ServerSocketReceiver components.) > --- > > Key: CASSANDRA-15421 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15421 > Project: Cassandra > Issue Type: Bug >Reporter: Abhishek Singh >Priority: Urgent > > *Description :**Description :* *Severity :* CVE CVSS 2.0: 7.5Sonatype CVSS 3: > 9.8 > > *Weakness :* CVE CWE: 502 > > *Source :* National Vulnerability Database > > *Categories :* Data > *Description from CVE :* QOS.ch Logback before 1.2.0 has a serialization > vulnerability affecting the SocketServer and ServerSocketReceiver components. > > *Explanation :* The RemoteStreamAppenderClient class in logback-classic and > the SocketNode classes in logback-classic and logback-access allow data to be > deserialized over a Java Socket, via an ObjectInputStream, without validating > the data beforehand.When data is received from the Socket, to be logged, it > is deserialized into Java objects.An attacker can exploit this vulnerability > by sending malicious, serialized Java objects over the connection to the > Socket, which may result in execution of arbitrary code when those objects > are deserialized.Note that although logback-core is implicated by the Logback > project here, the Sonatype Security Research team discovered that the > vulnerability is actually present in the logback-classic and logback-access > components. versions prior to 1.2.0, as stated in the advisory. > *Detection :* The application is vulnerable by using this component. > *Recommendation :* We recommend upgrading to a version of this component > that is not vulnerable to this specific issue. > *Root Cause :* > apache-cassandra-3.11.4-bin.tar.gzch/qos/logback/classic/net/SocketNode.class > : [1.0.12,1.2.0] > > *Advisories :* Project: https://logback.qos.ch/news.html > > *CVSS Details :* CVE CVSS 2.0: 7.5CVSS Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P > *Occurences (Paths) :* ["apache-cassandra.zip" ; "apache-cassandra.zip"] > *CVE :* CVE-2017-5929 > *URL :* http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929 > *Remediation :* This component does not have any non-vulnerable Version. > Please contact the vendor to get this vulnerability fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15829) Upgrade to logback 1.2.3 to address CVE-2017-5929
[ https://issues.apache.org/jira/browse/CASSANDRA-15829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261637#comment-17261637 ] Ivo Dujmovic commented on CASSANDRA-15829: -- I found the right tickets to link it to, and updated above. Also bumped up the the priority since the NVD score for this one is CRITICAL. > Upgrade to logback 1.2.3 to address CVE-2017-5929 > - > > Key: CASSANDRA-15829 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15829 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Assignee: Mark Denihan >Priority: High > > Recent scan results identified the following CVE that requires this upgrade > to address > [https://nvd.nist.gov/vuln/detail/CVE-2017-5929] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15829) Upgrade to logback 1.2.3 to address CVE-2017-5929
[ https://issues.apache.org/jira/browse/CASSANDRA-15829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivo Dujmovic updated CASSANDRA-15829: - Priority: High (was: Normal) > Upgrade to logback 1.2.3 to address CVE-2017-5929 > - > > Key: CASSANDRA-15829 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15829 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Assignee: Mark Denihan >Priority: High > > Recent scan results identified the following CVE that requires this upgrade > to address > [https://nvd.nist.gov/vuln/detail/CVE-2017-5929] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15829) Upgrade to logback 1.2.3 to address CVE-2017-5929
[ https://issues.apache.org/jira/browse/CASSANDRA-15829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivo Dujmovic updated CASSANDRA-15829: - Summary: Upgrade to logback 1.2.3 to address CVE-2017-5929 (was: Upgrade to logback 1.2.3 to address CVE) > Upgrade to logback 1.2.3 to address CVE-2017-5929 > - > > Key: CASSANDRA-15829 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15829 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Assignee: Mark Denihan >Priority: Normal > > Recent scan results identified the following CVE that requires this upgrade > to address > [https://nvd.nist.gov/vuln/detail/CVE-2017-5929] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15421) CVE-2017-5929 in 3.11.x (QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components.)
[ https://issues.apache.org/jira/browse/CASSANDRA-15421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivo Dujmovic updated CASSANDRA-15421: - Summary: CVE-2017-5929 in 3.11.x (QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components.) (was: CVE-2017-5929(QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components.)) > CVE-2017-5929 in 3.11.x (QOS.ch Logback before 1.2.0 has a serialization > vulnerability affecting the SocketServer and ServerSocketReceiver components.) > --- > > Key: CASSANDRA-15421 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15421 > Project: Cassandra > Issue Type: Bug >Reporter: Abhishek Singh >Priority: Normal > > *Description :**Description :* *Severity :* CVE CVSS 2.0: 7.5Sonatype CVSS 3: > 9.8 > > *Weakness :* CVE CWE: 502 > > *Source :* National Vulnerability Database > > *Categories :* Data > *Description from CVE :* QOS.ch Logback before 1.2.0 has a serialization > vulnerability affecting the SocketServer and ServerSocketReceiver components. > > *Explanation :* The RemoteStreamAppenderClient class in logback-classic and > the SocketNode classes in logback-classic and logback-access allow data to be > deserialized over a Java Socket, via an ObjectInputStream, without validating > the data beforehand.When data is received from the Socket, to be logged, it > is deserialized into Java objects.An attacker can exploit this vulnerability > by sending malicious, serialized Java objects over the connection to the > Socket, which may result in execution of arbitrary code when those objects > are deserialized.Note that although logback-core is implicated by the Logback > project here, the Sonatype Security Research team discovered that the > vulnerability is actually present in the logback-classic and logback-access > components. versions prior to 1.2.0, as stated in the advisory. > *Detection :* The application is vulnerable by using this component. > *Recommendation :* We recommend upgrading to a version of this component > that is not vulnerable to this specific issue. > *Root Cause :* > apache-cassandra-3.11.4-bin.tar.gzch/qos/logback/classic/net/SocketNode.class > : [1.0.12,1.2.0] > > *Advisories :* Project: https://logback.qos.ch/news.html > > *CVSS Details :* CVE CVSS 2.0: 7.5CVSS Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P > *Occurences (Paths) :* ["apache-cassandra.zip" ; "apache-cassandra.zip"] > *CVE :* CVE-2017-5929 > *URL :* http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5929 > *Remediation :* This component does not have any non-vulnerable Version. > Please contact the vendor to get this vulnerability fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16279) Incorrect check for -Xlog in cassandra-env.sh
[
https://issues.apache.org/jira/browse/CASSANDRA-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16279:
---
Fix Version/s: (was: 4.0-beta)
4.0
4.0-beta5
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/023eecb03acbc3d8ad751853f7ef067220eba1e9
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed as
[023eecb03acbc3d8ad751853f7ef067220eba1e9|https://github.com/apache/cassandra/commit/023eecb03acbc3d8ad751853f7ef067220eba1e9]
> Incorrect check for -Xlog in cassandra-env.sh
> --
>
> Key: CASSANDRA-16279
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16279
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
>Reporter: Yakir Gibraltar
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta5, 4.0
>
>
> Possible small bug in {{cassandra-env.sh}} of Cassandra 4:
> [https://github.com/apache/cassandra/blob/trunk/conf/cassandra-env.sh#L98]
> The following command incorrect:
> {code}
> echo "$JVM_OPTS" | grep -q "^-[X]log:gc"
> {code}
> Should be:
> {code}
> echo "$JVM_OPTS" | grep -qe "-[X]log:gc"
> {code}
> The variable {{$JVM_OPTS}} not starting with {{-Xlog..}} , and always
> return 1, remove {{^}} and add {{-qe}} will solve the problem.
> It's causing that {{cassandra-env.sh}} ignoring variable of {{-Xlog}} in
> {{jvm11-server.options}} and {{jvm8-server.options}}
>
> Right now, jvm11-server.options with:
> {code:java}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M{code}
> Will generate process of:
> {code:java}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M
>
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=10485760
> {code}
> With fix it will generate correct gc option of :
> {code}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: Fix check for -Xlog in cassandra-env.sh
This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new 023eecb Fix check for -Xlog in cassandra-env.sh
023eecb is described below
commit 023eecb03acbc3d8ad751853f7ef067220eba1e9
Author: Adam Holmberg
AuthorDate: Mon Dec 21 11:26:49 2020 -0600
Fix check for -Xlog in cassandra-env.sh
patch by Yakir Gibraltar; reviewed by Adam Holmberg, Mick Semb Wever for
CASSANDRA-16279
---
CHANGES.txt | 1 +
conf/cassandra-env.sh | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 46c1d13..7fef5a3 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
4.0-beta5
+ * Fix check for -Xlog in cassandra-env.sh (CASSANDRA-16279)
* SSLFactory should initialize SSLContext before setting protocols
(CASSANDRA-16362)
* Restore sasi dependencies jflex, snowball-stemmer, and concurrent-trees, in
the cassandra-all pom (CASSANDRA-16303)
* Fix DecimalDeserializer#toString OOM (CASSANDRA-14925)
diff --git a/conf/cassandra-env.sh b/conf/cassandra-env.sh
index a3e51e6..dd088df 100644
--- a/conf/cassandra-env.sh
+++ b/conf/cassandra-env.sh
@@ -95,7 +95,7 @@ fi
if [ $JAVA_VERSION -ge 11 ] ; then
# See description of https://bugs.openjdk.java.net/browse/JDK-8046148 for
details about the syntax
# The following is the equivalent to -XX:+PrintGCDetails
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=10M
-echo "$JVM_OPTS" | grep -q "^-[X]log:gc"
+echo "$JVM_OPTS" | grep -qe "-[X]log:gc"
if [ "$?" = "1" ] ; then # [X] to prevent ccm from replacing this line
# only add -Xlog:gc if it's not mentioned in jvm-server.options file
mkdir -p ${CASSANDRA_LOG_DIR}
@@ -103,7 +103,7 @@ if [ $JAVA_VERSION -ge 11 ] ; then
fi
else
# Java 8
-echo "$JVM_OPTS" | grep -q "^-[X]loggc"
+echo "$JVM_OPTS" | grep -qe "-[X]loggc"
if [ "$?" = "1" ] ; then # [X] to prevent ccm from replacing this line
# only add -Xlog:gc if it's not mentioned in jvm-server.options file
mkdir -p ${CASSANDRA_LOG_DIR}
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16279) Incorrect check for -Xlog in cassandra-env.sh
[
https://issues.apache.org/jira/browse/CASSANDRA-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16279:
---
Status: Ready to Commit (was: Review In Progress)
> Incorrect check for -Xlog in cassandra-env.sh
> --
>
> Key: CASSANDRA-16279
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16279
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
>Reporter: Yakir Gibraltar
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> Possible small bug in {{cassandra-env.sh}} of Cassandra 4:
> [https://github.com/apache/cassandra/blob/trunk/conf/cassandra-env.sh#L98]
> The following command incorrect:
> {code}
> echo "$JVM_OPTS" | grep -q "^-[X]log:gc"
> {code}
> Should be:
> {code}
> echo "$JVM_OPTS" | grep -qe "-[X]log:gc"
> {code}
> The variable {{$JVM_OPTS}} not starting with {{-Xlog..}} , and always
> return 1, remove {{^}} and add {{-qe}} will solve the problem.
> It's causing that {{cassandra-env.sh}} ignoring variable of {{-Xlog}} in
> {{jvm11-server.options}} and {{jvm8-server.options}}
>
> Right now, jvm11-server.options with:
> {code:java}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M{code}
> Will generate process of:
> {code:java}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M
>
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=10485760
> {code}
> With fix it will generate correct gc option of :
> {code}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16322) Fix failing python update dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-16322: -- Resolution: Done Status: Resolved (was: Open) https://app.circleci.com/pipelines/github/dcapwell/cassandra/858/workflows/195d9e91-c8be-4811-aa83-3cb342f0a6ea/jobs/5095 We are green again! > Fix failing python update dtests > > > Key: CASSANDRA-16322 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16322 > Project: Cassandra > Issue Type: Task > Components: CI, Test/dtest/python >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.0-beta > > > https://app.circleci.com/pipelines/github/dcapwell/cassandra/841/workflows/bcadf6e6-8d04-4010-8a47-99f7f9b5ac1d/jobs/4949/parallel-runs/23?filterBy=ALL > Over 600 upgrade tests are failing, this ticket is to root cause each failure > and fix the issues (in different tickets). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16322) Fix failing python update dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell reassigned CASSANDRA-16322: - Assignee: David Capwell (was: Adam Holmberg) > Fix failing python update dtests > > > Key: CASSANDRA-16322 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16322 > Project: Cassandra > Issue Type: Task > Components: CI, Test/dtest/python >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.0-beta > > > https://app.circleci.com/pipelines/github/dcapwell/cassandra/841/workflows/bcadf6e6-8d04-4010-8a47-99f7f9b5ac1d/jobs/4949/parallel-runs/23?filterBy=ALL > Over 600 upgrade tests are failing, this ticket is to root cause each failure > and fix the issues (in different tickets). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16322) Fix failing python update dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-16322: -- Test and Documentation Plan: CI Status: Patch Available (was: In Progress) > Fix failing python update dtests > > > Key: CASSANDRA-16322 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16322 > Project: Cassandra > Issue Type: Task > Components: CI, Test/dtest/python >Reporter: David Capwell >Assignee: Adam Holmberg >Priority: Normal > Fix For: 4.0-beta > > > https://app.circleci.com/pipelines/github/dcapwell/cassandra/841/workflows/bcadf6e6-8d04-4010-8a47-99f7f9b5ac1d/jobs/4949/parallel-runs/23?filterBy=ALL > Over 600 upgrade tests are failing, this ticket is to root cause each failure > and fix the issues (in different tickets). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16322) Fix failing python update dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-16322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-16322: -- Status: Open (was: Patch Available) > Fix failing python update dtests > > > Key: CASSANDRA-16322 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16322 > Project: Cassandra > Issue Type: Task > Components: CI, Test/dtest/python >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.0-beta > > > https://app.circleci.com/pipelines/github/dcapwell/cassandra/841/workflows/bcadf6e6-8d04-4010-8a47-99f7f9b5ac1d/jobs/4949/parallel-runs/23?filterBy=ALL > Over 600 upgrade tests are failing, this ticket is to root cause each failure > and fix the issues (in different tickets). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16330) Fix failing upgrade dtest test_basic_paging - upgrade_tests.paging_test.TestPagingDataNodes
[
https://issues.apache.org/jira/browse/CASSANDRA-16330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16330:
--
Fix Version/s: (was: 4.0-beta)
NA
Source Control Link:
https://github.com/apache/cassandra-dtest/commit/5cf417bd6cf4077e3a0fe7339d0c974d4cda4762
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Fix failing upgrade dtest test_basic_paging -
> upgrade_tests.paging_test.TestPagingDataNodes
> ---
>
> Key: CASSANDRA-16330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16330
> Project: Cassandra
> Issue Type: Improvement
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: NA
>
>
> test_basic_paging - upgrade_tests.paging_test.TestPagingDataNodes
> upgrade_tests/paging_test.py
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/843/workflows/9545f259-0a61-4ba8-8dea-485a33136032/jobs/4964
> {code}
> #4.0 doesn't support compact storage
> > if version_string == 'trunk' or version_string >= MAJOR_VERSION_4:
> upgrade_tests/paging_test.py:476:
> {code}
> {code}
> self = LooseVersion ('4.0')
> other = LooseVersion ('clone:/home/cassandra/cassandra')
> def _cmp (self, other):
> if isinstance(other, str):
> other = LooseVersion(other)
>
> if self.version == other.version:
> return 0
> > if self.version < other.version:
> E TypeError: '<' not supported between instances of 'int' and 'str'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16330) Fix failing upgrade dtest test_basic_paging - upgrade_tests.paging_test.TestPagingDataNodes
[
https://issues.apache.org/jira/browse/CASSANDRA-16330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16330:
--
Status: Ready to Commit (was: Review In Progress)
> Fix failing upgrade dtest test_basic_paging -
> upgrade_tests.paging_test.TestPagingDataNodes
> ---
>
> Key: CASSANDRA-16330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16330
> Project: Cassandra
> Issue Type: Improvement
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> test_basic_paging - upgrade_tests.paging_test.TestPagingDataNodes
> upgrade_tests/paging_test.py
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/843/workflows/9545f259-0a61-4ba8-8dea-485a33136032/jobs/4964
> {code}
> #4.0 doesn't support compact storage
> > if version_string == 'trunk' or version_string >= MAJOR_VERSION_4:
> upgrade_tests/paging_test.py:476:
> {code}
> {code}
> self = LooseVersion ('4.0')
> other = LooseVersion ('clone:/home/cassandra/cassandra')
> def _cmp (self, other):
> if isinstance(other, str):
> other = LooseVersion(other)
>
> if self.version == other.version:
> return 0
> > if self.version < other.version:
> E TypeError: '<' not supported between instances of 'int' and 'str'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-dtest] branch trunk updated: fix version checking for 4.0+ conditionals
This is an automated email from the ASF dual-hosted git repository.
dcapwell pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new 5cf417b fix version checking for 4.0+ conditionals
5cf417b is described below
commit 5cf417bd6cf4077e3a0fe7339d0c974d4cda4762
Author: Adam Holmberg
AuthorDate: Wed Dec 23 12:31:31 2020 -0600
fix version checking for 4.0+ conditionals
patch by Adam Holmberg; reviewed by Benjamin Lerer, David Capwell for
CASSANDRA-16330
---
upgrade_tests/paging_test.py | 8 ++--
upgrade_tests/thrift_upgrade_test.py | 20
upgrade_tests/upgrade_base.py| 13 +
3 files changed, 11 insertions(+), 30 deletions(-)
diff --git a/upgrade_tests/paging_test.py b/upgrade_tests/paging_test.py
index 11df0b9..06c5dfd 100644
--- a/upgrade_tests/paging_test.py
+++ b/upgrade_tests/paging_test.py
@@ -471,9 +471,7 @@ class TestPagingData(BasePagingTester, PageAssertionMixin):
) WITH COMPACT STORAGE;
""")
-version_string = self.upgrade_version_string()
-#4.0 doesn't support compact storage
-if version_string == 'trunk' or version_string >= MAJOR_VERSION_4:
+if testing_compact_storage and self.upgrade_is_version_4_or_greater():
# 4.0 doesn't support compact storage
cursor.execute("ALTER TABLE test2 DROP COMPACT STORAGE;")
for is_upgraded, cursor in self.do_upgrade(cursor):
@@ -527,9 +525,7 @@ class TestPagingData(BasePagingTester, PageAssertionMixin):
) WITH COMPACT STORAGE;
""")
-version_string = self.upgrade_version_string()
-#4.0 doesn't support compact storage
-if version_string == 'trunk' or version_string >= MAJOR_VERSION_4:
+if testing_compact_storage and self.upgrade_is_version_4_or_greater():
# 4.0 doesn't support compact storage
cursor.execute("ALTER TABLE test2 DROP COMPACT STORAGE;")
for is_upgraded, cursor in self.do_upgrade(cursor):
diff --git a/upgrade_tests/thrift_upgrade_test.py
b/upgrade_tests/thrift_upgrade_test.py
index cad1d7e..491786e 100644
--- a/upgrade_tests/thrift_upgrade_test.py
+++ b/upgrade_tests/thrift_upgrade_test.py
@@ -588,10 +588,7 @@ class TestThrift(UpgradeTester):
_validate_dense_cql(cursor)
_validate_dense_thrift(client)
-version_string = self.upgrade_version_string()
-is_version_4_or_greater = version_string == 'trunk' or version_string
>= '4.0'
-#4.0 doesn't support compact storage
-if is_version_4_or_greater:
+if self.upgrade_is_version_4_or_greater(): # 4.0 doesn't support
compact storage
cursor.execute("ALTER TABLE ks.dense_super_1 DROP COMPACT
STORAGE;")
for is_upgraded, cursor in self.do_upgrade(cursor,
row_factory=dict_factory, use_thrift=True):
@@ -628,10 +625,7 @@ class TestThrift(UpgradeTester):
_validate_dense_cql(cursor, cf='dense_super_2', key='renamed_key',
column1='renamed_column1', column2='renamed_column2', value='renamed_value')
_validate_dense_thrift(client, cf='dense_super_2')
-version_string = self.upgrade_version_string()
-is_version_4_or_greater = version_string == 'trunk' or version_string
>= '4.0'
-#4.0 doesn't support compact storage
-if is_version_4_or_greater:
+if self.upgrade_is_version_4_or_greater(): # 4.0 doesn't support
compact storage
cursor.execute("ALTER TABLE ks.dense_super_2 DROP COMPACT
STORAGE;")
for is_upgraded, cursor in self.do_upgrade(cursor,
row_factory=dict_factory, use_thrift=True):
@@ -671,10 +665,7 @@ class TestThrift(UpgradeTester):
_validate_sparse_thrift(client)
_validate_sparse_cql(cursor, column1='renamed_column1',
key='renamed_key')
-version_string = self.upgrade_version_string()
-is_version_4_or_greater = version_string == 'trunk' or version_string
>= '4.0'
-#4.0 doesn't support compact storage
-if is_version_4_or_greater:
+if self.upgrade_is_version_4_or_greater(): # 4.0 doesn't support
compact storage
cursor.execute("ALTER TABLE ks.sparse_super_1 DROP COMPACT
STORAGE;")
for is_upgraded, cursor in self.do_upgrade(cursor,
row_factory=dict_factory, use_thrift=True):
@@ -711,10 +702,7 @@ class TestThrift(UpgradeTester):
_validate_sparse_thrift(client, cf='sparse_super_2')
_validate_sparse_cql(cursor, cf='sparse_super_2')
-version_string = self.upgrade_version_string()
-is_version_4_or_greater = version_string == 'trunk' or version_string
>= '4.0'
-#4.0 doesn't support compact storage
-if is_version_4_or_greater:
+if self.upgrade_is_version_4_or_greater(): # 4.0 doesn't support
compact storage
[jira] [Commented] (CASSANDRA-16330) Fix failing upgrade dtest test_basic_paging - upgrade_tests.paging_test.TestPagingDataNodes
[
https://issues.apache.org/jira/browse/CASSANDRA-16330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261503#comment-17261503
]
David Capwell commented on CASSANDRA-16330:
---
+1 from me.
> Fix failing upgrade dtest test_basic_paging -
> upgrade_tests.paging_test.TestPagingDataNodes
> ---
>
> Key: CASSANDRA-16330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16330
> Project: Cassandra
> Issue Type: Improvement
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> test_basic_paging - upgrade_tests.paging_test.TestPagingDataNodes
> upgrade_tests/paging_test.py
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/843/workflows/9545f259-0a61-4ba8-8dea-485a33136032/jobs/4964
> {code}
> #4.0 doesn't support compact storage
> > if version_string == 'trunk' or version_string >= MAJOR_VERSION_4:
> upgrade_tests/paging_test.py:476:
> {code}
> {code}
> self = LooseVersion ('4.0')
> other = LooseVersion ('clone:/home/cassandra/cassandra')
> def _cmp (self, other):
> if isinstance(other, str):
> other = LooseVersion(other)
>
> if self.version == other.version:
> return 0
> > if self.version < other.version:
> E TypeError: '<' not supported between instances of 'int' and 'str'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16330) Fix failing upgrade dtest test_basic_paging - upgrade_tests.paging_test.TestPagingDataNodes
[
https://issues.apache.org/jira/browse/CASSANDRA-16330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16330:
--
Reviewers: Benjamin Lerer, David Capwell (was: Benjamin Lerer)
> Fix failing upgrade dtest test_basic_paging -
> upgrade_tests.paging_test.TestPagingDataNodes
> ---
>
> Key: CASSANDRA-16330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16330
> Project: Cassandra
> Issue Type: Improvement
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> test_basic_paging - upgrade_tests.paging_test.TestPagingDataNodes
> upgrade_tests/paging_test.py
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/843/workflows/9545f259-0a61-4ba8-8dea-485a33136032/jobs/4964
> {code}
> #4.0 doesn't support compact storage
> > if version_string == 'trunk' or version_string >= MAJOR_VERSION_4:
> upgrade_tests/paging_test.py:476:
> {code}
> {code}
> self = LooseVersion ('4.0')
> other = LooseVersion ('clone:/home/cassandra/cassandra')
> def _cmp (self, other):
> if isinstance(other, str):
> other = LooseVersion(other)
>
> if self.version == other.version:
> return 0
> > if self.version < other.version:
> E TypeError: '<' not supported between instances of 'int' and 'str'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16330) Fix failing upgrade dtest test_basic_paging - upgrade_tests.paging_test.TestPagingDataNodes
[
https://issues.apache.org/jira/browse/CASSANDRA-16330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261487#comment-17261487
]
David Capwell commented on CASSANDRA-16330:
---
yep, starting now
> Fix failing upgrade dtest test_basic_paging -
> upgrade_tests.paging_test.TestPagingDataNodes
> ---
>
> Key: CASSANDRA-16330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16330
> Project: Cassandra
> Issue Type: Improvement
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> test_basic_paging - upgrade_tests.paging_test.TestPagingDataNodes
> upgrade_tests/paging_test.py
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/843/workflows/9545f259-0a61-4ba8-8dea-485a33136032/jobs/4964
> {code}
> #4.0 doesn't support compact storage
> > if version_string == 'trunk' or version_string >= MAJOR_VERSION_4:
> upgrade_tests/paging_test.py:476:
> {code}
> {code}
> self = LooseVersion ('4.0')
> other = LooseVersion ('clone:/home/cassandra/cassandra')
> def _cmp (self, other):
> if isinstance(other, str):
> other = LooseVersion(other)
>
> if self.version == other.version:
> return 0
> > if self.version < other.version:
> E TypeError: '<' not supported between instances of 'int' and 'str'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16347) Fix upgrade python dtest upgrade_tests/upgrade_through_versions_test.py
[
https://issues.apache.org/jira/browse/CASSANDRA-16347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16347:
--
Fix Version/s: (was: 4.0-beta)
NA
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra-dtest/commit/d75f7e9ad25ab147113a107d0373af1cfa9a4e81
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
+1
> Fix upgrade python dtest upgrade_tests/upgrade_through_versions_test.py
> ---
>
> Key: CASSANDRA-16347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16347
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: NA
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/846/workflows/bee81d86-f720-4fc2-b3e7-7ed19ec3c9f0/jobs/4988/tests
> upgrade_tests/upgrade_through_versions_test.py seems to have a set of tests
> which fail with the following
> {code}
> > raise RuntimeError(message)
> E RuntimeError: A subprocess has terminated early. Subprocess
> statuses: Process-1 (is_alive: True), Process-2 (is_alive: False), attempting
> to terminate remaining subprocesses now.
> upgrade_tests/upgrade_through_versions_test.py:418: RuntimeError
> {code}
> The tests found to be failing were:
> test_rolling_upgrade_with_internode_ssl
> test_rolling_upgrade
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16347) Fix upgrade python dtest upgrade_tests/upgrade_through_versions_test.py
[
https://issues.apache.org/jira/browse/CASSANDRA-16347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16347:
--
Status: Ready to Commit (was: Review In Progress)
> Fix upgrade python dtest upgrade_tests/upgrade_through_versions_test.py
> ---
>
> Key: CASSANDRA-16347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16347
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/846/workflows/bee81d86-f720-4fc2-b3e7-7ed19ec3c9f0/jobs/4988/tests
> upgrade_tests/upgrade_through_versions_test.py seems to have a set of tests
> which fail with the following
> {code}
> > raise RuntimeError(message)
> E RuntimeError: A subprocess has terminated early. Subprocess
> statuses: Process-1 (is_alive: True), Process-2 (is_alive: False), attempting
> to terminate remaining subprocesses now.
> upgrade_tests/upgrade_through_versions_test.py:418: RuntimeError
> {code}
> The tests found to be failing were:
> test_rolling_upgrade_with_internode_ssl
> test_rolling_upgrade
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16347) Fix upgrade python dtest upgrade_tests/upgrade_through_versions_test.py
[
https://issues.apache.org/jira/browse/CASSANDRA-16347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16347:
--
Reviewers: David Capwell, David Capwell (was: David Capwell)
David Capwell, David Capwell
Status: Review In Progress (was: Patch Available)
> Fix upgrade python dtest upgrade_tests/upgrade_through_versions_test.py
> ---
>
> Key: CASSANDRA-16347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16347
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/846/workflows/bee81d86-f720-4fc2-b3e7-7ed19ec3c9f0/jobs/4988/tests
> upgrade_tests/upgrade_through_versions_test.py seems to have a set of tests
> which fail with the following
> {code}
> > raise RuntimeError(message)
> E RuntimeError: A subprocess has terminated early. Subprocess
> statuses: Process-1 (is_alive: True), Process-2 (is_alive: False), attempting
> to terminate remaining subprocesses now.
> upgrade_tests/upgrade_through_versions_test.py:418: RuntimeError
> {code}
> The tests found to be failing were:
> test_rolling_upgrade_with_internode_ssl
> test_rolling_upgrade
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-dtest] branch trunk updated: start rolling clusters with protocol capping overridden
This is an automated email from the ASF dual-hosted git repository.
dcapwell pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new d75f7e9 start rolling clusters with protocol capping overridden
d75f7e9 is described below
commit d75f7e9ad25ab147113a107d0373af1cfa9a4e81
Author: Adam Holmberg
AuthorDate: Tue Jan 5 14:31:07 2021 -0600
start rolling clusters with protocol capping overridden
patch by Adam Holmberg; reviewed by David Capwell for CASSANDRA-16347
---
upgrade_tests/upgrade_through_versions_test.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/upgrade_tests/upgrade_through_versions_test.py
b/upgrade_tests/upgrade_through_versions_test.py
index ec84bec..d2ae933 100644
--- a/upgrade_tests/upgrade_through_versions_test.py
+++ b/upgrade_tests/upgrade_through_versions_test.py
@@ -460,7 +460,8 @@ class TestUpgrade(Tester):
logger.debug('Starting %s on new version (%s)' % (node.name,
version_meta.version))
# Setup log4j / logback again (necessary moving from 2.0 -> 2.1):
node.set_log_level("INFO")
-node.start(wait_other_notice=400, wait_for_binary_proto=True)
+node.start(wait_other_notice=400, wait_for_binary_proto=True,
+
jvm_args=['-Dcassandra.disable_max_protocol_auto_override=true']) # prevent
protocol capping in mixed version clusters
node.nodetool('upgradesstables -a')
def _log_current_ver(self, current_version_meta):
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16352) Fix upgrade python dtest test_crc_check_chance_upgrade - upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-16352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16352:
--
Resolution: Duplicate
Status: Resolved (was: Open)
> Fix upgrade python dtest test_crc_check_chance_upgrade -
> upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade
>
>
> Key: CASSANDRA-16352
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16352
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/850/workflows/79486fdd-06d0-4d04-aa32-0fa648182356/jobs/5019/tests
> test_crc_check_chance_upgrade -
> upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade
> upgrade_crc_check_chance_test.py
> {code}
> > self.verify_new_crc_check_chance(node1)
> upgrade_crc_check_chance_test.py:66:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> upgrade_crc_check_chance_test.py:115: in verify_new_crc_check_chance
> session = self.patient_exclusive_cql_connection(node)
> dtest_setup.py:278: in patient_exclusive_cql_connection
> **kwargs
> dtest_setup.py:39: in retry_till_success
> return fun(*args, **kwargs)
> dtest_setup.py:188: in exclusive_cql_connection
> **kwargs)
> dtest_setup.py:216: in _create_session
> session = cluster.connect(wait_for_all_pools=True)
> cassandra/cluster.py:1667: in cassandra.cluster.Cluster.connect
> ???
> cassandra/cluster.py:1703: in cassandra.cluster.Cluster.connect
> ???
> cassandra/cluster.py:1690: in cassandra.cluster.Cluster.connect
> ???
> cassandra/cluster.py:3488: in cassandra.cluster.ControlConnection.connect
> ???
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> > ???
> E cassandra.cluster.NoHostAvailable: ('Unable to connect to any servers',
> {'127.0.0.1:9042': DriverException('ProtocolError returned from server while
> using explicitly set client protocol_version 4',)})
> cassandra/cluster.py:3533: NoHostAvailable
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16352) Fix upgrade python dtest test_crc_check_chance_upgrade - upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-16352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell reassigned CASSANDRA-16352:
-
Assignee: David Capwell (was: Adam Holmberg)
> Fix upgrade python dtest test_crc_check_chance_upgrade -
> upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade
>
>
> Key: CASSANDRA-16352
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16352
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/850/workflows/79486fdd-06d0-4d04-aa32-0fa648182356/jobs/5019/tests
> test_crc_check_chance_upgrade -
> upgrade_crc_check_chance_test.TestCrcCheckChanceUpgrade
> upgrade_crc_check_chance_test.py
> {code}
> > self.verify_new_crc_check_chance(node1)
> upgrade_crc_check_chance_test.py:66:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> upgrade_crc_check_chance_test.py:115: in verify_new_crc_check_chance
> session = self.patient_exclusive_cql_connection(node)
> dtest_setup.py:278: in patient_exclusive_cql_connection
> **kwargs
> dtest_setup.py:39: in retry_till_success
> return fun(*args, **kwargs)
> dtest_setup.py:188: in exclusive_cql_connection
> **kwargs)
> dtest_setup.py:216: in _create_session
> session = cluster.connect(wait_for_all_pools=True)
> cassandra/cluster.py:1667: in cassandra.cluster.Cluster.connect
> ???
> cassandra/cluster.py:1703: in cassandra.cluster.Cluster.connect
> ???
> cassandra/cluster.py:1690: in cassandra.cluster.Cluster.connect
> ???
> cassandra/cluster.py:3488: in cassandra.cluster.ControlConnection.connect
> ???
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> > ???
> E cassandra.cluster.NoHostAvailable: ('Unable to connect to any servers',
> {'127.0.0.1:9042': DriverException('ProtocolError returned from server while
> using explicitly set client protocol_version 4',)})
> cassandra/cluster.py:3533: NoHostAvailable
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16354) python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
[
https://issues.apache.org/jira/browse/CASSANDRA-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261480#comment-17261480
]
David Capwell commented on CASSANDRA-16354:
---
merged, thanks!
> python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
> -
>
> Key: CASSANDRA-16354
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16354
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: NA
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/850/workflows/79486fdd-06d0-4d04-aa32-0fa648182356/jobs/5019/artifacts
> We see that upgrade tests which talk to 2.2 clusters fail with the following
> error
> {code}
> > ???
> E cassandra.cluster.NoHostAvailable: ('Unable to connect to any servers',
> {'127.0.0.1:9042': DriverException('ProtocolError returned from server while
> using explicitly set client protocol_version 4',)})
> {code}
> For some reason, setting protocol version 4 causes 2.2 to fail, but this does
> not happen when using cqlsh (from trunk)
> {code}
> ./bin/cqlsh --protocol-version=4
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.2.20-SNAPSHOT | CQL spec 3.3.1 | Native protocol
> v4]
> Use HELP for help.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16354) python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
[
https://issues.apache.org/jira/browse/CASSANDRA-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16354:
--
Fix Version/s: (was: 4.0-beta)
NA
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra-dtest/commit/f235b00d07671dab745f2b82c7191db92fe365ae
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
> -
>
> Key: CASSANDRA-16354
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16354
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: NA
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/850/workflows/79486fdd-06d0-4d04-aa32-0fa648182356/jobs/5019/artifacts
> We see that upgrade tests which talk to 2.2 clusters fail with the following
> error
> {code}
> > ???
> E cassandra.cluster.NoHostAvailable: ('Unable to connect to any servers',
> {'127.0.0.1:9042': DriverException('ProtocolError returned from server while
> using explicitly set client protocol_version 4',)})
> {code}
> For some reason, setting protocol version 4 causes 2.2 to fail, but this does
> not happen when using cqlsh (from trunk)
> {code}
> ./bin/cqlsh --protocol-version=4
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.2.20-SNAPSHOT | CQL spec 3.3.1 | Native protocol
> v4]
> Use HELP for help.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16354) python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
[
https://issues.apache.org/jira/browse/CASSANDRA-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16354:
--
Reviewers: David Capwell, Sam Tunnicliffe (was: David Capwell)
> python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
> -
>
> Key: CASSANDRA-16354
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16354
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/850/workflows/79486fdd-06d0-4d04-aa32-0fa648182356/jobs/5019/artifacts
> We see that upgrade tests which talk to 2.2 clusters fail with the following
> error
> {code}
> > ???
> E cassandra.cluster.NoHostAvailable: ('Unable to connect to any servers',
> {'127.0.0.1:9042': DriverException('ProtocolError returned from server while
> using explicitly set client protocol_version 4',)})
> {code}
> For some reason, setting protocol version 4 causes 2.2 to fail, but this does
> not happen when using cqlsh (from trunk)
> {code}
> ./bin/cqlsh --protocol-version=4
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.2.20-SNAPSHOT | CQL spec 3.3.1 | Native protocol
> v4]
> Use HELP for help.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-dtest] branch trunk updated: override overly strict max protocol in 3.0 upgrade test
This is an automated email from the ASF dual-hosted git repository.
dcapwell pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new f235b00 override overly strict max protocol in 3.0 upgrade test
f235b00 is described below
commit f235b00d07671dab745f2b82c7191db92fe365ae
Author: Adam Holmberg
AuthorDate: Tue Dec 22 10:07:17 2020 -0600
override overly strict max protocol in 3.0 upgrade test
patch by Adam Holmberg; reviewed by David Capwell, Sam Tunnicliffe for
CASSANDRA-16354
---
upgrade_crc_check_chance_test.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/upgrade_crc_check_chance_test.py b/upgrade_crc_check_chance_test.py
index 46c0fdf..74b7584 100644
--- a/upgrade_crc_check_chance_test.py
+++ b/upgrade_crc_check_chance_test.py
@@ -137,7 +137,7 @@ class TestCrcCheckChanceUpgrade(Tester):
logger.debug('Starting {node} on new version
({tag})'.format(**format_args))
# Setup log4j / logback again (necessary moving from 2.0 -> 2.1):
node.set_log_level("INFO")
-node.start(wait_for_binary_proto=True)
+node.start(wait_for_binary_proto=True,
jvm_args=['-Dcassandra.disable_max_protocol_auto_override=true'])
logger.debug('Running upgradesstables')
node.nodetool('upgradesstables -a')
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16362) SSLFactory should initialize SSLContext before setting protocols
[
https://issues.apache.org/jira/browse/CASSANDRA-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261431#comment-17261431
]
Alexander Dejanovski commented on CASSANDRA-16362:
--
Sure thing, I'll run a test ASAP.
> SSLFactory should initialize SSLContext before setting protocols
>
>
> Key: CASSANDRA-16362
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16362
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Erik Merkle
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.0-beta5
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Trying to use sstableloader from the latest trunk produced the following
> Exception:
> {quote}
> Exception in thread "main" java.lang.RuntimeException: Could not create SSL
> Context.
> at
> org.apache.cassandra.tools.BulkLoader.buildSSLOptions(BulkLoader.java:261)
> at org.apache.cassandra.tools.BulkLoader.load(BulkLoader.java:64)
> at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:49)
> Caused by: java.io.IOException: Error creating/initializing the SSL Context
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:184)
> at
> org.apache.cassandra.tools.BulkLoader.buildSSLOptions(BulkLoader.java:257)
> ... 2 more
> Caused by: java.lang.IllegalStateException: SSLContext is not initialized
> at
> sun.security.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:208)
> at javax.net.ssl.SSLContextSpi.getDefaultSocket(SSLContextSpi.java:158)
> at
> javax.net.ssl.SSLContextSpi.engineGetDefaultSSLParameters(SSLContextSpi.java:184)
> at javax.net.ssl.SSLContext.getDefaultSSLParameters(SSLContext.java:435)
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:178)
> ... 3 more
> {quote}
> I believe this is because of a change to SSLFactory for CASSANDRA-13325 here:
> [https://github.com/apache/cassandra/commit/919a8964a83511d96766c3e53ba603e77bca626c#diff-0d569398cfd58566fc56bfb80c971a72afe3f392addc2df731a0b44baf29019eR177-R178]
>
> I think the solution is to call {{ctx.init()}} before trying to call
> {{ctx.getDefaultSSLParameters()}}, essentialy swapping the two lines in the
> link above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16362) SSLFactory should initialize SSLContext before setting protocols
[
https://issues.apache.org/jira/browse/CASSANDRA-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261430#comment-17261430
]
Jon Meredith edited comment on CASSANDRA-16362 at 1/8/21, 4:46 PM:
---
[~adejanovski] would you be able to rerun the Medusa integration test to verify
we've resolved the problem?
was (Author: jmeredithco):
[~adejanovski] would you be able to rerun the Medusa integration test to verify
we've resolve the problem?
> SSLFactory should initialize SSLContext before setting protocols
>
>
> Key: CASSANDRA-16362
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16362
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Erik Merkle
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.0-beta5
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Trying to use sstableloader from the latest trunk produced the following
> Exception:
> {quote}
> Exception in thread "main" java.lang.RuntimeException: Could not create SSL
> Context.
> at
> org.apache.cassandra.tools.BulkLoader.buildSSLOptions(BulkLoader.java:261)
> at org.apache.cassandra.tools.BulkLoader.load(BulkLoader.java:64)
> at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:49)
> Caused by: java.io.IOException: Error creating/initializing the SSL Context
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:184)
> at
> org.apache.cassandra.tools.BulkLoader.buildSSLOptions(BulkLoader.java:257)
> ... 2 more
> Caused by: java.lang.IllegalStateException: SSLContext is not initialized
> at
> sun.security.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:208)
> at javax.net.ssl.SSLContextSpi.getDefaultSocket(SSLContextSpi.java:158)
> at
> javax.net.ssl.SSLContextSpi.engineGetDefaultSSLParameters(SSLContextSpi.java:184)
> at javax.net.ssl.SSLContext.getDefaultSSLParameters(SSLContext.java:435)
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:178)
> ... 3 more
> {quote}
> I believe this is because of a change to SSLFactory for CASSANDRA-13325 here:
> [https://github.com/apache/cassandra/commit/919a8964a83511d96766c3e53ba603e77bca626c#diff-0d569398cfd58566fc56bfb80c971a72afe3f392addc2df731a0b44baf29019eR177-R178]
>
> I think the solution is to call {{ctx.init()}} before trying to call
> {{ctx.getDefaultSSLParameters()}}, essentialy swapping the two lines in the
> link above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16362) SSLFactory should initialize SSLContext before setting protocols
[
https://issues.apache.org/jira/browse/CASSANDRA-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261430#comment-17261430
]
Jon Meredith commented on CASSANDRA-16362:
--
[~adejanovski] would you be able to rerun the Medusa integration test to verify
we've resolve the problem?
> SSLFactory should initialize SSLContext before setting protocols
>
>
> Key: CASSANDRA-16362
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16362
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
>Reporter: Erik Merkle
>Assignee: Jon Meredith
>Priority: Normal
> Fix For: 4.0-beta5
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Trying to use sstableloader from the latest trunk produced the following
> Exception:
> {quote}
> Exception in thread "main" java.lang.RuntimeException: Could not create SSL
> Context.
> at
> org.apache.cassandra.tools.BulkLoader.buildSSLOptions(BulkLoader.java:261)
> at org.apache.cassandra.tools.BulkLoader.load(BulkLoader.java:64)
> at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:49)
> Caused by: java.io.IOException: Error creating/initializing the SSL Context
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:184)
> at
> org.apache.cassandra.tools.BulkLoader.buildSSLOptions(BulkLoader.java:257)
> ... 2 more
> Caused by: java.lang.IllegalStateException: SSLContext is not initialized
> at
> sun.security.ssl.SSLContextImpl.engineGetSocketFactory(SSLContextImpl.java:208)
> at javax.net.ssl.SSLContextSpi.getDefaultSocket(SSLContextSpi.java:158)
> at
> javax.net.ssl.SSLContextSpi.engineGetDefaultSSLParameters(SSLContextSpi.java:184)
> at javax.net.ssl.SSLContext.getDefaultSSLParameters(SSLContext.java:435)
> at
> org.apache.cassandra.security.SSLFactory.createSSLContext(SSLFactory.java:178)
> ... 3 more
> {quote}
> I believe this is because of a change to SSLFactory for CASSANDRA-13325 here:
> [https://github.com/apache/cassandra/commit/919a8964a83511d96766c3e53ba603e77bca626c#diff-0d569398cfd58566fc56bfb80c971a72afe3f392addc2df731a0b44baf29019eR177-R178]
>
> I think the solution is to call {{ctx.init()}} before trying to call
> {{ctx.getDefaultSSLParameters()}}, essentialy swapping the two lines in the
> link above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15962) Digest for some queries is different depending whether the data are retrieved from sstable or memtable
[
https://issues.apache.org/jira/browse/CASSANDRA-15962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261401#comment-17261401
]
Kornel Pal commented on CASSANDRA-15962:
Thank you [~blerer]!
> Digest for some queries is different depending whether the data are retrieved
> from sstable or memtable
> --
>
> Key: CASSANDRA-15962
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15962
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 3.11.x, 4.0-beta
>
> Attachments: DigestTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Not sure into which category should I assign this ticket.
>
> Basically when reading using certain column filters, the digest is different
> depending whether we read from sstable and memtable. This happens on
> {{trunk}} and {{cassandra-3.11}} branches. However it works properly on
> {{cassandra-3.0}} branch.
>
> I'm attaching a simple test for trunk to demonstrate what I mean.
>
> Please verify my test and my conclusions
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14834) Avoid keeping StreamingTombstoneHistogramBuilder.Spool in memory during the whole compaction
[
https://issues.apache.org/jira/browse/CASSANDRA-14834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261379#comment-17261379
]
Michael Semb Wever commented on CASSANDRA-14834:
ci-cassandra CI –
https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/280/pipeline
> Avoid keeping StreamingTombstoneHistogramBuilder.Spool in memory during the
> whole compaction
>
>
> Key: CASSANDRA-14834
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14834
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction
>Reporter: Marcus Eriksson
>Assignee: Adam Holmberg
>Priority: Low
> Fix For: 4.0-beta
>
>
> Since CASSANDRA-13444 {{StreamingTombstoneHistogramBuilder.Spool}} is
> allocated to keep around an array with 131072 * 2 * 2 integers *per written
> sstable* during the whole compaction. With LCS at times creating 1000s of
> sstables during a compaction it kills the node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16279) Incorrect check for -Xlog in cassandra-env.sh
[
https://issues.apache.org/jira/browse/CASSANDRA-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261320#comment-17261320
]
Michael Semb Wever edited comment on CASSANDRA-16279 at 1/8/21, 2:23 PM:
-
CI runs
- circleci j8
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/9/workflows/79395309-7132-4db0-88cf-57789cf303ea
- circleci j11
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/9/workflows/a472ea28-62aa-4bf5-bb0f-ef1fd6a064b5
- ci-cassandra
https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/279/
was (Author: michaelsembwever):
CI runs
- circleci j8
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/8/workflows/4105826e-5499-487f-a90d-f8e277d57e0f
- circleci j11
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/8/workflows/255d38bc-facd-4eb7-8a81-54ccebba441e
- ci-cassandra
https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/279/
> Incorrect check for -Xlog in cassandra-env.sh
> --
>
> Key: CASSANDRA-16279
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16279
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
>Reporter: Yakir Gibraltar
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> Possible small bug in {{cassandra-env.sh}} of Cassandra 4:
> [https://github.com/apache/cassandra/blob/trunk/conf/cassandra-env.sh#L98]
> The following command incorrect:
> {code}
> echo "$JVM_OPTS" | grep -q "^-[X]log:gc"
> {code}
> Should be:
> {code}
> echo "$JVM_OPTS" | grep -qe "-[X]log:gc"
> {code}
> The variable {{$JVM_OPTS}} not starting with {{-Xlog..}} , and always
> return 1, remove {{^}} and add {{-qe}} will solve the problem.
> It's causing that {{cassandra-env.sh}} ignoring variable of {{-Xlog}} in
> {{jvm11-server.options}} and {{jvm8-server.options}}
>
> Right now, jvm11-server.options with:
> {code:java}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M{code}
> Will generate process of:
> {code:java}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M
>
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=10485760
> {code}
> With fix it will generate correct gc option of :
> {code}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15563) Backport removal of OpenJDK warning log
[ https://issues.apache.org/jira/browse/CASSANDRA-15563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer reassigned CASSANDRA-15563: -- Assignee: Benjamin Lerer > Backport removal of OpenJDK warning log > --- > > Key: CASSANDRA-15563 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15563 > Project: Cassandra > Issue Type: Task > Components: Local/Startup and Shutdown >Reporter: Thomas Steinmaurer >Assignee: Benjamin Lerer >Priority: Low > Labels: lhf > Fix For: 2.2.x, 3.0.x > > > As requested on ASF Slack, creating this ticket for a backport of > CASSANDRA-13916 for 3.0. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16279) Incorrect check for -Xlog in cassandra-env.sh
[
https://issues.apache.org/jira/browse/CASSANDRA-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16279:
---
Reviewers: Adam Holmberg, Michael Semb Wever, Michael Semb Wever (was:
Adam Holmberg, Michael Semb Wever)
Adam Holmberg, Michael Semb Wever, Michael Semb Wever (was:
Adam Holmberg)
Status: Review In Progress (was: Patch Available)
> Incorrect check for -Xlog in cassandra-env.sh
> --
>
> Key: CASSANDRA-16279
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16279
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
>Reporter: Yakir Gibraltar
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> Possible small bug in {{cassandra-env.sh}} of Cassandra 4:
> [https://github.com/apache/cassandra/blob/trunk/conf/cassandra-env.sh#L98]
> The following command incorrect:
> {code}
> echo "$JVM_OPTS" | grep -q "^-[X]log:gc"
> {code}
> Should be:
> {code}
> echo "$JVM_OPTS" | grep -qe "-[X]log:gc"
> {code}
> The variable {{$JVM_OPTS}} not starting with {{-Xlog..}} , and always
> return 1, remove {{^}} and add {{-qe}} will solve the problem.
> It's causing that {{cassandra-env.sh}} ignoring variable of {{-Xlog}} in
> {{jvm11-server.options}} and {{jvm8-server.options}}
>
> Right now, jvm11-server.options with:
> {code:java}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M{code}
> Will generate process of:
> {code:java}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M
>
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=10485760
> {code}
> With fix it will generate correct gc option of :
> {code}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16279) Incorrect check for -Xlog in cassandra-env.sh
[
https://issues.apache.org/jira/browse/CASSANDRA-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261320#comment-17261320
]
Michael Semb Wever commented on CASSANDRA-16279:
CI runs
- circleci j8
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/8/workflows/4105826e-5499-487f-a90d-f8e277d57e0f
- circleci j11
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/8/workflows/255d38bc-facd-4eb7-8a81-54ccebba441e
- ci-cassandra
https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/279/
> Incorrect check for -Xlog in cassandra-env.sh
> --
>
> Key: CASSANDRA-16279
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16279
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
>Reporter: Yakir Gibraltar
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> Possible small bug in {{cassandra-env.sh}} of Cassandra 4:
> [https://github.com/apache/cassandra/blob/trunk/conf/cassandra-env.sh#L98]
> The following command incorrect:
> {code}
> echo "$JVM_OPTS" | grep -q "^-[X]log:gc"
> {code}
> Should be:
> {code}
> echo "$JVM_OPTS" | grep -qe "-[X]log:gc"
> {code}
> The variable {{$JVM_OPTS}} not starting with {{-Xlog..}} , and always
> return 1, remove {{^}} and add {{-qe}} will solve the problem.
> It's causing that {{cassandra-env.sh}} ignoring variable of {{-Xlog}} in
> {{jvm11-server.options}} and {{jvm8-server.options}}
>
> Right now, jvm11-server.options with:
> {code:java}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M{code}
> Will generate process of:
> {code:java}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M
>
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=10485760
> {code}
> With fix it will generate correct gc option of :
> {code}
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=/var/log/cassandra/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=100M
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15829) Upgrade to logback 1.2.3 to address CVE
[ https://issues.apache.org/jira/browse/CASSANDRA-15829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261292#comment-17261292 ] Kevin Eveker commented on CASSANDRA-15829: -- [~ivodujmovic] i probably cloned the other ticket to create this one so ignore that. This one still need to be addressed. > Upgrade to logback 1.2.3 to address CVE > --- > > Key: CASSANDRA-15829 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15829 > Project: Cassandra > Issue Type: Improvement >Reporter: Kevin Eveker >Assignee: Mark Denihan >Priority: Normal > > Recent scan results identified the following CVE that requires this upgrade > to address > [https://nvd.nist.gov/vuln/detail/CVE-2017-5929] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16370) Install Cassandra on IBM Cloud
[
https://issues.apache.org/jira/browse/CASSANDRA-16370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Md. Mubassir Ahsan updated CASSANDRA-16370:
---
Description:
This documentation will describe how to Install Cassandra on [IBM
Cloud|https://cloud.ibm.com/].
*Requirements/Prerequisites:*
* IBM Cloud Pay-As-You-Go or Subscription [Account
types|https://cloud.ibm.com/docs/account?topic=account-accounts].
*Installation Steps:*
We are assuming that you have logged-in to [IBM Cloud|https://cloud.ibm.com/].
Now follow the steps below:
*Step 1: Provision a Kubernetes Cluster*
* Click on the [Catalog|https://cloud.ibm.com/catalog#services]{color:#172b4d}
{color}link on the top menu.
* Select *{color:#172b4d}Services{color}* from left navigation menu of the
[Catalog|https://cloud.ibm.com/catalog#services] page.
Now Search for Kubernetes Service and [click on
it.|https://cloud.ibm.com/kubernetes/catalog/create]!Step 1 3 - Kubernates
Services.png|width=635,height=504!
{color:#172b4d} Option 1: Create{color} free Kubernates Engine:
* Price Plan: Free
{color:#172b4d}!Step 1 4 create cluster plan only.png!{color}
* {color:#172b4d}Now click *create*{color} on the right to provision the free
kubernetes cluster.
!create cluster --.png!
* Please wait for few moments to complete the cluster creation.
Option 2: Create Standard Kubernetes Engine with following attributes:
* Price Plan: Standard
* Infrastructure: Classic
!image-2020-12-29-16-32-55-506.png!
* Availability: Single Zone
* Geography: Europe
* Worker Zone: London 02
!Step 1 6 Kubernate details.png!
* 4 VCPU
* 16 GB RAM
* Worker nodes per zone: 2
!Step 1 7 Kubernate details.png!
* Enter the cluster name of your choice.
* Now Click {color:#172b4d}*Create* {color}to provision.
!create cluster --.png!
* Please wait for few moment to provision the cluster.
*Step 2: deploy IBM Cloud Block Storage plug-in*
* Just like the step 1, click on the [Catalog|https://cloud.ibm.com/catalog]
on the top menu again.
* Search for "Storage Block" and [Click on
it.|https://cloud.ibm.com/infrastructure/block-storage]
* Click on {color:#172b4d}*Create* {color}
* Now give storage details
* N.B. Select location as the cluster location.
* Location > Europe > Single Zone > London 02
* Billing Method > 20 GB >Linux
!Step 2 1.png!
* Click on “_I have agreed to the terms and conditions listed below_”.
* Now a storage plugin will be available in the dashboard.
*Step 3: Deploy Cassandra*
* Again go to the catalog and search for “Cassandra” and [Click on
it.|https://cloud.ibm.com/catalog#software]
* Now {color:#172b4d}select {color}"Cassandra".
* In the Cassandra creation page add the details below:
** Summary
** Cassandra
** Target: IBM Kubernetes Service
** Method: Helm chart
** Kubernetes cluster: mycluster-free (eu-de)
** Target namespace: default
** Workspace: cassandra-test
** Resource group: Default
!Step 4 1 cassandra.png!
* Select your previously created cluster
* Select the default namespace
!Step 4 2 1 Select Details of cluster.png!
* Add a name to your cluster for example “cassandra-test”
!image-2020-12-29-16-55-57-447.png!
* Select *Create* and wait for some time.
*Step 4: Verify Installation*
* Go to the *Resources List* in the Left Navigation Menu:
!image-2020-12-29-16-57-24-395.png!
* Click on *Clusters* > Select your Cluster.
!resourcelist.png!
* Now you are at your clusters overview page. You will see details of your
cluster as below:
!cluster-free-details.png!
* Here click on *Actions* (in the right corner) and select *Web terminal* from
the dropdown menu.
* Click *install,* then - wait for couple of minutes to finish the process.
* After completing the installation click on *actions* > *Web terminal* again
.
!web-terminal.png!
* A terminal will open up
* Type in the terminal, please change NAMESPACE to the namespace you choose at
the deployment setup:
{code:java}
$ kubectl get ns{code}
{code:java}
$ kubectl get pod -n NAMESPACE -o wide{code}
{code:java}
$ kubectl get service -n NAMESPACE{code}
!image-2020-12-29-17-06-42-587.png!
The installation is over. Enjoy!
was:
This documentation will describe how to Install Cassandra on [IBM
Cloud|https://cloud.ibm.com/].
*Requirements/Prerequisites:*
* IBM Cloud Pay-As-You-Go or Subscription [Account
types|https://cloud.ibm.com/docs/account?topic=account-accounts].
*Installation Steps:*
We are assuming that you have logged-in to [IBM Cloud|https://cloud.ibm.com/].
Now follow the steps below:
*Step 1: Provision a Kubernetes Cluster*
* Click on the [Catalog|https://cloud.ibm.com/catalog#services]{color:#172b4d}
{color}link on the top menu.
* Select *{color:#172b4d}Services{color}* from left navigation menu of the
[Catalog|https://cloud.ibm.com/catalog#services] page.
Now Search for Kubernetes
[jira] [Updated] (CASSANDRA-16354) python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
[
https://issues.apache.org/jira/browse/CASSANDRA-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16354:
Status: Ready to Commit (was: Review In Progress)
+1 on the dtest change (which I think we'll need to duplicate for the actual
upgrade tests for CASSANDRA-16347)
> python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
> -
>
> Key: CASSANDRA-16354
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16354
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/850/workflows/79486fdd-06d0-4d04-aa32-0fa648182356/jobs/5019/artifacts
> We see that upgrade tests which talk to 2.2 clusters fail with the following
> error
> {code}
> > ???
> E cassandra.cluster.NoHostAvailable: ('Unable to connect to any servers',
> {'127.0.0.1:9042': DriverException('ProtocolError returned from server while
> using explicitly set client protocol_version 4',)})
> {code}
> For some reason, setting protocol version 4 causes 2.2 to fail, but this does
> not happen when using cqlsh (from trunk)
> {code}
> ./bin/cqlsh --protocol-version=4
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.2.20-SNAPSHOT | CQL spec 3.3.1 | Native protocol
> v4]
> Use HELP for help.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16354) python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
[
https://issues.apache.org/jira/browse/CASSANDRA-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261181#comment-17261181
]
Sam Tunnicliffe commented on CASSANDRA-16354:
-
bq. The way it's written presently, the default is to return a DynamicLimit.
When initializing a 3.0 node in a cluster with 2.2 nodes, the max version is
lowered.
oh, right yes. I was overlooking the fact that these are *upgrade* tests :P
bq. mind being a reviewer for this as you have more context?
No probs, I'll give it a look today
> python dtest fails to talk to 2.2 using protocol 4 but cqlsh has no issue
> -
>
> Key: CASSANDRA-16354
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16354
> Project: Cassandra
> Issue Type: Bug
> Components: CI, Test/dtest/python
>Reporter: David Capwell
>Assignee: Adam Holmberg
>Priority: Normal
> Fix For: 4.0-beta
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/850/workflows/79486fdd-06d0-4d04-aa32-0fa648182356/jobs/5019/artifacts
> We see that upgrade tests which talk to 2.2 clusters fail with the following
> error
> {code}
> > ???
> E cassandra.cluster.NoHostAvailable: ('Unable to connect to any servers',
> {'127.0.0.1:9042': DriverException('ProtocolError returned from server while
> using explicitly set client protocol_version 4',)})
> {code}
> For some reason, setting protocol version 4 causes 2.2 to fail, but this does
> not happen when using cqlsh (from trunk)
> {code}
> ./bin/cqlsh --protocol-version=4
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.2.20-SNAPSHOT | CQL spec 3.3.1 | Native protocol
> v4]
> Use HELP for help.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16373) Deploy testing docker images to hub.docker.com/u/apache/
[
https://issues.apache.org/jira/browse/CASSANDRA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261165#comment-17261165
]
Sam Tunnicliffe commented on CASSANDRA-16373:
-
{quote}I've stuck with the `20210105` tag (and the images that were built that
day). (Trunk patch has been corrected.)
{quote}
wfm, thanks!
> Deploy testing docker images to hub.docker.com/u/apache/
> -
>
> Key: CASSANDRA-16373
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16373
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/java, Test/dtest/python, Test/unit
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 2.2.20, 3.0.24, 3.11.10, 4.0-beta5, 4.0
>
>
> INFRA-21103 demonstrates PMC individuals can get access to the apache
> organisation on dockerhub (and the dockerhub "cassandra" team).
> We have a number of docker images (used in testing and CI) that are currently
> deployed under individual user accounts on dockerhub. These can now be
> deployed under https://hub.docker.com/u/apache
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
