[jira] [Updated] (CASSANDRA-15597) Correct Visibility and Improve Safety of Methods in LatencyMetrics
[ https://issues.apache.org/jira/browse/CASSANDRA-15597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Haddad updated CASSANDRA-15597: --- Fix Version/s: (was: 4.0) 4.0-alpha Source Control Link: https://github.com/apache/cassandra/commit/c5eb532b63e80bb976d9dfdd4aa1c76f27f726e5 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed, thanks! > Correct Visibility and Improve Safety of Methods in LatencyMetrics > -- > > Key: CASSANDRA-15597 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15597 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Metrics >Reporter: Jordan West >Assignee: Jeff >Priority: Normal > Fix For: 4.0-alpha > > > * add/removeChildren does not need to be public (and exposing addChildren is > unsafe since no lock is used). > * casting in the constructor is safer than casting each time in removeChildren -- 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-15597) Correct Visibility and Improve Safety of Methods in LatencyMetrics
[ https://issues.apache.org/jira/browse/CASSANDRA-15597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Haddad updated CASSANDRA-15597: --- Status: Ready to Commit (was: Review In Progress) > Correct Visibility and Improve Safety of Methods in LatencyMetrics > -- > > Key: CASSANDRA-15597 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15597 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Metrics >Reporter: Jordan West >Assignee: Jeff >Priority: Normal > Fix For: 4.0 > > > * add/removeChildren does not need to be public (and exposing addChildren is > unsafe since no lock is used). > * casting in the constructor is safer than casting each time in removeChildren -- 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: Correct Visibility and Improve Safety of Methods in LatencyMetrics
This is an automated email from the ASF dual-hosted git repository. rustyrazorblade 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 c5eb532 Correct Visibility and Improve Safety of Methods in LatencyMetrics c5eb532 is described below commit c5eb532b63e80bb976d9dfdd4aa1c76f27f726e5 Author: Jeff Lai AuthorDate: Sat Feb 29 10:06:11 2020 -0500 Correct Visibility and Improve Safety of Methods in LatencyMetrics patch by jefftt; reviewed by Jordan West and Jon Haddad for CASSANDRA-15597 --- CHANGES.txt | 1 + src/java/org/apache/cassandra/metrics/LatencyMetrics.java | 12 ++-- 2 files changed, 7 insertions(+), 6 deletions(-) diff --git a/CHANGES.txt b/CHANGES.txt index 5dd25e4..5a9d3e1 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 4.0-alpha4 + * Correct Visibility and Improve Safety of Methods in LatencyMetrics (CASSANDRA-15597) * Allow cqlsh to run with Python2.7/Python3.6+ (CASSANDRA-15659,CASSANDRA-15573) * Improve logging around incremental repair (CASSANDRA-15599) * Do not check cdc_raw_directory filesystem space if CDC disabled (CASSANDRA-15688) diff --git a/src/java/org/apache/cassandra/metrics/LatencyMetrics.java b/src/java/org/apache/cassandra/metrics/LatencyMetrics.java index 7d5d288..ab4c9a5 100644 --- a/src/java/org/apache/cassandra/metrics/LatencyMetrics.java +++ b/src/java/org/apache/cassandra/metrics/LatencyMetrics.java @@ -37,7 +37,7 @@ import static org.apache.cassandra.metrics.CassandraMetricsRegistry.Metrics; public class LatencyMetrics { /** Latency */ -public final Timer latency; +public final LatencyMetricsTimer latency; /** Total latency in micro sec */ public final Counter totalLatency; @@ -89,7 +89,7 @@ public class LatencyMetrics this.aliasFactory = aliasFactory; this.namePrefix = namePrefix; -Timer timer = new LatencyMetrics.LatencyMetricsTimer(new DecayingEstimatedHistogramReservoir()); +LatencyMetricsTimer timer = new LatencyMetrics.LatencyMetricsTimer(new DecayingEstimatedHistogramReservoir()); Counter counter = new LatencyMetricsCounter(); if (aliasFactory == null) @@ -122,12 +122,12 @@ public class LatencyMetrics } } -public void addChildren(LatencyMetrics latencyMetric) +private void addChildren(LatencyMetrics latencyMetric) { this.children.add(latencyMetric); } -public synchronized void removeChildren(LatencyMetrics toRelease) +private synchronized void removeChildren(LatencyMetrics toRelease) { /* Merge details of removed children metrics and add them to our local copy to prevent metrics from going @@ -135,7 +135,7 @@ public class LatencyMetrics Will not protect against simultaneous updates, but since these methods are used by linked parent instances only, they should not receive any updates. */ -((LatencyMetricsTimer) this.latency).releasedLatencyCount += toRelease.latency.getCount(); +this.latency.releasedLatencyCount += toRelease.latency.getCount(); DecayingEstimatedHistogramReservoir.EstimatedHistogramReservoirSnapshot childSnapshot = (DecayingEstimatedHistogramReservoir.EstimatedHistogramReservoirSnapshot) toRelease.latency.getSnapshot(); DecayingEstimatedHistogramReservoir.EstimatedHistogramReservoirSnapshot snapshot = (DecayingEstimatedHistogramReservoir.EstimatedHistogramReservoirSnapshot) this.latency.getSnapshot(); @@ -176,7 +176,7 @@ public class LatencyMetrics } } -class LatencyMetricsTimer extends Timer +public class LatencyMetricsTimer extends Timer { long releasedLatencyCount = 0; - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15713) InstanceClassLoader fails to load with the following previously initiated loading for a different type with name "org/w3c/dom/Document"
[ https://issues.apache.org/jira/browse/CASSANDRA-15713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084370#comment-17084370 ] David Capwell commented on CASSANDRA-15713: --- Based off [this comment|https://github.com/apache/cassandra-in-jvm-dtest-api/pull/7#issuecomment-614028723] looks like [~ifesdjeen] approved as well. > InstanceClassLoader fails to load with the following previously initiated > loading for a different type with name "org/w3c/dom/Document" > --- > > Key: CASSANDRA-15713 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15713 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > java.lang.LinkageError: loader constraint violation: loader (instance of > org/apache/cassandra/distributed/shared/InstanceClassLoader) previously > initiated loading for a different type with name "org/w3c/dom/Document” > This is caused when using dtest outside of the normal Cassandra context. > There is no API to add more exclusions so unable to work around this. -- 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-15713) InstanceClassLoader fails to load with the following previously initiated loading for a different type with name "org/w3c/dom/Document"
[ https://issues.apache.org/jira/browse/CASSANDRA-15713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15713: -- Reviewers: Alex Petrov, Jon Meredith (was: Jon Meredith) > InstanceClassLoader fails to load with the following previously initiated > loading for a different type with name "org/w3c/dom/Document" > --- > > Key: CASSANDRA-15713 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15713 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > java.lang.LinkageError: loader constraint violation: loader (instance of > org/apache/cassandra/distributed/shared/InstanceClassLoader) previously > initiated loading for a different type with name "org/w3c/dom/Document” > This is caused when using dtest outside of the normal Cassandra context. > There is no API to add more exclusions so unable to work around this. -- 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-builds] branch master updated: Update agents list and install instructions after donations from - Amazon's 15 m5.2xlarge servers - iland's 5 16core 32gb ram servers
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/cassandra-builds.git The following commit(s) were added to refs/heads/master by this push: new 98af352 Update agents list and install instructions after donations from - Amazon's 15 m5.2xlarge servers - iland's 5 16core 32gb ram servers 98af352 is described below commit 98af35261cac5829af9aea0bb37fdc04f1697c3a Author: mck AuthorDate: Sat Mar 21 08:32:23 2020 +0100 Update agents list and install instructions after donations from - Amazon's 15 m5.2xlarge servers - iland's 5 16core 32gb ram servers --- ASF-slaves.txt | 75 +- 1 file changed, 58 insertions(+), 17 deletions(-) diff --git a/ASF-slaves.txt b/ASF-slaves.txt index d9ae4cd..156234a 100644 --- a/ASF-slaves.txt +++ b/ASF-slaves.txt @@ -7,17 +7,22 @@ Additional compute resource donations for the Apache Cassandra project are appreciated. If you have questions about compute resource donations, ask on the dev mailing list . -The installed OS software is the stock online.net Ubuntu 16.04 LTS amd64 image +The installed OS software is the stock online.net Ubuntu 18.04 LTS amd64 image with only their default installation of bind9 removed: $ sudo apt-get autoremove --purge bind9 $ sudo rm -r /var/cache/bind +On AWS you are free to re-use the public AMI `ami-02cd664c0e9899a91 cassandra-jenkins-host-v3`. + Edit sudoers to allow INFRA to sudo without password, or provide them with the password. For example, set: %sudo ALL=(ALL:ALL) NOPASSWD:ALL $ sudo visudo +Ensure the additional (500GB) data volume is mounted (and added to `/etc/fstab` at `/home/jenkins` + Add jenkins user: - $ sudo useradd -m -s /bin/bash jenkins + $ sudo groupadd -g 910 jenkins + $ sudo useradd -m -u 910 -g 910 -s /bin/bash jenkins Add ssh pub key from puppet deployment repo: https://github.com/apache/infrastructure-puppet/blob/deployment/data/ubuntu/1404.yaml#L295 @@ -27,12 +32,38 @@ Add ssh pub key from puppet deployment repo: $ sudo chmod 700 /home/jenkins/.ssh $ sudo chmod 600 /home/jenkins/.ssh/authorized_keys +Install and Configure Puppet: +1. I added an 'asf999' user which has a pub key file containing keys from the Infra Team. (It has our standard uid/gid of 910) +(See also: https://github.com/apache/infrastructure-puppet/blob/deployment/data/common.yaml#L55 ) +2. The asf999 user has sudo no passwd (configured in visudo) +3. Installed Puppet 6 (Not Puppet 5 that Bionic would normally install) + and configured the puppet.conf file ready for use + 3a. wget https://apt.puppetlabs.com/puppet-release-bionic.deb + 3b. dpkg -i puppet-release-bionic.deb + 3c. apt-get update + 3d. apt-get install -y puppet-agent + 3e. cat >> /etc/puppetlabs/puppet/puppet.conf << EOF +[main] +server = pm01-lw-us.apache.org +EOF + + +Ensure `hostname` is configured to the server's public ip. + + -Slaves for build.apache.org: +Slaves for ci-cassandra.apache.org: -'cassandra' label slaves (16G RAM) +All have label 'cassandra'. Agents with 32GB+ RAM also have the label 'cassandra-large'. +cassandra1 - 163.172.73.141 - Ubuntu 18.04 LTS amd64, 32G RAM, donated by Datastax +cassandra2 - 163.172.73.156 - Ubuntu 18.04 LTS amd64, 32G RAM, donated by Datastax +cassandra3 - 163.172.4.20 - Ubuntu 18.04 LTS amd64, 32G RAM, donated by Datastax +cassandra4 - 163.172.4.140 - Ubuntu 18.04 LTS amd64, 32G RAM, donated by Datastax +cassandra5 - 163.172.4.150 - Ubuntu 18.04 LTS amd64, 32G RAM, donated by Datastax +cassandra6 - 163.172.4.175 - Ubuntu 18.04 LTS amd64, 32G RAM, donated by Datastax +cassandra7 - 163.172.4.184 - Ubuntu 18.04 LTS amd64, 32G RAM, donated by Datastax cassandra8 - 35.160.175.252 - Ubuntu 16.04 LTS amd64, 16G RAM, 4 cores, donated by instaclustr cassandra9 - 34.210.158.175 - Ubuntu 16.04 LTS amd64, 16G RAM, 4 cores, donated by instaclustr cassandra10 - 35.165.114.131 - Ubuntu 16.04 LTS amd64, 16G RAM, 4 cores, donated by instaclustr @@ -42,20 +73,27 @@ cassandra13 - 52.32.194.237 - Ubuntu 16.04 LTS amd64, 16G RAM, 4 cores, donated cassandra14 - 52.38.171.39 - Ubuntu 16.04 LTS amd64, 16G RAM, 4 cores, donated by instaclustr cassandra15 - 52.89.160.64 - Ubuntu 16.04 LTS amd64, 16G RAM, 4 cores, donated by instaclustr cassandra16 - 54.148.184.162 - Ubuntu 16.04 LTS amd64, 16G RAM, 4 cores, donated by instaclustr +cassandra17 - 44.230.121.32 - Ubuntu 18.04 LTS amd64, 32G RAM, m5.2xlarge, donated by Amazon +cassandra18 - 44.230.213.15 - Ubuntu 18.04 LTS amd64, 32G RAM, m5.2xlarge, donated by Amazon +cassandra19 - 44.231.106.18 - Ubuntu 18.04 LTS amd64, 32G RAM, m5.2xlarge, donated by Amazon +cassandra20 - 44.231.194.19 - Ubuntu 18.04 LTS amd64, 32G RAM, m5.2xlarge, donated by Amazon
[jira] [Commented] (CASSANDRA-15733) jvm dtest builder should be provided to the factory and expose state
[ https://issues.apache.org/jira/browse/CASSANDRA-15733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084368#comment-17084368 ] David Capwell commented on CASSANDRA-15733: --- patch includes dtest + trunk, once the code is approved I will write for 2.2, 3.0, and 3.11 > jvm dtest builder should be provided to the factory and expose state > > > Key: CASSANDRA-15733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15733 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Currently the builder is rather heavy and creates configs plus call the > factory with specific fields only, this isn’t that flexible and makes it > harder to have custom cluster definitions which require additional fields to > be defined. To solve this we should make the builder be sent to the factory > and expose the state so the factory can get all the fields it needs, the > factory should also be in charge of creating the configs -- 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-15733) jvm dtest builder should be provided to the factory and expose state
[ https://issues.apache.org/jira/browse/CASSANDRA-15733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15733: -- Reviewers: Alex Petrov > jvm dtest builder should be provided to the factory and expose state > > > Key: CASSANDRA-15733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15733 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Currently the builder is rather heavy and creates configs plus call the > factory with specific fields only, this isn’t that flexible and makes it > harder to have custom cluster definitions which require additional fields to > be defined. To solve this we should make the builder be sent to the factory > and expose the state so the factory can get all the fields it needs, the > factory should also be in charge of creating the configs -- 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-15733) jvm dtest builder should be provided to the factory and expose state
[ https://issues.apache.org/jira/browse/CASSANDRA-15733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15733: -- Test and Documentation Plan: manual verification Status: Patch Available (was: Open) > jvm dtest builder should be provided to the factory and expose state > > > Key: CASSANDRA-15733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15733 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Currently the builder is rather heavy and creates configs plus call the > factory with specific fields only, this isn’t that flexible and makes it > harder to have custom cluster definitions which require additional fields to > be defined. To solve this we should make the builder be sent to the factory > and expose the state so the factory can get all the fields it needs, the > factory should also be in charge of creating the configs -- 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-15733) jvm dtest builder should be provided to the factory and expose state
[ https://issues.apache.org/jira/browse/CASSANDRA-15733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-15733: --- Labels: pull-request-available (was: ) > jvm dtest builder should be provided to the factory and expose state > > > Key: CASSANDRA-15733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15733 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > > Currently the builder is rather heavy and creates configs plus call the > factory with specific fields only, this isn’t that flexible and makes it > harder to have custom cluster definitions which require additional fields to > be defined. To solve this we should make the builder be sent to the factory > and expose the state so the factory can get all the fields it needs, the > factory should also be in charge of creating the configs -- 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-15733) jvm dtest builder should be provided to the factory and expose state
[ https://issues.apache.org/jira/browse/CASSANDRA-15733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15733: -- Change Category: Quality Assurance Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > jvm dtest builder should be provided to the factory and expose state > > > Key: CASSANDRA-15733 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15733 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > > Currently the builder is rather heavy and creates configs plus call the > factory with specific fields only, this isn’t that flexible and makes it > harder to have custom cluster definitions which require additional fields to > be defined. To solve this we should make the builder be sent to the factory > and expose the state so the factory can get all the fields it needs, the > factory should also be in charge of creating the configs -- 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] [Created] (CASSANDRA-15733) jvm dtest builder should be provided to the factory and expose state
David Capwell created CASSANDRA-15733: - Summary: jvm dtest builder should be provided to the factory and expose state Key: CASSANDRA-15733 URL: https://issues.apache.org/jira/browse/CASSANDRA-15733 Project: Cassandra Issue Type: Improvement Components: Test/dtest Reporter: David Capwell Assignee: David Capwell Currently the builder is rather heavy and creates configs plus call the factory with specific fields only, this isn’t that flexible and makes it harder to have custom cluster definitions which require additional fields to be defined. To solve this we should make the builder be sent to the factory and expose the state so the factory can get all the fields it needs, the factory should also be in charge of creating the configs -- 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-15732) DOC - Update details of new book "Cassandra: The Definitive Guide"
[ https://issues.apache.org/jira/browse/CASSANDRA-15732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084309#comment-17084309 ] Erick Ramirez commented on CASSANDRA-15732: --- Got this from [~mck] -- https://github.com/apache/cassandra-website. Cheers! (y) > DOC - Update details of new book "Cassandra: The Definitive Guide" > -- > > Key: CASSANDRA-15732 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15732 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > > There is a new edition of the book "Cassandra: The Definitive Guide" by Jeff > Carpenter and Eben Hewitt. > * 3rd edition > * updated for Cassandra 4.0 > * https://www.amazon.com/gp/product/1098115163/ > Need to update the Community page. -- 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-15710) DOC - Add cqlsh Python 3 support in NEWS.txt and tools section of website
[ https://issues.apache.org/jira/browse/CASSANDRA-15710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084297#comment-17084297 ] Erick Ramirez commented on CASSANDRA-15710: --- Thanks [~dcapwell]. (y) [~ptbannister], just checking in to see if you think there is anything else to add. Cheers! > DOC - Add cqlsh Python 3 support in NEWS.txt and tools section of website > - > > Key: CASSANDRA-15710 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15710 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/NEWS.txt >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Attachments: 15710-trunk.txt > > Time Spent: 10m > Remaining Estimate: 0h > > h2. Background > I found out by accident that CASSANDRA-10190 is not documented in > {{NEWS.txt}}. > h2. Scope > * {{NEWS.txt}} - Add info on Python 3 support for cqlsh. > * Docs - include new {{--python}} option -- 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-15732) DOC - Update details of new book "Cassandra: The Definitive Guide"
[ https://issues.apache.org/jira/browse/CASSANDRA-15732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084294#comment-17084294 ] Erick Ramirez commented on CASSANDRA-15732: --- The [Community page|http://cassandra.apache.org/community/] doesn't seem to be managed in-tree. Trying to find out where it's maintained. Do you know [~rustyrazorblade]? > DOC - Update details of new book "Cassandra: The Definitive Guide" > -- > > Key: CASSANDRA-15732 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15732 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > > There is a new edition of the book "Cassandra: The Definitive Guide" by Jeff > Carpenter and Eben Hewitt. > * 3rd edition > * updated for Cassandra 4.0 > * https://www.amazon.com/gp/product/1098115163/ > Need to update the Community page. -- 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-15732) DOC - Update details of new book "Cassandra: The Definitive Guide"
[ https://issues.apache.org/jira/browse/CASSANDRA-15732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-15732: -- Reviewers: Jeffrey Carpenter, Jon Haddad (was: Jon Haddad) > DOC - Update details of new book "Cassandra: The Definitive Guide" > -- > > Key: CASSANDRA-15732 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15732 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > > There is a new edition of the book "Cassandra: The Definitive Guide" by Jeff > Carpenter and Eben Hewitt. > * 3rd edition > * updated for Cassandra 4.0 > * https://www.amazon.com/gp/product/1098115163/ > Need to update the Community page. -- 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-15732) DOC - Update details of new book "Cassandra: The Definitive Guide"
[ https://issues.apache.org/jira/browse/CASSANDRA-15732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-15732: -- Change Category: Quality Assurance Complexity: Low Hanging Fruit Reviewers: Jon Haddad Status: Open (was: Triage Needed) > DOC - Update details of new book "Cassandra: The Definitive Guide" > -- > > Key: CASSANDRA-15732 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15732 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > > There is a new edition of the book "Cassandra: The Definitive Guide" by Jeff > Carpenter and Eben Hewitt. > * 3rd edition > * updated for Cassandra 4.0 > * https://www.amazon.com/gp/product/1098115163/ > Need to update the Community page. -- 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] [Created] (CASSANDRA-15732) DOC - Update details of new book "Cassandra: The Definitive Guide"
Erick Ramirez created CASSANDRA-15732: - Summary: DOC - Update details of new book "Cassandra: The Definitive Guide" Key: CASSANDRA-15732 URL: https://issues.apache.org/jira/browse/CASSANDRA-15732 Project: Cassandra Issue Type: Improvement Components: Documentation/Website Reporter: Erick Ramirez Assignee: Erick Ramirez There is a new edition of the book "Cassandra: The Definitive Guide" by Jeff Carpenter and Eben Hewitt. * 3rd edition * updated for Cassandra 4.0 * https://www.amazon.com/gp/product/1098115163/ Need to update the Community page. -- 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-15674) liveDiskSpaceUsed and totalDiskSpaceUsed get corrupted if IndexSummaryRedistribution gets interrupted
[ https://issues.apache.org/jira/browse/CASSANDRA-15674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084281#comment-17084281 ] David Capwell commented on CASSANDRA-15674: --- [~marcuse] I moved the test to use CQLTester based off your comment: see [here|https://github.com/apache/cassandra/pull/500/commits/902354e378429292b63c7127171856312102da22] > liveDiskSpaceUsed and totalDiskSpaceUsed get corrupted if > IndexSummaryRedistribution gets interrupted > - > > Key: CASSANDRA-15674 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15674 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction, Observability/Metrics >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 4.0-alpha > > > IndexSummaryRedistribution is a compaction task and as such extends Holder > and supports cancelation by throwing a CompactionInterruptedException. The > issue is that IndexSummaryRedistribution tries to use transactions, but > mutates the sstable in-place; transaction is unable to roll back. > This would be fine (only updates summary) if it wasn’t for the fact the task > attempts to also mutate the two metrics liveDiskSpaceUsed and > totalDiskSpaceUsed, since these can’t be rolled back any cancelation could > corrupt these metrics. -- 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-15731) cassandra-stress fails when we specify a port per node
[ https://issues.apache.org/jira/browse/CASSANDRA-15731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Boudreault updated CASSANDRA-15731: Description: {code} $ ./tools/bin/cassandra-stress write n=10 -node 127.0.0.1:9046,127.0.0.1:9048 ... java.lang.RuntimeException: java.lang.IllegalArgumentException: Failed to add contact point: 127.0.0.1:9046 at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:148) at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:116) at org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:66) at org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:156) at org.apache.cassandra.stress.StressAction.run(StressAction.java:56) at org.apache.cassandra.stress.Stress.run(Stress.java:143) at org.apache.cassandra.stress.Stress.main(Stress.java:62) Caused by: java.lang.IllegalArgumentException: Failed to add contact point: 127.0.0.1:9046 at com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:922) at org.apache.cassandra.stress.util.JavaDriverClient.connect(JavaDriverClient.java:131) at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:139) ... 6 more Caused by: java.net.UnknownHostException: 127.0.0.1:9046: invalid IPv6 address at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1341) at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1298) at com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:919) ... 8 more {code} was: {code} $ ./tools/bin/cassandra-stress write n=10 -node 127.0.0.1:9046 ... java.lang.RuntimeException: java.lang.IllegalArgumentException: Failed to add contact point: 127.0.0.1:9046 at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:148) at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:116) at org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:66) at org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:156) at org.apache.cassandra.stress.StressAction.run(StressAction.java:56) at org.apache.cassandra.stress.Stress.run(Stress.java:143) at org.apache.cassandra.stress.Stress.main(Stress.java:62) Caused by: java.lang.IllegalArgumentException: Failed to add contact point: 127.0.0.1:9046 at com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:922) at org.apache.cassandra.stress.util.JavaDriverClient.connect(JavaDriverClient.java:131) at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:139) ... 6 more Caused by: java.net.UnknownHostException: 127.0.0.1:9046: invalid IPv6 address at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1341) at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1298) at com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:919) ... 8 more {code} > cassandra-stress fails when we specify a port per node > --- > > Key: CASSANDRA-15731 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15731 > Project: Cassandra > Issue Type: Bug >Reporter: Alan Boudreault >Priority: Normal > Fix For: 4.0-beta > > > {code} > $ ./tools/bin/cassandra-stress write n=10 -node 127.0.0.1:9046,127.0.0.1:9048 > ... > java.lang.RuntimeException: java.lang.IllegalArgumentException: Failed to add > contact point: 127.0.0.1:9046 > at > org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:148) > at > org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:116) > at > org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:66) > at > org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:156) > at org.apache.cassandra.stress.StressAction.run(StressAction.java:56) > at org.apache.cassandra.stress.Stress.run(Stress.java:143) > at org.apache.cassandra.stress.Stress.main(Stress.java:62) > Caused by: java.lang.IllegalArgumentException: Failed to add contact point: > 127.0.0.1:9046 > at > com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:922) > at > org.apache.cassandra.stress.util.JavaDriverClient.connect(JavaDriverClient.java:131) > at >
[jira] [Updated] (CASSANDRA-15731) cassandra-stress fails when we specify a port per node
[ https://issues.apache.org/jira/browse/CASSANDRA-15731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Boudreault updated CASSANDRA-15731: Summary: cassandra-stress fails when we specify a port per node (was: cassandra-stress fails when we specify a node port) > cassandra-stress fails when we specify a port per node > --- > > Key: CASSANDRA-15731 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15731 > Project: Cassandra > Issue Type: Bug >Reporter: Alan Boudreault >Priority: Normal > Fix For: 4.0-beta > > > {code} > $ ./tools/bin/cassandra-stress write n=10 -node 127.0.0.1:9046 > ... > java.lang.RuntimeException: java.lang.IllegalArgumentException: Failed to add > contact point: 127.0.0.1:9046 > at > org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:148) > at > org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:116) > at > org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:66) > at > org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:156) > at org.apache.cassandra.stress.StressAction.run(StressAction.java:56) > at org.apache.cassandra.stress.Stress.run(Stress.java:143) > at org.apache.cassandra.stress.Stress.main(Stress.java:62) > Caused by: java.lang.IllegalArgumentException: Failed to add contact point: > 127.0.0.1:9046 > at > com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:922) > at > org.apache.cassandra.stress.util.JavaDriverClient.connect(JavaDriverClient.java:131) > at > org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:139) > ... 6 more > Caused by: java.net.UnknownHostException: 127.0.0.1:9046: invalid IPv6 address > at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1341) > at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1298) > at > com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:919) > ... 8 more > {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-15731) cassandra-stress fails when we specify a node port
[ https://issues.apache.org/jira/browse/CASSANDRA-15731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Boudreault updated CASSANDRA-15731: Fix Version/s: 4.0-beta > cassandra-stress fails when we specify a node port > --- > > Key: CASSANDRA-15731 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15731 > Project: Cassandra > Issue Type: Bug >Reporter: Alan Boudreault >Priority: Normal > Fix For: 4.0-beta > > > {code} > $ ./tools/bin/cassandra-stress write n=10 -node 127.0.0.1:9046 > ... > java.lang.RuntimeException: java.lang.IllegalArgumentException: Failed to add > contact point: 127.0.0.1:9046 > at > org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:148) > at > org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:116) > at > org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:66) > at > org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:156) > at org.apache.cassandra.stress.StressAction.run(StressAction.java:56) > at org.apache.cassandra.stress.Stress.run(Stress.java:143) > at org.apache.cassandra.stress.Stress.main(Stress.java:62) > Caused by: java.lang.IllegalArgumentException: Failed to add contact point: > 127.0.0.1:9046 > at > com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:922) > at > org.apache.cassandra.stress.util.JavaDriverClient.connect(JavaDriverClient.java:131) > at > org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:139) > ... 6 more > Caused by: java.net.UnknownHostException: 127.0.0.1:9046: invalid IPv6 address > at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1341) > at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1298) > at > com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:919) > ... 8 more > {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] [Created] (CASSANDRA-15731) cassandra-stress fails when we specify a node port
Alan Boudreault created CASSANDRA-15731: --- Summary: cassandra-stress fails when we specify a node port Key: CASSANDRA-15731 URL: https://issues.apache.org/jira/browse/CASSANDRA-15731 Project: Cassandra Issue Type: Bug Reporter: Alan Boudreault {code} $ ./tools/bin/cassandra-stress write n=10 -node 127.0.0.1:9046 ... java.lang.RuntimeException: java.lang.IllegalArgumentException: Failed to add contact point: 127.0.0.1:9046 at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:148) at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:116) at org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:66) at org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:156) at org.apache.cassandra.stress.StressAction.run(StressAction.java:56) at org.apache.cassandra.stress.Stress.run(Stress.java:143) at org.apache.cassandra.stress.Stress.main(Stress.java:62) Caused by: java.lang.IllegalArgumentException: Failed to add contact point: 127.0.0.1:9046 at com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:922) at org.apache.cassandra.stress.util.JavaDriverClient.connect(JavaDriverClient.java:131) at org.apache.cassandra.stress.settings.StressSettings.getJavaDriverClient(StressSettings.java:139) ... 6 more Caused by: java.net.UnknownHostException: 127.0.0.1:9046: invalid IPv6 address at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1341) at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1298) at com.datastax.driver.core.Cluster$Builder.addContactPoint(Cluster.java:919) ... 8 more {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-15338) Fix flakey testMessagePurging - org.apache.cassandra.net.ConnectionTest
[ https://issues.apache.org/jira/browse/CASSANDRA-15338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084233#comment-17084233 ] Yifan Cai commented on CASSANDRA-15338: --- Thanks [~adelapena]. That will be great. Please proceed. > Fix flakey testMessagePurging - org.apache.cassandra.net.ConnectionTest > --- > > Key: CASSANDRA-15338 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15338 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: David Capwell >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Attachments: CASS-15338-Docker.zip > > Time Spent: 10m > Remaining Estimate: 0h > > Example failure: > [https://circleci.com/gh/dcapwell/cassandra/11#artifacts/containers/1] > > {code:java} > Testcase: testMessagePurging(org.apache.cassandra.net.ConnectionTest): FAILED > expected:<0> but was:<1> > junit.framework.AssertionFailedError: expected:<0> but was:<1> > at > org.apache.cassandra.net.ConnectionTest.lambda$testMessagePurging$38(ConnectionTest.java:625) > at > org.apache.cassandra.net.ConnectionTest.doTestManual(ConnectionTest.java:258) > at > org.apache.cassandra.net.ConnectionTest.testManual(ConnectionTest.java:231) > at > org.apache.cassandra.net.ConnectionTest.testMessagePurging(ConnectionTest.java:584){code} > > Looking closer at > org.apache.cassandra.net.OutboundConnection.Delivery#stopAndRun it seems that > the run method is called before > org.apache.cassandra.net.OutboundConnection.Delivery#doRun which may lead to > a test race condition where the CountDownLatch completes before executing -- 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-15338) Fix flakey testMessagePurging - org.apache.cassandra.net.ConnectionTest
[ https://issues.apache.org/jira/browse/CASSANDRA-15338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084228#comment-17084228 ] Andres de la Peña commented on CASSANDRA-15338: --- Looks good to me. [~yifanc] do you need me to commit it? > Fix flakey testMessagePurging - org.apache.cassandra.net.ConnectionTest > --- > > Key: CASSANDRA-15338 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15338 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: David Capwell >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Attachments: CASS-15338-Docker.zip > > Time Spent: 10m > Remaining Estimate: 0h > > Example failure: > [https://circleci.com/gh/dcapwell/cassandra/11#artifacts/containers/1] > > {code:java} > Testcase: testMessagePurging(org.apache.cassandra.net.ConnectionTest): FAILED > expected:<0> but was:<1> > junit.framework.AssertionFailedError: expected:<0> but was:<1> > at > org.apache.cassandra.net.ConnectionTest.lambda$testMessagePurging$38(ConnectionTest.java:625) > at > org.apache.cassandra.net.ConnectionTest.doTestManual(ConnectionTest.java:258) > at > org.apache.cassandra.net.ConnectionTest.testManual(ConnectionTest.java:231) > at > org.apache.cassandra.net.ConnectionTest.testMessagePurging(ConnectionTest.java:584){code} > > Looking closer at > org.apache.cassandra.net.OutboundConnection.Delivery#stopAndRun it seems that > the run method is called before > org.apache.cassandra.net.OutboundConnection.Delivery#doRun which may lead to > a test race condition where the CountDownLatch completes before executing -- 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-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083920#comment-17083920 ] Benjamin Lerer edited comment on CASSANDRA-15728 at 4/15/20, 4:14 PM: -- [jenkins ci-run|https://ci-cassandra.apache.org/job/Cassandra-devbranch/62/] was (Author: blerer): [jenkins ci-run|https://ci-cassandra.apache.org/job/Cassandra-devbranch/57/] > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 20m > Remaining Estimate: 0h > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) >
[jira] [Commented] (CASSANDRA-15714) Support in cassandra-in-jvm-dtest-api for replacing logback with alternate logger
[ https://issues.apache.org/jira/browse/CASSANDRA-15714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084214#comment-17084214 ] David Capwell commented on CASSANDRA-15714: --- Sorry didn't look after you fixed my feedback. +1 to the patch (assuming you remove mine from it ^_^) Adding CHANGES.txt makes sense to me > Support in cassandra-in-jvm-dtest-api for replacing logback with alternate > logger > -- > > Key: CASSANDRA-15714 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15714 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Jon Meredith >Assignee: Jon Meredith >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Not all forks use logback, and there is an (prematurely) closed ticket > indicating that it would be valuable CASSANDRA-13212. > > Add support for making the log file configuration property and log file > pathname configurable rather than hard-coding to logback. > > Also had to add 'org.w3c.dom' to the InstanceClassLoader so that log4j2 could > load its configuration, but looks like that can be handled with the changes > in CASSANDRA-15713 -- 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-15714) Support in cassandra-in-jvm-dtest-api for replacing logback with alternate logger
[ https://issues.apache.org/jira/browse/CASSANDRA-15714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084207#comment-17084207 ] Jon Meredith commented on CASSANDRA-15714: -- I think documenting evolutions of the API would be useful. > Support in cassandra-in-jvm-dtest-api for replacing logback with alternate > logger > -- > > Key: CASSANDRA-15714 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15714 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Jon Meredith >Assignee: Jon Meredith >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Not all forks use logback, and there is an (prematurely) closed ticket > indicating that it would be valuable CASSANDRA-13212. > > Add support for making the log file configuration property and log file > pathname configurable rather than hard-coding to logback. > > Also had to add 'org.w3c.dom' to the InstanceClassLoader so that log4j2 could > load its configuration, but looks like that can be handled with the changes > in CASSANDRA-15713 -- 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-15730) Logic for determining if all statements in a batch are for the same table is inverted
[ https://issues.apache.org/jira/browse/CASSANDRA-15730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryn Cooke updated CASSANDRA-15730: --- Description: Currently affectsMultipleTables is true if all statements in a batch are for the same table [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144] This later causes an assertion failure [here|https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75] was: Currently affectsMultipleTables is true if all statements in a batch are for the same table [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144] This later causes an assertion failure [here|https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75] > Logic for determining if all statements in a batch are for the same table is > inverted > - > > Key: CASSANDRA-15730 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15730 > Project: Cassandra > Issue Type: Bug >Reporter: Bryn Cooke >Priority: Normal > > Currently affectsMultipleTables is true if all statements in a batch are for > the same table > [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144] > > This later causes an assertion failure > [here|https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75] > > -- 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-15730) Logic for determining if all statements in a batch are for the same table is inverted
[ https://issues.apache.org/jira/browse/CASSANDRA-15730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryn Cooke updated CASSANDRA-15730: --- Description: Currently affectsMultipleTables is true if all statements in a batch are for the same table [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144] This later causes an assertion failure [here|https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75] was: Currently affectsMultipleTables is true if all statements in a batch are for the same table [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144] This later causes an assertion failure [here|#L75]] > Logic for determining if all statements in a batch are for the same table is > inverted > - > > Key: CASSANDRA-15730 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15730 > Project: Cassandra > Issue Type: Bug >Reporter: Bryn Cooke >Priority: Normal > > Currently affectsMultipleTables is true if all statements in a batch are for > the same table > [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144] > > This later causes an assertion failure > [here|https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75] > > -- 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-15730) Logic for determining if all statements in a batch are for the same table is inverted
[ https://issues.apache.org/jira/browse/CASSANDRA-15730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryn Cooke updated CASSANDRA-15730: --- Description: Currently affectsMultipleTables is true if all statements in a batch are for the same table [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144] This later causes an assertion failure [here|#L75]] was: Currently affectsMultipleTables is true if all statements in a batch are for the same table [here|[https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144]][ |https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144] This later causes an assertion failure [here|[https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75]] > Logic for determining if all statements in a batch are for the same table is > inverted > - > > Key: CASSANDRA-15730 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15730 > Project: Cassandra > Issue Type: Bug >Reporter: Bryn Cooke >Priority: Normal > > Currently affectsMultipleTables is true if all statements in a batch are for > the same table > [here|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144] > > This later causes an assertion failure [here|#L75]] > > -- 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] [Created] (CASSANDRA-15730) Logic for determining if all statements in a batch are for the same table is inverted
Bryn Cooke created CASSANDRA-15730: -- Summary: Logic for determining if all statements in a batch are for the same table is inverted Key: CASSANDRA-15730 URL: https://issues.apache.org/jira/browse/CASSANDRA-15730 Project: Cassandra Issue Type: Bug Reporter: Bryn Cooke Currently affectsMultipleTables is true if all statements in a batch are for the same table [here|[https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144]][ |https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L144] This later causes an assertion failure [here|[https://github.com/apache/cassandra/blob/24c8a21c1c131abd89c6b646343ff098d1b3263b/src/java/org/apache/cassandra/cql3/VariableSpecifications.java#L75]] -- 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-15724) Modify cassandra.yaml and replace the default data location, still data stored in default location
[ https://issues.apache.org/jira/browse/CASSANDRA-15724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Meredith updated CASSANDRA-15724: - Resolution: Works for Me Status: Resolved (was: Awaiting Feedback) Configuration issue. > Modify cassandra.yaml and replace the default data location, still data > stored in default location > -- > > Key: CASSANDRA-15724 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15724 > Project: Cassandra > Issue Type: Bug > Components: Local/SSTable >Reporter: Boopalan >Priority: Normal > > I have created a separated directory (/mnt/) for cassandra data, commit log, > hint and saved_cache. But data are not created on created directory, stored > in default location /var/lib/cassandra/data. > > *Configuration File:* > [root@node-master cassandra]# cat /etc/cassandra/default.conf/cassandra.yaml > | grep /mnt/ > hints_directory: */mnt/*hints > - */mnt/*data > commitlog_directory: */mnt/*commitlog > cdc_raw_directory: */mnt/*cdc_raw > saved_caches_directory: */mnt/*saved_caches > > Please help me to resolve this issue. -- 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-15724) Modify cassandra.yaml and replace the default data location, still data stored in default location
[ https://issues.apache.org/jira/browse/CASSANDRA-15724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084163#comment-17084163 ] Jon Meredith commented on CASSANDRA-15724: -- I'm going to close this issue as it's configuration related. If you read the logs you've provided, you can see there's a permission problems with accessing the path {{/mnt/data/system/local-7ad54392bcdd35a684174e047860b377/md_txn_flush_4ed121f0-7ef4-11ea-8dc8-cf6c58093313.log}} Check that the user you are running Cassandra as (probably {{cassandra}} in group {{cassandra}}) has permissions to access the directories you have configured in {{cassandra.yaml}}, something like {{sudo chown cassandra:cassandra /mnt/data}}. Good luck. This is the community resource page in case you get stuck, http://cassandra.apache.org/community/ > Modify cassandra.yaml and replace the default data location, still data > stored in default location > -- > > Key: CASSANDRA-15724 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15724 > Project: Cassandra > Issue Type: Bug > Components: Local/SSTable >Reporter: Boopalan >Priority: Normal > > I have created a separated directory (/mnt/) for cassandra data, commit log, > hint and saved_cache. But data are not created on created directory, stored > in default location /var/lib/cassandra/data. > > *Configuration File:* > [root@node-master cassandra]# cat /etc/cassandra/default.conf/cassandra.yaml > | grep /mnt/ > hints_directory: */mnt/*hints > - */mnt/*data > commitlog_directory: */mnt/*commitlog > cdc_raw_directory: */mnt/*cdc_raw > saved_caches_directory: */mnt/*saved_caches > > Please help me to resolve this issue. -- 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-13666) Secondary index query on partition key columns might not return partitions with only static data
[ https://issues.apache.org/jira/browse/CASSANDRA-13666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084153#comment-17084153 ] Berenguer Blasi commented on CASSANDRA-13666: - Tested and 2.2 is not affected. > Secondary index query on partition key columns might not return partitions > with only static data > > > Key: CASSANDRA-13666 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13666 > Project: Cassandra > Issue Type: Bug > Components: Feature/2i Index >Reporter: Benjamin Lerer >Assignee: Berenguer Blasi >Priority: Normal > > The problem can be reproduced with the following test in {{3.0}}: > {code} >@Test > public void testIndexOnPartitionKeyWithPartitionWithoutRows() throws > Throwable > { > createTable("CREATE TABLE %s (pk1 int, pk2 int, c int, s int static, > v int, PRIMARY KEY((pk1, pk2), c))"); > createIndex("CREATE INDEX ON %s (pk2)"); > execute("INSERT INTO %s (pk1, pk2, c, s, v) VALUES (?, ?, ?, ?, ?)", > 1, 1, 1, 9, 1); > execute("INSERT INTO %s (pk1, pk2, c, s, v) VALUES (?, ?, ?, ?, ?)", > 1, 1, 2, 9, 2); > execute("INSERT INTO %s (pk1, pk2, c, s, v) VALUES (?, ?, ?, ?, ?)", > 3, 1, 1, 9, 1); > execute("INSERT INTO %s (pk1, pk2, c, s, v) VALUES (?, ?, ?, ?, ?)", > 4, 1, 1, 9, 1); > flush(); > assertRows(execute("SELECT * FROM %s WHERE pk2 = ?", 1), >row(1, 1, 1, 9, 1), >row(1, 1, 2, 9, 2), >row(3, 1, 1, 9, 1), >row(4, 1, 1, 9, 1)); > execute("DELETE FROM %s WHERE pk1 = ? AND pk2 = ? AND c = ?", 3, 1, > 1); > assertRows(execute("SELECT * FROM %s WHERE pk2 = ?", 1), >row(1, 1, 1, 9, 1), >row(1, 1, 2, 9, 2), >row(3, 1, null, 9, null), // This row will not be returned >row(4, 1, 1, 9, 1)); > } > {code} > The problem seems to be that the index entries for the static data are > inserted with an empty clustering key. When the first {{SELECT}} is executed > those entries are removed by {{CompositesSearcher::filterStaleEntries}} which > consider that those entries are stales. When the second {{SELECT}} is > executed the index ignore the (3, 1) partition as there is not entry for it > anymore. -- 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-15713) InstanceClassLoader fails to load with the following previously initiated loading for a different type with name "org/w3c/dom/Document"
[ https://issues.apache.org/jira/browse/CASSANDRA-15713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-15713: Attachment: image.png > InstanceClassLoader fails to load with the following previously initiated > loading for a different type with name "org/w3c/dom/Document" > --- > > Key: CASSANDRA-15713 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15713 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > java.lang.LinkageError: loader constraint violation: loader (instance of > org/apache/cassandra/distributed/shared/InstanceClassLoader) previously > initiated loading for a different type with name "org/w3c/dom/Document” > This is caused when using dtest outside of the normal Cassandra context. > There is no API to add more exclusions so unable to work around this. -- 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-15713) InstanceClassLoader fails to load with the following previously initiated loading for a different type with name "org/w3c/dom/Document"
[ https://issues.apache.org/jira/browse/CASSANDRA-15713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-15713: Attachment: (was: image.png) > InstanceClassLoader fails to load with the following previously initiated > loading for a different type with name "org/w3c/dom/Document" > --- > > Key: CASSANDRA-15713 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15713 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > java.lang.LinkageError: loader constraint violation: loader (instance of > org/apache/cassandra/distributed/shared/InstanceClassLoader) previously > initiated loading for a different type with name "org/w3c/dom/Document” > This is caused when using dtest outside of the normal Cassandra context. > There is no API to add more exclusions so unable to work around this. -- 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-15714) Support in cassandra-in-jvm-dtest-api for replacing logback with alternate logger
[ https://issues.apache.org/jira/browse/CASSANDRA-15714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084105#comment-17084105 ] Alex Petrov commented on CASSANDRA-15714: - +1 to make this change. This is unrelated to the ticket itself: I'm starting thinking if it'd be useful to add {{CHANGES.txt}} file and keep a log of tickets that were committed to make it easier to maintain cross-version compatibility? > Support in cassandra-in-jvm-dtest-api for replacing logback with alternate > logger > -- > > Key: CASSANDRA-15714 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15714 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Jon Meredith >Assignee: Jon Meredith >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Not all forks use logback, and there is an (prematurely) closed ticket > indicating that it would be valuable CASSANDRA-13212. > > Add support for making the log file configuration property and log file > pathname configurable rather than hard-coding to logback. > > Also had to add 'org.w3c.dom' to the InstanceClassLoader so that log4j2 could > load its configuration, but looks like that can be handled with the changes > in CASSANDRA-15713 -- 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-15726) buffer pool may throw NPE with concurrent release due to in-progress tiny pool eviction
[ https://issues.apache.org/jira/browse/CASSANDRA-15726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084099#comment-17084099 ] Aleksey Yeschenko commented on CASSANDRA-15726: --- Sure, I'll take a look once I've gotten through some items in my queue. > buffer pool may throw NPE with concurrent release due to in-progress tiny > pool eviction > --- > > Key: CASSANDRA-15726 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15726 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: ZhaoYang >Assignee: ZhaoYang >Priority: Normal > Fix For: 4.0-alpha > > > This can be reproduced by running {{LongBufferPoolTest}}, 1 out 5 runs.. > {code:java} > java.lang.NullPointerException > at > org.apache.cassandra.utils.memory.BufferPool$Chunk.access$1300(BufferPool.java:836) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.lambda$remove$1(BufferPool.java:716) > at > org.apache.cassandra.utils.memory.BufferPool$MicroQueueOfChunks.removeIf(BufferPool.java:460) > at > org.apache.cassandra.utils.memory.BufferPool$MicroQueueOfChunks.access$1500(BufferPool.java:304) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.remove(BufferPool.java:716) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.put(BufferPool.java:590) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.recycle(BufferPool.java:709) > at > org.apache.cassandra.utils.memory.BufferPool$Chunk.recycle(BufferPool.java:909) > at > org.apache.cassandra.utils.memory.BufferPool$Chunk.tryRecycle(BufferPool.java:903) > at > org.apache.cassandra.utils.memory.BufferPool$Chunk.release(BufferPool.java:896) > at > org.apache.cassandra.utils.memory.BufferPool$MicroQueueOfChunks.removeIf(BufferPool.java:465) > at > org.apache.cassandra.utils.memory.BufferPool$MicroQueueOfChunks.access$1500(BufferPool.java:304) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.addChunk(BufferPool.java:736) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.addChunkFromParent(BufferPool.java:725) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.tryGetInternal(BufferPool.java:691) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.tryGet(BufferPool.java:679) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.access$000(BufferPool.java:518) > at > org.apache.cassandra.utils.memory.BufferPool.tryGet(BufferPool.java:120) > > at > org.apache.cassandra.utils.memory.LongBufferPoolTest$2.testOne(LongBufferPoolTest.java:497) > at > org.apache.cassandra.utils.memory.LongBufferPoolTest$TestUntil.call(LongBufferPoolTest.java:558) > at > org.apache.cassandra.utils.memory.LongBufferPoolTest$TestUntil.call(LongBufferPoolTest.java:538) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) > at java.lang.Thread.run(Thread.java:748) > {code} > The cause is that: > * When evicting a normal chunk from a full MicroQueueOfChunks, local pool > will try to remove corresponding tiny chunks, via > {{MicroQueueOfChunks#removeIf}}. > * If matching tiny chunk is found, tiny {{chunk.release()}} is called > immediately before moving null chunk to the back of the queue. > * Due to concurrent release from different threads, tiny {{chunk.release()}} > may cause its parent normal chunk, aka. the evicted chunk in #1, to be > removed from local pool and causes tiny pool to remove corresponding tiny > chunks again in {{LocalPool#remove()}}. > * In {{MicroQueueOfChunks#removeIf}}, due to previous in-progress > {{removeIf}}, it throws NPE as it violate MicroQueueOfChunks's assumption > which requires null chunks to be put at the back of queue. > > |[patch|https://github.com/apache/cassandra/pull/537]|[CI|https://circleci.com/workflow-run/a97317a0-ef21-4c01-9a97-82eaf28d7faf]| > The fix is to put null chunks to the back of queue before releasing any > chunks. -- 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-15726) buffer pool may throw NPE with concurrent release due to in-progress tiny pool eviction
[ https://issues.apache.org/jira/browse/CASSANDRA-15726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-15726: -- Reviewers: Aleksey Yeschenko > buffer pool may throw NPE with concurrent release due to in-progress tiny > pool eviction > --- > > Key: CASSANDRA-15726 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15726 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: ZhaoYang >Assignee: ZhaoYang >Priority: Normal > Fix For: 4.0-alpha > > > This can be reproduced by running {{LongBufferPoolTest}}, 1 out 5 runs.. > {code:java} > java.lang.NullPointerException > at > org.apache.cassandra.utils.memory.BufferPool$Chunk.access$1300(BufferPool.java:836) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.lambda$remove$1(BufferPool.java:716) > at > org.apache.cassandra.utils.memory.BufferPool$MicroQueueOfChunks.removeIf(BufferPool.java:460) > at > org.apache.cassandra.utils.memory.BufferPool$MicroQueueOfChunks.access$1500(BufferPool.java:304) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.remove(BufferPool.java:716) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.put(BufferPool.java:590) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.recycle(BufferPool.java:709) > at > org.apache.cassandra.utils.memory.BufferPool$Chunk.recycle(BufferPool.java:909) > at > org.apache.cassandra.utils.memory.BufferPool$Chunk.tryRecycle(BufferPool.java:903) > at > org.apache.cassandra.utils.memory.BufferPool$Chunk.release(BufferPool.java:896) > at > org.apache.cassandra.utils.memory.BufferPool$MicroQueueOfChunks.removeIf(BufferPool.java:465) > at > org.apache.cassandra.utils.memory.BufferPool$MicroQueueOfChunks.access$1500(BufferPool.java:304) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.addChunk(BufferPool.java:736) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.addChunkFromParent(BufferPool.java:725) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.tryGetInternal(BufferPool.java:691) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.tryGet(BufferPool.java:679) > at > org.apache.cassandra.utils.memory.BufferPool$LocalPool.access$000(BufferPool.java:518) > at > org.apache.cassandra.utils.memory.BufferPool.tryGet(BufferPool.java:120) > > at > org.apache.cassandra.utils.memory.LongBufferPoolTest$2.testOne(LongBufferPoolTest.java:497) > at > org.apache.cassandra.utils.memory.LongBufferPoolTest$TestUntil.call(LongBufferPoolTest.java:558) > at > org.apache.cassandra.utils.memory.LongBufferPoolTest$TestUntil.call(LongBufferPoolTest.java:538) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) > at java.lang.Thread.run(Thread.java:748) > {code} > The cause is that: > * When evicting a normal chunk from a full MicroQueueOfChunks, local pool > will try to remove corresponding tiny chunks, via > {{MicroQueueOfChunks#removeIf}}. > * If matching tiny chunk is found, tiny {{chunk.release()}} is called > immediately before moving null chunk to the back of the queue. > * Due to concurrent release from different threads, tiny {{chunk.release()}} > may cause its parent normal chunk, aka. the evicted chunk in #1, to be > removed from local pool and causes tiny pool to remove corresponding tiny > chunks again in {{LocalPool#remove()}}. > * In {{MicroQueueOfChunks#removeIf}}, due to previous in-progress > {{removeIf}}, it throws NPE as it violate MicroQueueOfChunks's assumption > which requires null chunks to be put at the back of queue. > > |[patch|https://github.com/apache/cassandra/pull/537]|[CI|https://circleci.com/workflow-run/a97317a0-ef21-4c01-9a97-82eaf28d7faf]| > The fix is to put null chunks to the back of queue before releasing any > chunks. -- 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-15727) Internode messaging connection setup between 4.0 and legacy SSL 3.0 fails if initial connection version incorrect
[ https://issues.apache.org/jira/browse/CASSANDRA-15727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-15727: -- Reviewers: Aleksey Yeschenko > Internode messaging connection setup between 4.0 and legacy SSL 3.0 fails if > initial connection version incorrect > - > > Key: CASSANDRA-15727 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15727 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Internode >Reporter: Jon Meredith >Assignee: Jon Meredith >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta > > Time Spent: 10m > Remaining Estimate: 0h > > This was discovered while testing upgrading an SSL enabled cluster from 3.0 > to 4.0. The 3.0 cluster was configured to only listen on the ssl storage > port. When the upgraded 4.0 node started it received a gossip messsage that > triggered a shadow round before it had correctly set the messaging versions > for the other endpoints. > Sending the message created the connection, but because the endpoint > defaulted to {code}VERSION_40{code} the initial connect attempt was to the > regular {code}storage_port{code}. The 3.0 node was only listening on the > {code}ssl_storage_port{code}, so the connection was refused and the > {code}OutboundCOnnection.onFailure{code} handler was called. As the shadow > gossip round had queued up a message, the {code}hasPending{code} branch was > followed and the connection was rescheduled, however the port is never > recalculated as the original settings are used so it always fails. > Meanwhile, the node discovered information about peers through inbound > connection and gossip updating the messaging version for the endpoint which > could have been used to make a valid connection. -- 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-15501) Duplicate results with DISTINCT queries in mixed mode 2.1/3.0
[ https://issues.apache.org/jira/browse/CASSANDRA-15501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-15501: Reviewers: Aleksey Yeschenko, Alex Petrov, Sam Tunnicliffe (was: Aleksey Yeschenko, Sam Tunnicliffe) > Duplicate results with DISTINCT queries in mixed mode 2.1/3.0 > - > > Key: CASSANDRA-15501 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15501 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > When a client switches coordinator from a 2.1 node to a 3.0 node it sends a > 2.1 paging state to the 3.0 node. The 2.1 {{PagingState}} does not have > {{remainingInPartition}} so on the 3.0 side we default this to > Integer.MAX_VALUE. This value is then used to decide if the lastKey should be > included in the result. -- 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-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083920#comment-17083920 ] Benjamin Lerer edited comment on CASSANDRA-15728 at 4/15/20, 12:54 PM: --- [jenkins ci-run|https://ci-cassandra.apache.org/job/Cassandra-devbranch/57/] was (Author: blerer): [jenkins ci-run|https://ci-cassandra.apache.org/job/Cassandra-devbranch/52/] > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 20m > Remaining Estimate: 0h > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) >
[jira] [Commented] (CASSANDRA-15501) Duplicate results with DISTINCT queries in mixed mode 2.1/3.0
[ https://issues.apache.org/jira/browse/CASSANDRA-15501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084042#comment-17084042 ] Marcus Eriksson commented on CASSANDRA-15501: - had to fix in-jvm upgrade tests, [~ifesdjeen] could you have a quick look at the two last (non-circle-ci) commits in the trunk branch below? branches: [2.2|https://github.com/krummas/cassandra/commits/marcuse/15501-2.2] [3.0|https://github.com/krummas/cassandra/commits/marcuse/15501] [3.11|https://github.com/krummas/cassandra/commits/marcuse/15501-3.11] [trunk|https://github.com/krummas/cassandra/commits/marcuse/15501-trunk] unit tests: [2.2|https://circleci.com/gh/krummas/cassandra/3175] [3.0|https://circleci.com/gh/krummas/cassandra/3169] [3.11|https://circleci.com/gh/krummas/cassandra/3171] [trunk|https://circleci.com/gh/krummas/cassandra/3192] jvm dtests [2.2|https://circleci.com/gh/krummas/cassandra/3176] [3.0|https://circleci.com/gh/krummas/cassandra/3168] [3.11|https://circleci.com/gh/krummas/cassandra/3170] [trunk|https://circleci.com/gh/krummas/cassandra/3193] jvm upgrade dtests [3.0|https://circleci.com/gh/krummas/cassandra/3179] [3.11|https://circleci.com/gh/krummas/cassandra/3180] (failure expected since we use 2.2 -> 3.0 for this upgrade test) [trunk|https://circleci.com/gh/krummas/cassandra/3198] dtests novnodes [3.0|https://circleci.com/gh/krummas/cassandra/3182] [3.11|https://circleci.com/gh/krummas/cassandra/3186] [trunk|https://circleci.com/gh/krummas/cassandra/3196] dtests vnodes [3.0|https://circleci.com/gh/krummas/cassandra/3181] [3.11|https://circleci.com/gh/krummas/cassandra/3185] [trunk|https://circleci.com/gh/krummas/cassandra/3197] > Duplicate results with DISTINCT queries in mixed mode 2.1/3.0 > - > > Key: CASSANDRA-15501 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15501 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > When a client switches coordinator from a 2.1 node to a 3.0 node it sends a > 2.1 paging state to the 3.0 node. The 2.1 {{PagingState}} does not have > {{remainingInPartition}} so on the 3.0 side we default this to > Integer.MAX_VALUE. This value is then used to decide if the lastKey should be > included in the result. -- 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-14825) Expose table schema for drivers
[ https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084039#comment-17084039 ] Benjamin Lerer commented on CASSANDRA-14825: [Jenkins ci-run|https://ci-cassandra.apache.org/job/Cassandra-devbranch/56/] > Expose table schema for drivers > --- > > Key: CASSANDRA-14825 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14825 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/CQL >Reporter: Chris Lohfink >Assignee: Robert Stupp >Priority: Normal > Labels: pull-request-available > Fix For: 4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Currently the drivers recreate the CQL for the tables by putting together the > system table values. This is very difficult to keep up to date and buggy > enough that its only even supported in Java and Python drivers. Cassandra > already has some limited output available for snapshots that we could provide > in a virtual table or new query that the drivers can fetch. This can greatly > reduce the complexity of drivers while also reducing bugs like > CASSANDRA-14822 as the underlying schema and properties change. -- 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-14825) Expose table schema for drivers
[ https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-14825: --- Reviewers: Benjamin Lerer, Benjamin Lerer (was: Benjamin Lerer) Benjamin Lerer, Benjamin Lerer (was: Benjamin Lerer) Status: Review In Progress (was: Patch Available) > Expose table schema for drivers > --- > > Key: CASSANDRA-14825 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14825 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/CQL >Reporter: Chris Lohfink >Assignee: Robert Stupp >Priority: Normal > Labels: pull-request-available > Fix For: 4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Currently the drivers recreate the CQL for the tables by putting together the > system table values. This is very difficult to keep up to date and buggy > enough that its only even supported in Java and Python drivers. Cassandra > already has some limited output available for snapshots that we could provide > in a virtual table or new query that the drivers can fetch. This can greatly > reduce the complexity of drivers while also reducing bugs like > CASSANDRA-14822 as the underlying schema and properties change. -- 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-15338) Fix flakey testMessagePurging - org.apache.cassandra.net.ConnectionTest
[ https://issues.apache.org/jira/browse/CASSANDRA-15338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-15338: -- Reviewers: Andres de la Peña, Andres de la Peña (was: Andres de la Peña) Andres de la Peña, Andres de la Peña (was: Andres de la Peña) Status: Review In Progress (was: Patch Available) > Fix flakey testMessagePurging - org.apache.cassandra.net.ConnectionTest > --- > > Key: CASSANDRA-15338 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15338 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: David Capwell >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Attachments: CASS-15338-Docker.zip > > Time Spent: 10m > Remaining Estimate: 0h > > Example failure: > [https://circleci.com/gh/dcapwell/cassandra/11#artifacts/containers/1] > > {code:java} > Testcase: testMessagePurging(org.apache.cassandra.net.ConnectionTest): FAILED > expected:<0> but was:<1> > junit.framework.AssertionFailedError: expected:<0> but was:<1> > at > org.apache.cassandra.net.ConnectionTest.lambda$testMessagePurging$38(ConnectionTest.java:625) > at > org.apache.cassandra.net.ConnectionTest.doTestManual(ConnectionTest.java:258) > at > org.apache.cassandra.net.ConnectionTest.testManual(ConnectionTest.java:231) > at > org.apache.cassandra.net.ConnectionTest.testMessagePurging(ConnectionTest.java:584){code} > > Looking closer at > org.apache.cassandra.net.OutboundConnection.Delivery#stopAndRun it seems that > the run method is called before > org.apache.cassandra.net.OutboundConnection.Delivery#doRun which may lead to > a test race condition where the CountDownLatch completes before executing -- 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-15729) Jenkins Test Results Report in plaintext and emailable
[ https://issues.apache.org/jira/browse/CASSANDRA-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15729: --- Labels: Jenkins (was: ) > Jenkins Test Results Report in plaintext and emailable > -- > > Key: CASSANDRA-15729 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15729 > Project: Cassandra > Issue Type: Task > Components: Build, CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Labels: Jenkins > Fix For: 4.0-beta > > > The Jenkins pipeline builds now aggregate all test reports. > For example: > - https://ci-cassandra.apache.org/job/Cassandra-trunk/68/testReport/ > - > https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-trunk/detail/Cassandra-trunk/68/tests > But Jenkins can only keep a limited amount of build history, so those links > are not permanent, can't be used as references, and don't help for bisecting > and blame on regressions (and flakey tests) over a longer period of time. > The builds@ ML can provide a permanent record of test results. > This was first brought up in these two threads: > - > https://lists.apache.org/thread.html/re8122e4fdd8629e7fbca2abf27d72054b3bc0e3690ece8b8e66f618b%40%3Cdev.cassandra.apache.org%3E > - > https://lists.apache.org/thread.html/ra5f6aeea89546825fe7ccc4a80898c62f8ed57decabf709d81d9c720%40%3Cdev.cassandra.apache.org%3E > An example plaintext report, to demonstrate feasibility, is available here: > https://lists.apache.org/thread.html/r80d13f7af706bf8dfbf2387fab46004c1fbd3917b7bc339c49e69aa8%40%3Cbuilds.cassandra.apache.org%3E > Hurdles: > - the ASF mailing lists won't except html, attachments, or any message body > over 1MB. > - packages are used as a differentiator in the final aggregated report. The > cqlsh and dtests currently don't specify it. It needs to be added as a > "dot-separated" prefix to the testsuite and testcase name. -- 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-15729) Jenkins Test Results Report in plaintext and emailable
[ https://issues.apache.org/jira/browse/CASSANDRA-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083993#comment-17083993 ] Michael Semb Wever edited comment on CASSANDRA-15729 at 4/15/20, 10:40 AM: --- Discussion on Jenkins emailext templates and related plugins: - https://lists.apache.org/thread.html/r245e945a0d668ec3c792c406b1a47e82fc5c78ad3fd7352f922e050c%40%3Cbuilds.apache.org%3E Work in progress: - https://github.com/thelastpickle/cassandra-builds/commit/1f98d39151284d5e76e132a54e64b55e569c4c8b was (Author: michaelsembwever): I asked about Jenkins emailext templates and related plugins here: https://lists.apache.org/thread.html/r245e945a0d668ec3c792c406b1a47e82fc5c78ad3fd7352f922e050c%40%3Cbuilds.apache.org%3E Work in progress: https://github.com/thelastpickle/cassandra-builds/commit/1f98d39151284d5e76e132a54e64b55e569c4c8b > Jenkins Test Results Report in plaintext and emailable > -- > > Key: CASSANDRA-15729 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15729 > Project: Cassandra > Issue Type: Task > Components: Build, CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 4.0-beta > > > The Jenkins pipeline builds now aggregate all test reports. > For example: > - https://ci-cassandra.apache.org/job/Cassandra-trunk/68/testReport/ > - > https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-trunk/detail/Cassandra-trunk/68/tests > But Jenkins can only keep a limited amount of build history, so those links > are not permanent, can't be used as references, and don't help for bisecting > and blame on regressions (and flakey tests) over a longer period of time. > The builds@ ML can provide a permanent record of test results. > This was first brought up in these two threads: > - > https://lists.apache.org/thread.html/re8122e4fdd8629e7fbca2abf27d72054b3bc0e3690ece8b8e66f618b%40%3Cdev.cassandra.apache.org%3E > - > https://lists.apache.org/thread.html/ra5f6aeea89546825fe7ccc4a80898c62f8ed57decabf709d81d9c720%40%3Cdev.cassandra.apache.org%3E > An example plaintext report, to demonstrate feasibility, is available here: > https://lists.apache.org/thread.html/r80d13f7af706bf8dfbf2387fab46004c1fbd3917b7bc339c49e69aa8%40%3Cbuilds.cassandra.apache.org%3E > Hurdles: > - the ASF mailing lists won't except html, attachments, or any message body > over 1MB. > - packages are used as a differentiator in the final aggregated report. The > cqlsh and dtests currently don't specify it. It needs to be added as a > "dot-separated" prefix to the testsuite and testcase name. -- 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-15729) Jenkins Test Results Report in plaintext and emailable
[ https://issues.apache.org/jira/browse/CASSANDRA-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083993#comment-17083993 ] Michael Semb Wever commented on CASSANDRA-15729: I asked about Jenkins emailext templates and related plugins here: https://lists.apache.org/thread.html/r245e945a0d668ec3c792c406b1a47e82fc5c78ad3fd7352f922e050c%40%3Cbuilds.apache.org%3E Work in progress: https://github.com/thelastpickle/cassandra-builds/commit/1f98d39151284d5e76e132a54e64b55e569c4c8b > Jenkins Test Results Report in plaintext and emailable > -- > > Key: CASSANDRA-15729 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15729 > Project: Cassandra > Issue Type: Task > Components: Build, CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 4.0-beta > > > The Jenkins pipeline builds now aggregate all test reports. > For example: > - https://ci-cassandra.apache.org/job/Cassandra-trunk/68/testReport/ > - > https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-trunk/detail/Cassandra-trunk/68/tests > But Jenkins can only keep a limited amount of build history, so those links > are not permanent, can't be used as references, and don't help for bisecting > and blame on regressions (and flakey tests) over a longer period of time. > The builds@ ML can provide a permanent record of test results. > This was first brought up in these two threads: > - > https://lists.apache.org/thread.html/re8122e4fdd8629e7fbca2abf27d72054b3bc0e3690ece8b8e66f618b%40%3Cdev.cassandra.apache.org%3E > - > https://lists.apache.org/thread.html/ra5f6aeea89546825fe7ccc4a80898c62f8ed57decabf709d81d9c720%40%3Cdev.cassandra.apache.org%3E > An example plaintext report, to demonstrate feasibility, is available here: > https://lists.apache.org/thread.html/r80d13f7af706bf8dfbf2387fab46004c1fbd3917b7bc339c49e69aa8%40%3Cbuilds.cassandra.apache.org%3E > Hurdles: > - the ASF mailing lists won't except html, attachments, or any message body > over 1MB. > - packages are used as a differentiator in the final aggregated report. The > cqlsh and dtests currently don't specify it. It needs to be added as a > "dot-separated" prefix to the testsuite and testcase name. -- 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-15729) Jenkins Test Results Report in plaintext and emailable
[ https://issues.apache.org/jira/browse/CASSANDRA-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15729: --- Change Category: Code Clarity Complexity: Normal Fix Version/s: 4.0-beta Assignee: Michael Semb Wever Status: Open (was: Triage Needed) > Jenkins Test Results Report in plaintext and emailable > -- > > Key: CASSANDRA-15729 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15729 > Project: Cassandra > Issue Type: Task > Components: Build, CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 4.0-beta > > > The Jenkins pipeline builds now aggregate all test reports. > For example: > - https://ci-cassandra.apache.org/job/Cassandra-trunk/68/testReport/ > - > https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-trunk/detail/Cassandra-trunk/68/tests > But Jenkins can only keep a limited amount of build history, so those links > are not permanent, can't be used as references, and don't help for bisecting > and blame on regressions (and flakey tests) over a longer period of time. > The builds@ ML can provide a permanent record of test results. > This was first brought up in these two threads: > - > https://lists.apache.org/thread.html/re8122e4fdd8629e7fbca2abf27d72054b3bc0e3690ece8b8e66f618b%40%3Cdev.cassandra.apache.org%3E > - > https://lists.apache.org/thread.html/ra5f6aeea89546825fe7ccc4a80898c62f8ed57decabf709d81d9c720%40%3Cdev.cassandra.apache.org%3E > An example plaintext report, to demonstrate feasibility, is available here: > https://lists.apache.org/thread.html/r80d13f7af706bf8dfbf2387fab46004c1fbd3917b7bc339c49e69aa8%40%3Cbuilds.cassandra.apache.org%3E > Hurdles: > - the ASF mailing lists won't except html, attachments, or any message body > over 1MB. > - packages are used as a differentiator in the final aggregated report. The > cqlsh and dtests currently don't specify it. It needs to be added as a > "dot-separated" prefix to the testsuite and testcase name. -- 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] [Created] (CASSANDRA-15729) Jenkins Test Results Report in plaintext and emailable
Michael Semb Wever created CASSANDRA-15729: -- Summary: Jenkins Test Results Report in plaintext and emailable Key: CASSANDRA-15729 URL: https://issues.apache.org/jira/browse/CASSANDRA-15729 Project: Cassandra Issue Type: Task Components: CI, Build Reporter: Michael Semb Wever The Jenkins pipeline builds now aggregate all test reports. For example: - https://ci-cassandra.apache.org/job/Cassandra-trunk/68/testReport/ - https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-trunk/detail/Cassandra-trunk/68/tests But Jenkins can only keep a limited amount of build history, so those links are not permanent, can't be used as references, and don't help for bisecting and blame on regressions (and flakey tests) over a longer period of time. The builds@ ML can provide a permanent record of test results. This was first brought up in these two threads: - https://lists.apache.org/thread.html/re8122e4fdd8629e7fbca2abf27d72054b3bc0e3690ece8b8e66f618b%40%3Cdev.cassandra.apache.org%3E - https://lists.apache.org/thread.html/ra5f6aeea89546825fe7ccc4a80898c62f8ed57decabf709d81d9c720%40%3Cdev.cassandra.apache.org%3E An example plaintext report, to demonstrate feasibility, is available here: https://lists.apache.org/thread.html/r80d13f7af706bf8dfbf2387fab46004c1fbd3917b7bc339c49e69aa8%40%3Cbuilds.cassandra.apache.org%3E Hurdles: - the ASF mailing lists won't except html, attachments, or any message body over 1MB. - packages are used as a differentiator in the final aggregated report. The cqlsh and dtests currently don't specify it. It needs to be added as a "dot-separated" prefix to the testsuite and testcase name. -- 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-15472) Read failure due to exception from metrics-core dependency
[ https://issues.apache.org/jira/browse/CASSANDRA-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083947#comment-17083947 ] Michael Semb Wever commented on CASSANDRA-15472: ||branch||circleci||jenkins|| |[cassandra_3.0_15472|https://github.com/apache/cassandra/compare/cassandra-3.0...sumanth-pasupuleti:bugfix/15472_30]|[circleci|https://circleci.com/gh/sumanth-pasupuleti/workflows/cassandra/tree/bugfix%2F15472_30]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/53/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/53]| |[cassandra_3.11_15472|https://github.com/apache/cassandra/compare/cassandra-3.11...sumanth-pasupuleti:bugfix/15472_311]|[circleci|https://circleci.com/gh/sumanth-pasupuleti/workflows/cassandra/tree/bugfix%2F15472_311]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/54/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/54]| |[trunk_15472|https://github.com/apache/cassandra/compare/trunk...sumanth-pasupuleti:bugfix/15472_40]|[circleci|https://circleci.com/gh/sumanth-pasupuleti/workflows/cassandra/tree/bugfix%2F15472_40]|[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/55/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/55]| > Read failure due to exception from metrics-core dependency > -- > > Key: CASSANDRA-15472 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15472 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Labels: lhf > Fix For: 4.0, 3.0.x, 3.11.x > > > Stacktrace > {code:java} > Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {} > java.util.NoSuchElementException: null > at > java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053) > ~[na:1.8.0_222] > at > com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102) > ~[metrics-core-2.2.0.jar:na] > at > com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Histogram.update(Histogram.java:110) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Timer.update(Timer.java:198) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Timer.update(Timer.java:76) > ~[metrics-core-2.2.0.jar:na] > at > org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_222] > at > org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) > [nf-cassandra-2.1.19.10.jar:2.1.19.10] > at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222] > {code} > This [issue|https://github.com/dropwizard/metrics/issues/1278] has been > [fixed|https://github.com/dropwizard/metrics/pull/1436] in > [v4.0.6|https://github.com/dropwizard/metrics/releases/tag/v4.0.6]. > This is observed on a 2.1.19 cluster, but this would impact pretty much any > version of C* since we depend on lower versions of metrics-core that do not > have the fix. -- 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-15472) Read failure due to exception from metrics-core dependency
[ https://issues.apache.org/jira/browse/CASSANDRA-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumanth Pasupuleti updated CASSANDRA-15472: --- Reviewers: Mick Semb Wever > Read failure due to exception from metrics-core dependency > -- > > Key: CASSANDRA-15472 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15472 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Labels: lhf > Fix For: 4.0, 3.0.x, 3.11.x > > > Stacktrace > {code:java} > Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {} > java.util.NoSuchElementException: null > at > java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053) > ~[na:1.8.0_222] > at > com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102) > ~[metrics-core-2.2.0.jar:na] > at > com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Histogram.update(Histogram.java:110) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Timer.update(Timer.java:198) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Timer.update(Timer.java:76) > ~[metrics-core-2.2.0.jar:na] > at > org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_222] > at > org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) > [nf-cassandra-2.1.19.10.jar:2.1.19.10] > at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222] > {code} > This [issue|https://github.com/dropwizard/metrics/issues/1278] has been > [fixed|https://github.com/dropwizard/metrics/pull/1436] in > [v4.0.6|https://github.com/dropwizard/metrics/releases/tag/v4.0.6]. > This is observed on a 2.1.19 cluster, but this would impact pretty much any > version of C* since we depend on lower versions of metrics-core that do not > have the fix. -- 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-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083920#comment-17083920 ] Benjamin Lerer edited comment on CASSANDRA-15728 at 4/15/20, 9:15 AM: -- [jenkins ci-run|https://ci-cassandra.apache.org/job/Cassandra-devbranch/52/] was (Author: blerer): [jenkins ci-run|https://ci-cassandra.apache.org/job/Cassandra-devbranch/51/] > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 20m > Remaining Estimate: 0h > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) >
[jira] [Commented] (CASSANDRA-15472) Read failure due to exception from metrics-core dependency
[ https://issues.apache.org/jira/browse/CASSANDRA-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083935#comment-17083935 ] Sumanth Pasupuleti commented on CASSANDRA-15472: Done with the code/lib changes. Running UTs, Dtests on CircleCI. Changes so far: https://github.com/apache/cassandra/compare/cassandra-3.0...sumanth-pasupuleti:bugfix/15472_30?expand=1 https://github.com/apache/cassandra/compare/cassandra-3.11...sumanth-pasupuleti:bugfix/15472_311?expand=1 https://github.com/apache/cassandra/compare/trunk...sumanth-pasupuleti:bugfix/15472_40?expand=1 > Read failure due to exception from metrics-core dependency > -- > > Key: CASSANDRA-15472 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15472 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Labels: lhf > Fix For: 4.0, 3.0.x, 3.11.x > > > Stacktrace > {code:java} > Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {} > java.util.NoSuchElementException: null > at > java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053) > ~[na:1.8.0_222] > at > com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102) > ~[metrics-core-2.2.0.jar:na] > at > com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Histogram.update(Histogram.java:110) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Timer.update(Timer.java:198) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Timer.update(Timer.java:76) > ~[metrics-core-2.2.0.jar:na] > at > org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_222] > at > org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) > [nf-cassandra-2.1.19.10.jar:2.1.19.10] > at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222] > {code} > This [issue|https://github.com/dropwizard/metrics/issues/1278] has been > [fixed|https://github.com/dropwizard/metrics/pull/1436] in > [v4.0.6|https://github.com/dropwizard/metrics/releases/tag/v4.0.6]. > This is observed on a 2.1.19 cluster, but this would impact pretty much any > version of C* since we depend on lower versions of metrics-core that do not > have the fix. -- 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-14825) Expose table schema for drivers
[ https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083928#comment-17083928 ] Benjamin Lerer commented on CASSANDRA-14825: Marking the fix version as 4.0 after discussion on the dev mailing list. > Expose table schema for drivers > --- > > Key: CASSANDRA-14825 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14825 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/CQL >Reporter: Chris Lohfink >Assignee: Robert Stupp >Priority: Normal > Labels: pull-request-available > Fix For: 4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Currently the drivers recreate the CQL for the tables by putting together the > system table values. This is very difficult to keep up to date and buggy > enough that its only even supported in Java and Python drivers. Cassandra > already has some limited output available for snapshots that we could provide > in a virtual table or new query that the drivers can fetch. This can greatly > reduce the complexity of drivers while also reducing bugs like > CASSANDRA-14822 as the underlying schema and properties change. -- 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-15724) Modify cassandra.yaml and replace the default data location, still data stored in default location
[ https://issues.apache.org/jira/browse/CASSANDRA-15724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083927#comment-17083927 ] Boopalan commented on CASSANDRA-15724: --- Thanks [~jmeredithco]. I have prepare a new ubuntu setup. # Install Java 1.8.0_242 # Install Cassandra 3.11.6 # Create ext4 filesystem on our SSD disk and mount in /mnt/ directory # Edit the cassandra.yaml file and replace all data, hints, saved_caches and commit to /mnt/ directory # Edit the cassandra-en.sh file and replace lineVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=*127*.0.0.1" # Edit jvm.options file -Dcassandra.config=/etc/cassandra/cassandra.yaml # Restart Cassandra # nodetool status Now am running into different issue. Please find the below snippet. {noformat} root@cassandra-master:/mnt/data/system_auth# systemctl status cassandra ● cassandra.service - LSB: distributed storage system for structured data Loaded: loaded (/etc/init.d/cassandra; generated) Active: active (exited) since Wed 2020-04-15 14:07:06 IST; 7min ago Docs: man:systemd-sysv-generator(8) Process: 29015 ExecStop=/etc/init.d/cassandra stop (code=exited, status=0/SUCCESS) Process: 29033 ExecStart=/etc/init.d/cassandra start (code=exited, status=0/SUCCESS) Apr 15 14:07:06 cassandra-master systemd[1]: Starting LSB: distributed storage system for structured data... Apr 15 14:07:06 cassandra-master systemd[1]: Started LSB: distributed storage system for structured data. {noformat} {noformat} root@cassandra-master:/etc/cassandra# nodetool status nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused (Connection refused)'. {noformat} *cat /var/log/cassandra/system.log* {noformat} ERROR [MemtableFlushWriter:1] 2020-04-15 14:07:14,791 LogTransaction.java:277 - Transaction log [md_txn_flush_4ed121f0-7ef4-11ea-8dc8-cf6c58093313.log in /mnt/data/system/local-7ad54392bcdd35a684174e047860b377] indicates txn was not completed, trying to abort it now ERROR [MemtableFlushWriter:1] 2020-04-15 14:07:14,795 LogTransaction.java:280 - Failed to abort transaction log [md_txn_flush_4ed121f0-7ef4-11ea-8dc8-cf6c58093313.log in /mnt/data/system/local-7ad54392bcdd35a684174e047860b377] java.lang.RuntimeException: java.nio.file.AccessDeniedException: /mnt/data/system/local-7ad54392bcdd35a684174e047860b377/md_txn_flush_4ed121f0-7ef4-11ea-8dc8-cf6c58093313.log at org.apache.cassandra.io.util.FileUtils.write(FileUtils.java:605) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.io.util.FileUtils.appendAndSync(FileUtils.java:586) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.db.lifecycle.LogReplica.append(LogReplica.java:104) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.db.lifecycle.LogReplicaSet.lambda$null$5(LogReplicaSet.java:224) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.utils.Throwables.perform(Throwables.java:113) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.utils.Throwables.perform(Throwables.java:103) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.db.lifecycle.LogReplicaSet.append(LogReplicaSet.java:224) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.db.lifecycle.LogFile.addRecord(LogFile.java:350) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.db.lifecycle.LogFile.abort(LogFile.java:269) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.utils.Throwables.perform(Throwables.java:113) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.utils.Throwables.perform(Throwables.java:103) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.utils.Throwables.perform(Throwables.java:98) ~[apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.db.lifecycle.LogTransaction$TransactionTidier.run(LogTransaction.java:278) [apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.db.lifecycle.LogTransaction$TransactionTidier.tidy(LogTransaction.java:260) [apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.utils.concurrent.Ref$GlobalState.release(Ref.java:326) [apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.utils.concurrent.Ref$State.ensureReleased(Ref.java:204) [apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.utils.concurrent.Ref.ensureReleased(Ref.java:124) [apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.db.lifecycle.LogTransaction.complete(LogTransaction.java:397) [apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.db.lifecycle.LogTransaction.doAbort(LogTransaction.java:414) [apache-cassandra-3.11.6.jar:3.11.6] at org.apache.cassandra.utils.concurrent.Transactional$AbstractTransactional.abort(Transactional.java:141)
[jira] [Updated] (CASSANDRA-14825) Expose table schema for drivers
[ https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-14825: --- Fix Version/s: 4.0 > Expose table schema for drivers > --- > > Key: CASSANDRA-14825 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14825 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/CQL >Reporter: Chris Lohfink >Assignee: Robert Stupp >Priority: Normal > Labels: pull-request-available > Fix For: 4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Currently the drivers recreate the CQL for the tables by putting together the > system table values. This is very difficult to keep up to date and buggy > enough that its only even supported in Java and Python drivers. Cassandra > already has some limited output available for snapshots that we could provide > in a virtual table or new query that the drivers can fetch. This can greatly > reduce the complexity of drivers while also reducing bugs like > CASSANDRA-14822 as the underlying schema and properties change. -- 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-14825) Expose table schema for drivers
[ https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-14825: --- Reviewers: Benjamin Lerer > Expose table schema for drivers > --- > > Key: CASSANDRA-14825 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14825 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/CQL >Reporter: Chris Lohfink >Assignee: Robert Stupp >Priority: Normal > Labels: pull-request-available > Time Spent: 1h 50m > Remaining Estimate: 0h > > Currently the drivers recreate the CQL for the tables by putting together the > system table values. This is very difficult to keep up to date and buggy > enough that its only even supported in Java and Python drivers. Cassandra > already has some limited output available for snapshots that we could provide > in a virtual table or new query that the drivers can fetch. This can greatly > reduce the complexity of drivers while also reducing bugs like > CASSANDRA-14822 as the underlying schema and properties change. -- 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-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083920#comment-17083920 ] Benjamin Lerer commented on CASSANDRA-15728: [jenkins ci-run|https://ci-cassandra.apache.org/job/Cassandra-devbranch/51/] > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 20m > Remaining Estimate: 0h > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line > 440, in pytest_collection_modifyitems >
[jira] [Commented] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083906#comment-17083906 ] Berenguer Blasi commented on CASSANDRA-15728: - +1 from me. Went over the PR and tested it indeed failed and it's fixed now. > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 20m > Remaining Estimate: 0h > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line > 440, in pytest_collection_modifyitems >
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15728: Reviewers: Berenguer Blasi (was: Berenguer Blasi, Eduard Tudenhoefner) > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 20m > Remaining Estimate: 0h > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line > 440, in pytest_collection_modifyitems > INTERNALERROR> raise
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15728: Reviewers: Berenguer Blasi, Eduard Tudenhoefner (was: Berenguer Blasi) Status: Review In Progress (was: Patch Available) > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 20m > Remaining Estimate: 0h > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line > 440, in
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15728: Reviewers: Berenguer Blasi > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 10m > Remaining Estimate: 0h > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line > 440, in pytest_collection_modifyitems > INTERNALERROR> raise Exception("Required dtest arguments were missing! > You must
[jira] [Updated] (CASSANDRA-15472) Read failure due to exception from metrics-core dependency
[ https://issues.apache.org/jira/browse/CASSANDRA-15472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15472: --- Labels: lhf (was: ) > Read failure due to exception from metrics-core dependency > -- > > Key: CASSANDRA-15472 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15472 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Labels: lhf > Fix For: 4.0, 3.0.x, 3.11.x > > > Stacktrace > {code:java} > Uncaught exception on thread Thread[SharedPool-Worker-27,5,main]: {} > java.util.NoSuchElementException: null > at > java.util.concurrent.ConcurrentSkipListMap.firstKey(ConcurrentSkipListMap.java:2053) > ~[na:1.8.0_222] > at > com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:102) > ~[metrics-core-2.2.0.jar:na] > at > com.yammer.metrics.stats.ExponentiallyDecayingSample.update(ExponentiallyDecayingSample.java:81) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Histogram.update(Histogram.java:110) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Timer.update(Timer.java:198) > ~[metrics-core-2.2.0.jar:na] > at com.yammer.metrics.core.Timer.update(Timer.java:76) > ~[metrics-core-2.2.0.jar:na] > at > org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:108) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.metrics.LatencyMetrics.addNano(LatencyMetrics.java:114) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1897) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at org.apache.cassandra.db.Keyspace.getRow(Keyspace.java:353) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:85) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:47) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:64) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_222] > at > org.apache.cassandra.concurrent.AbstractTracingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164) > ~[nf-cassandra-2.1.19.10.jar:2.1.19.10] > at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) > [nf-cassandra-2.1.19.10.jar:2.1.19.10] > at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222] > {code} > This [issue|https://github.com/dropwizard/metrics/issues/1278] has been > [fixed|https://github.com/dropwizard/metrics/pull/1436] in > [v4.0.6|https://github.com/dropwizard/metrics/releases/tag/v4.0.6]. > This is observed on a 2.1.19 cluster, but this would impact pretty much any > version of C* since we depend on lower versions of metrics-core that do not > have the fix. -- 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-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15728: Test and Documentation Plan: run *pytest sometest.py* with *cassandra_dir* being set in *pytest.ini* Status: Patch Available (was: In Progress) > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > Time Spent: 10m > Remaining Estimate: 0h > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File >
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-15728: --- Labels: pull-request-available (was: ) > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-alpha > > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line > 440, in pytest_collection_modifyitems > INTERNALERROR> raise Exception("Required dtest arguments were missing! > You must provide either --cassandra-dir " > INTERNALERROR>
[jira] [Updated] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
[ https://issues.apache.org/jira/browse/CASSANDRA-15728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Tudenhoefner updated CASSANDRA-15728: Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Discovered By: User Report Fix Version/s: 4.0-alpha Severity: Low Status: Open (was: Triage Needed) > Setting "cassandra_dir" in pytest.ini has no effect > --- > > Key: CASSANDRA-15728 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest >Reporter: Eduard Tudenhoefner >Assignee: Eduard Tudenhoefner >Priority: Normal > Fix For: 4.0-alpha > > > Setting *cassandra_dir* in *pytest.ini* should not require specifying > *--cassandra-dir* on the command line: > {code} > $ pytest cql_tracing_test.py > > test session starts > = > platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 > rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: > pytest.ini > plugins: timeout-1.3.4, flaky-3.6.1 > timeout: 900.0s > timeout method: signal > timeout func_only: False > collecting 4 items > > > > INTERNALERROR> Traceback (most recent call last): > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, > in wrap_session > INTERNALERROR> session.exitstatus = doit(config, session) or 0 > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, > in _main > INTERNALERROR> config.hook.pytest_collection(session=session) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, > in pytest_collection > INTERNALERROR> return session.perform_collect() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, > in perform_collect > INTERNALERROR> session=self, config=self.config, items=items > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, > in __call__ > INTERNALERROR> return self._hookexec(self, self._nonwrappers + > self._wrappers, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, > in _hookexec > INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, > in > INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, > in _multicall > INTERNALERROR> return outcome.get_result() > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, > in get_result > INTERNALERROR> raise ex[1].with_traceback(ex[2]) > INTERNALERROR> File > "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, > in _multicall > INTERNALERROR> res = hook_impl.function(*args) > INTERNALERROR> File > "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line > 440, in pytest_collection_modifyitems
[jira] [Created] (CASSANDRA-15728) Setting "cassandra_dir" in pytest.ini has no effect
Eduard Tudenhoefner created CASSANDRA-15728: --- Summary: Setting "cassandra_dir" in pytest.ini has no effect Key: CASSANDRA-15728 URL: https://issues.apache.org/jira/browse/CASSANDRA-15728 Project: Cassandra Issue Type: Bug Components: Test/dtest Reporter: Eduard Tudenhoefner Assignee: Eduard Tudenhoefner Setting *cassandra_dir* in *pytest.ini* should not require specifying *--cassandra-dir* on the command line: {code} $ pytest cql_tracing_test.py test session starts = platform linux -- Python 3.6.9, pytest-3.6.4, py-1.8.1, pluggy-0.7.1 rootdir: /home/nastra/Development/pycharm-projects/cassandra-dtest, inifile: pytest.ini plugins: timeout-1.3.4, flaky-3.6.1 timeout: 900.0s timeout method: signal timeout func_only: False collecting 4 items INTERNALERROR> Traceback (most recent call last): INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 178, in wrap_session INTERNALERROR> session.exitstatus = doit(config, session) or 0 INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 214, in _main INTERNALERROR> config.hook.pytest_collection(session=session) INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, in __call__ INTERNALERROR> return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs) INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, in _hookexec INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, in INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, in _multicall INTERNALERROR> return outcome.get_result() INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, in get_result INTERNALERROR> raise ex[1].with_traceback(ex[2]) INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, in _multicall INTERNALERROR> res = hook_impl.function(*args) INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 224, in pytest_collection INTERNALERROR> return session.perform_collect() INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/_pytest/main.py", line 429, in perform_collect INTERNALERROR> session=self, config=self.config, items=items INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/hooks.py", line 258, in __call__ INTERNALERROR> return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs) INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 67, in _hookexec INTERNALERROR> return self._inner_hookexec(hook, methods, kwargs) INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/manager.py", line 61, in INTERNALERROR> firstresult=hook.spec_opts.get('firstresult'), INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 201, in _multicall INTERNALERROR> return outcome.get_result() INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 76, in get_result INTERNALERROR> raise ex[1].with_traceback(ex[2]) INTERNALERROR> File "/home/nastra/dtest/lib/python3.6/site-packages/pluggy/callers.py", line 180, in _multicall INTERNALERROR> res = hook_impl.function(*args) INTERNALERROR> File "/home/nastra/Development/pycharm-projects/cassandra-dtest/conftest.py", line 440, in pytest_collection_modifyitems INTERNALERROR> raise Exception("Required dtest arguments were missing! You must provide either --cassandra-dir " INTERNALERROR> Exception: Required dtest arguments were missing! You must provide either --cassandra-dir or --cassandra-version. Refer to the documentation or invoke the help with --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