[jira] [Comment Edited] (CASSANDRA-15907) Operational Improvements & Hardening for Replica Filtering Protection
[
https://issues.apache.org/jira/browse/CASSANDRA-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152248#comment-17152248
]
Caleb Rackliffe edited comment on CASSANDRA-15907 at 7/21/20, 3:09 AM:
---
[~jwest] I've hopefully addressed the points from [~adelapena]'s first round of
review, so I think this is officially ready for a second reviewer.
3.0: [patch|https://github.com/apache/cassandra/pull/659],
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra/66/workflows/c3e60efe-a50e-47ff-a8a7-51de36deb17b]
WIP (avoid review ATM)
3.11: [patch|https://github.com/apache/cassandra/pull/665],
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra/38/workflows/c3a3b51b-d105-49d9-91f8-2a149cf211b6]
trunk: [patch|https://github.com/apache/cassandra/pull/666], [j8
CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra/37/workflows/84e48d9e-f3dd-45ff-b70a-b69a86f6eb96]
[j11 Circle
CI|https://app.circleci.com/pipelines/github/maedhroz/cassandra/37/workflows/79b581ab-94a1-4920-a894-7f0f91ef466b]
If we're happy with the implementation, the next step will be to do some basic
stress testing.
Note: Existing issues described by CASSANDRA-14595 (Thrift dtest) and
CASSANDRA-15881 (SASI memtable switching) are visible in the test results so
far.
was (Author: maedhroz):
[~jwest] I've hopefully addressed the points from [~adelapena]'s first round of
review, so I think this is officially ready for a second reviewer.
3.0: [patch|https://github.com/apache/cassandra/pull/659],
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra/60/workflows/37dcf29a-effb-425a-95de-2362949942c5]
WIP (avoid review ATM)
3.11: [patch|https://github.com/apache/cassandra/pull/665],
[CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra/38/workflows/c3a3b51b-d105-49d9-91f8-2a149cf211b6]
trunk: [patch|https://github.com/apache/cassandra/pull/666], [j8
CircleCI|https://app.circleci.com/pipelines/github/maedhroz/cassandra/37/workflows/84e48d9e-f3dd-45ff-b70a-b69a86f6eb96]
[j11 Circle
CI|https://app.circleci.com/pipelines/github/maedhroz/cassandra/37/workflows/79b581ab-94a1-4920-a894-7f0f91ef466b]
If we're happy with the implementation, the next step will be to do some basic
stress testing.
Note: Existing issues described by CASSANDRA-14595 (Thrift dtest) and
CASSANDRA-15881 (SASI memtable switching) are visible in the test results so
far.
> Operational Improvements & Hardening for Replica Filtering Protection
> -
>
> Key: CASSANDRA-15907
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15907
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination, Feature/2i Index
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Labels: 2i, memory
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> CASSANDRA-8272 uses additional space on the heap to ensure correctness for 2i
> and filtering queries at consistency levels above ONE/LOCAL_ONE. There are a
> few things we should follow up on, however, to make life a bit easier for
> operators and generally de-risk usage:
> (Note: Line numbers are based on {{trunk}} as of
> {{3cfe3c9f0dcf8ca8b25ad111800a21725bf152cb}}.)
> *Minor Optimizations*
> * {{ReplicaFilteringProtection:114}} - Given we size them up-front, we may be
> able to use simple arrays instead of lists for {{rowsToFetch}} and
> {{originalPartitions}}. Alternatively (or also), we may be able to null out
> references in these two collections more aggressively. (ex. Using
> {{ArrayList#set()}} instead of {{get()}} in {{queryProtectedPartitions()}},
> assuming we pass {{toFetch}} as an argument to {{querySourceOnKey()}}.)
> * {{ReplicaFilteringProtection:323}} - We may be able to use
> {{EncodingStats.merge()}} and remove the custom {{stats()}} method.
> * {{DataResolver:111 & 228}} - Cache an instance of
> {{UnaryOperator#identity()}} instead of creating one on the fly.
> * {{ReplicaFilteringProtection:217}} - We may be able to scatter/gather
> rather than serially querying every row that needs to be completed. This
> isn't a clear win perhaps, given it targets the latency of single queries and
> adds some complexity. (Certainly a decent candidate to kick even out of this
> issue.)
> *Documentation and Intelligibility*
> * There are a few places (CHANGES.txt, tracing output in
> {{ReplicaFilteringProtection}}, etc.) where we mention "replica-side
> filtering protection" (which makes it seem like the coordinator doesn't
> filter) rather than "replica filtering protection" (which sounds more like
> what we actually do, which is protect
[jira] [Updated] (CASSANDRA-15907) Operational Improvements & Hardening for Replica Filtering Protection
[
https://issues.apache.org/jira/browse/CASSANDRA-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-15907:
Source Control Link: https://github.com/apache/cassandra/pull/659 (3.0)
> Operational Improvements & Hardening for Replica Filtering Protection
> -
>
> Key: CASSANDRA-15907
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15907
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination, Feature/2i Index
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Labels: 2i, memory
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> CASSANDRA-8272 uses additional space on the heap to ensure correctness for 2i
> and filtering queries at consistency levels above ONE/LOCAL_ONE. There are a
> few things we should follow up on, however, to make life a bit easier for
> operators and generally de-risk usage:
> (Note: Line numbers are based on {{trunk}} as of
> {{3cfe3c9f0dcf8ca8b25ad111800a21725bf152cb}}.)
> *Minor Optimizations*
> * {{ReplicaFilteringProtection:114}} - Given we size them up-front, we may be
> able to use simple arrays instead of lists for {{rowsToFetch}} and
> {{originalPartitions}}. Alternatively (or also), we may be able to null out
> references in these two collections more aggressively. (ex. Using
> {{ArrayList#set()}} instead of {{get()}} in {{queryProtectedPartitions()}},
> assuming we pass {{toFetch}} as an argument to {{querySourceOnKey()}}.)
> * {{ReplicaFilteringProtection:323}} - We may be able to use
> {{EncodingStats.merge()}} and remove the custom {{stats()}} method.
> * {{DataResolver:111 & 228}} - Cache an instance of
> {{UnaryOperator#identity()}} instead of creating one on the fly.
> * {{ReplicaFilteringProtection:217}} - We may be able to scatter/gather
> rather than serially querying every row that needs to be completed. This
> isn't a clear win perhaps, given it targets the latency of single queries and
> adds some complexity. (Certainly a decent candidate to kick even out of this
> issue.)
> *Documentation and Intelligibility*
> * There are a few places (CHANGES.txt, tracing output in
> {{ReplicaFilteringProtection}}, etc.) where we mention "replica-side
> filtering protection" (which makes it seem like the coordinator doesn't
> filter) rather than "replica filtering protection" (which sounds more like
> what we actually do, which is protect ourselves against incorrect replica
> filtering results). It's a minor fix, but would avoid confusion.
> * The method call chain in {{DataResolver}} might be a bit simpler if we put
> the {{repairedDataTracker}} in {{ResolveContext}}.
> *Testing*
> * I want to bite the bullet and get some basic tests for RFP (including any
> guardrails we might add here) onto the in-JVM dtest framework.
> *Guardrails*
> * As it stands, we don't have a way to enforce an upper bound on the memory
> usage of {{ReplicaFilteringProtection}} which caches row responses from the
> first round of requests. (Remember, these are later used to merged with the
> second round of results to complete the data for filtering.) Operators will
> likely need a way to protect themselves, i.e. simply fail queries if they hit
> a particular threshold rather than GC nodes into oblivion. (Having control
> over limits and page sizes doesn't quite get us there, because stale results
> _expand_ the number of incomplete results we must cache.) The fun question is
> how we do this, with the primary axes being scope (per-query, global, etc.)
> and granularity (per-partition, per-row, per-cell, actual heap usage, etc.).
> My starting disposition on the right trade-off between
> performance/complexity and accuracy is having something along the lines of
> cached rows per query. Prior art suggests this probably makes sense alongside
> things like {{tombstone_failure_threshold}} in {{cassandra.yaml}}.
--
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] (CASSANDRASC-23) Set up structure for handling multiple Cassandra versions
[
https://issues.apache.org/jira/browse/CASSANDRASC-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161620#comment-17161620
]
Jon Haddad edited comment on CASSANDRASC-23 at 7/21/20, 12:22 AM:
--
I've updated the patch to use Kubernetes instead of Docker directly since it
seems to be more ubiquitous. I've run the tests on my mac with minikube, and
microk8s in CircleCI. I've provided environment variables to support different
configurations as well as a setup script which will guide developers through
initial setup of their machines.
https://github.com/apache/cassandra-sidecar/pull/14
CircleCI runs here:
https://app.circleci.com/pipelines/github/rustyrazorblade/cassandra-sidecar?branch=jon%2F23%2Fmultiple-cassandra-versions
was (Author: rustyrazorblade):
I've updated the patch to use Kubernetes instead of Docker directly since it
seems to be more ubiquitous. I've run the tests on my mac with minikube, and
microk8s in CircleCI. I've provided environment variables to support different
configurations as well as a setup script which will guide developers through
initial setup of their machines.
https://github.com/apache/cassandra-sidecar/pull/14
CircleCI runs here:
https://app.circleci.com/pipelines/github/rustyrazorblade/cassandra-sidecar
> Set up structure for handling multiple Cassandra versions
> -
>
> Key: CASSANDRASC-23
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-23
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Jon Haddad
>Assignee: Jon Haddad
>Priority: Normal
>
> The first sidecar release will be for Cassandra 4.0, but one of the project
> goals is to be able to handle multiple versions. This will be especially
> important in mixed version clusters, or even mixed version 1:N sidecar to C*
> nodes (see CASSANDRASC-17).
> This JIRA is to lay the foundational work for supporting multiple Cassandra
> versions.
> Each Cassandra version (for example \{{cassandra40}}, \{{cassandra50}}, will
> be in a separate Gradle subproject, implementing a common interface defined
> in a \{{common}} subproject. A common cassandra integration testing
> framework will be able to test every version to ensure each version adheres
> to the expected interface.
> Each module will define the minimum compatibility it supports, so if someone
> (for example) wants to implement a Cassandra30 module for their own cluster,
> they will have the ability to do so.
--
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] (CASSANDRASC-17) Ensure sidecar can control multiple Cassandra instances
[ https://issues.apache.org/jira/browse/CASSANDRASC-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Haddad updated CASSANDRASC-17: -- Resolution: Won't Fix Status: Resolved (was: Triage Needed) I'm going to close this out since I don't plan on implementing it and I'm not sure if it's worth it anymore. > Ensure sidecar can control multiple Cassandra instances > --- > > Key: CASSANDRASC-17 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-17 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Jon Haddad >Priority: Normal > > Since we can run multiple hosts per node, we should allow a single sidecar > process to control multiple Cassandra nodes. > I am not sure if we should encode the id of the node in the URL or as a > parameter that would have to be present in every request if using > 1 node. > I lean towards the latter - meaning it’s a slight inconvenience for a very > small group, rather than messing with the URL scheme for everyone else. I > don’t hold this opinion very strongly though. I’d like to discuss before > doing any work here. > Thoughts? -- 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] (CASSANDRASC-23) Set up structure for handling multiple Cassandra versions
[
https://issues.apache.org/jira/browse/CASSANDRASC-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161620#comment-17161620
]
Jon Haddad edited comment on CASSANDRASC-23 at 7/21/20, 12:10 AM:
--
I've updated the patch to use Kubernetes instead of Docker directly since it
seems to be more ubiquitous. I've run the tests on my mac with minikube, and
microk8s in CircleCI. I've provided environment variables to support different
configurations as well as a setup script which will guide developers through
initial setup of their machines.
https://github.com/apache/cassandra-sidecar/pull/14
CircleCI runs here:
https://app.circleci.com/pipelines/github/rustyrazorblade/cassandra-sidecar
was (Author: rustyrazorblade):
I've updated the patch to use Kubernetes instead of Docker directly since it
seems to be more ubiquitous. I've run the tests on my mac with minikube, and
microk8s in CircleCI. I've provided environment variables to support different
configurations as well as a setup script which will guide developers through
initial setup of their machines.
https://github.com/apache/cassandra-sidecar/pull/14
> Set up structure for handling multiple Cassandra versions
> -
>
> Key: CASSANDRASC-23
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-23
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Jon Haddad
>Assignee: Jon Haddad
>Priority: Normal
>
> The first sidecar release will be for Cassandra 4.0, but one of the project
> goals is to be able to handle multiple versions. This will be especially
> important in mixed version clusters, or even mixed version 1:N sidecar to C*
> nodes (see CASSANDRASC-17).
> This JIRA is to lay the foundational work for supporting multiple Cassandra
> versions.
> Each Cassandra version (for example \{{cassandra40}}, \{{cassandra50}}, will
> be in a separate Gradle subproject, implementing a common interface defined
> in a \{{common}} subproject. A common cassandra integration testing
> framework will be able to test every version to ensure each version adheres
> to the expected interface.
> Each module will define the minimum compatibility it supports, so if someone
> (for example) wants to implement a Cassandra30 module for their own cluster,
> they will have the ability to do so.
--
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] (CASSANDRASC-23) Set up structure for handling multiple Cassandra versions
[
https://issues.apache.org/jira/browse/CASSANDRASC-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Haddad updated CASSANDRASC-23:
--
Test and Documentation Plan:
[CircleCI|https://app.circleci.com/pipelines/github/rustyrazorblade/cassandra-sidecar]
was:
[CircleCI|https://app.circleci.com/pipelines/github/rustyrazorblade/cassandra-sidecar?branch=jon%2F23%2Fmultiple-cassandra-versions]
> Set up structure for handling multiple Cassandra versions
> -
>
> Key: CASSANDRASC-23
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-23
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Jon Haddad
>Assignee: Jon Haddad
>Priority: Normal
>
> The first sidecar release will be for Cassandra 4.0, but one of the project
> goals is to be able to handle multiple versions. This will be especially
> important in mixed version clusters, or even mixed version 1:N sidecar to C*
> nodes (see CASSANDRASC-17).
> This JIRA is to lay the foundational work for supporting multiple Cassandra
> versions.
> Each Cassandra version (for example \{{cassandra40}}, \{{cassandra50}}, will
> be in a separate Gradle subproject, implementing a common interface defined
> in a \{{common}} subproject. A common cassandra integration testing
> framework will be able to test every version to ensure each version adheres
> to the expected interface.
> Each module will define the minimum compatibility it supports, so if someone
> (for example) wants to implement a Cassandra30 module for their own cluster,
> they will have the ability to do so.
--
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] (CASSANDRASC-23) Set up structure for handling multiple Cassandra versions
[
https://issues.apache.org/jira/browse/CASSANDRASC-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161620#comment-17161620
]
Jon Haddad commented on CASSANDRASC-23:
---
I've updated the patch to use Kubernetes instead of Docker directly since it
seems to be more ubiquitous. I've run the tests on my mac with minikube, and
microk8s in CircleCI. I've provided environment variables to support different
configurations as well as a setup script which will guide developers through
initial setup of their machines.
https://github.com/apache/cassandra-sidecar/pull/14
> Set up structure for handling multiple Cassandra versions
> -
>
> Key: CASSANDRASC-23
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-23
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Jon Haddad
>Assignee: Jon Haddad
>Priority: Normal
>
> The first sidecar release will be for Cassandra 4.0, but one of the project
> goals is to be able to handle multiple versions. This will be especially
> important in mixed version clusters, or even mixed version 1:N sidecar to C*
> nodes (see CASSANDRASC-17).
> This JIRA is to lay the foundational work for supporting multiple Cassandra
> versions.
> Each Cassandra version (for example \{{cassandra40}}, \{{cassandra50}}, will
> be in a separate Gradle subproject, implementing a common interface defined
> in a \{{common}} subproject. A common cassandra integration testing
> framework will be able to test every version to ensure each version adheres
> to the expected interface.
> Each module will define the minimum compatibility it supports, so if someone
> (for example) wants to implement a Cassandra30 module for their own cluster,
> they will have the ability to do so.
--
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-15953) Support fetching all user tables to compare in Cassandra-diff
[
https://issues.apache.org/jira/browse/CASSANDRA-15953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161611#comment-17161611
]
Yifan Cai commented on CASSANDRA-15953:
---
Log from the manual spark job testing.
{code:java}
➜ docker run --name cas-src -d -p 9042:9042 cassandra:3.0.18
➜ docker run --name cas-tgt -d -p 9043:9042 cassandra:latest
➜ docker exec cas-src cassandra-stress write n=1k -schema keyspace="keyspace1"
➜ docker exec cas-tgt cassandra-stress write n=1k -schema keyspace="keyspace1"
➜ docker exec cas-src cassandra-stress write n=1k -schema keyspace="keyspace2"
➜ docker exec cas-tgt cassandra-stress write n=1k -schema keyspace="keyspace2"
➜ spark-submit --files ./spark-job/localconfig-auto-discover.yaml --class
org.apache.cassandra.diff.DiffJob
spark-uberjar/target/spark-uberjar-0.2-SNAPSHOT.jar
localconfig-auto-discover.yaml
// The diff job yields the following result.
INFO DiffJob: FINISHED: {KeyspaceTablePair{keyspace=keyspace1,
table=counter1}=Matched Partitions - 0, Mismatched Partitions - 0, Partition
Errors - 0, Partitions Only In Source - 0, Partitions Only In Target - 0,
Skipped Partitions - 0, Matched Rows - 0, Matched Values - 0, Mismatched Values
- 0 , KeyspaceTablePair{keyspace=keyspace1, table=standard1}=Matched Partitions
- 1000, Mismatched Partitions - 0, Partition Errors - 0, Partitions Only In
Source - 0, Partitions Only In Target - 0, Skipped Partitions - 0, Matched Rows
- 1000, Matched Values - 6000, Mismatched Values - 0 ,
KeyspaceTablePair{keyspace=keyspace2, table=standard1}=Matched Partitions -
1000, Mismatched Partitions - 0, Partition Errors - 0, Partitions Only In
Source - 0, Partitions Only In Target - 0, Skipped Partitions - 0, Matched Rows
- 1000, Matched Values - 6000, Mismatched Values - 0 ,
KeyspaceTablePair{keyspace=keyspace2, table=counter1}=Matched Partitions - 0,
Mismatched Partitions - 0, Partition Errors - 0, Partitions Only In Source - 0,
Partitions Only In Target - 0, Skipped Partitions - 0, Matched Rows - 0,
Matched Values - 0, Mismatched Values - 0 }
{code}
> Support fetching all user tables to compare in Cassandra-diff
> -
>
> Key: CASSANDRA-15953
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15953
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/diff
>Reporter: Yifan Cai
>Assignee: Yifan Cai
>Priority: Normal
>
> The spark diff job may fail to launch with kernel error "E2BIG: Argument list
> too long", when passing a large list of keyspace table list to compare.
> Proposing a mode to fetch all user tables from the clusters to be compared.
> When the mode is on, the spark job ignores the parameter "keyspace_tables".
--
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-website] branch asf-staging updated (f3aefc2 -> eb9e4d8)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. discard f3aefc2 generate docs for 7d367b75 add acdbe09 ninja-fix: 4.0-beta1 blog post: island -> iland new eb9e4d8 generate docs for acdbe09b This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (f3aefc2) \ N -- N -- N refs/heads/asf-staging (eb9e4d8) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/blog/2020/07/20/apache-cassandra-4-0-beta1.html | 2 +- content/feed.xml | 4 ++-- src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (3edfa83 -> f3aefc2)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. omit 3edfa83 generate docs for 39d5bcc8 add c5b7637 ninja-fix: download link in blog post add 7d367b7 make changes to index.html to update companies, add third-party page new f3aefc2 generate docs for 7d367b75 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (3edfa83) \ N -- N -- N refs/heads/asf-staging (f3aefc2) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../2020/07/20/apache-cassandra-4-0-beta1.html | 2 +- content/blog/index.html| 2 +- content/community/index.html | 13 +- content/feed.xml | 4 +- content/index.html | 22 +- content/third-party/index.html | 241 + .../2020-07-20-apache-cassandra-4-0-beta1.markdown | 2 +- src/community.md | 12 +- src/index.html | 22 +- src/third-party.md | 79 +++ 10 files changed, 362 insertions(+), 37 deletions(-) create mode 100644 content/third-party/index.html create mode 100644 src/third-party.md - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch master updated: ninja-fix: 4.0-beta1 blog post: island -> iland
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-website.git The following commit(s) were added to refs/heads/master by this push: new acdbe09 ninja-fix: 4.0-beta1 blog post: island -> iland acdbe09 is described below commit acdbe09b46f67dc78719b6ed69d5d0beb9bf1f67 Author: mck AuthorDate: Tue Jul 21 00:39:33 2020 +0200 ninja-fix: 4.0-beta1 blog post: island -> iland --- src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown b/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown index 0fab207..b62fb87 100644 --- a/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown +++ b/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown @@ -9,7 +9,7 @@ categories: blog This is the most **stable** Apache Cassandra in history; you should start using Apache Cassandra 4.0 Beta today in your test and QA environments, head to the [downloads site](https://cassandra.apache.org/download/) to get your hands on it. The Cassandra community is on a mission to deliver a 4.0 GA release that is ready to be deployed to production. You can guarantee this holds true by running your application workloads against the Beta release and contributing to the community's validat [...] -With over 1,000 bug fixes, improvements and new features and the project's wholehearted [focus on quality](https://cassandra.apache.org/blog/2018/08/21/testing_apache_cassandra.html) with [replay, fuzz, property-based, fault-injection](https://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html), and performance tests on clusters as large as 1,000 nodes and with hundreds of real world use cases and schemas tested, Cassandra 4.0 redefines what users should e [...] +With over 1,000 bug fixes, improvements and new features and the project's wholehearted [focus on quality](https://cassandra.apache.org/blog/2018/08/21/testing_apache_cassandra.html) with [replay, fuzz, property-based, fault-injection](https://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html), and performance tests on clusters as large as 1,000 nodes and with hundreds of real world use cases and schemas tested, Cassandra 4.0 redefines what users should e [...] There will be no new features or breaking API changes in future Beta or GA builds. You can expect the time you put into the beta to translate into transitioning your production workloads to 4.0 in the near future. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-site updated: ninja-fix: 4.0-beta1 blog post: island -> iland
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/asf-site by this push: new eca9a6e ninja-fix: 4.0-beta1 blog post: island -> iland eca9a6e is described below commit eca9a6e27a5c432de2ddb31f32a3c08c950ffd4a Author: mck AuthorDate: Tue Jul 21 00:38:31 2020 +0200 ninja-fix: 4.0-beta1 blog post: island -> iland --- content/blog/2020/07/20/apache-cassandra-4-0-beta1.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2020/07/20/apache-cassandra-4-0-beta1.html b/content/blog/2020/07/20/apache-cassandra-4-0-beta1.html index 6972093..b696112 100644 --- a/content/blog/2020/07/20/apache-cassandra-4-0-beta1.html +++ b/content/blog/2020/07/20/apache-cassandra-4-0-beta1.html @@ -100,7 +100,7 @@ This is the most stable Apache Cassandra in history; you should start using Apache Cassandra 4.0 Beta today in your test and QA environments, head to the https://cassandra.apache.org/download/;>downloads site to get your hands on it. The Cassandra community is on a mission to deliver a 4.0 GA release that is ready to be deployed to production. You can guarantee this holds true by running your application workloads against the Beta release and contributi [...] -With over 1,000 bug fixes, improvements and new features and the project’s wholehearted https://cassandra.apache.org/blog/2018/08/21/testing_apache_cassandra.html;>focus on quality with https://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html;>replay, fuzz, property-based, fault-injection, and performance tests on clusters as large as 1,000 nodes and with hundreds of real world use cases and schemas tested, Cassandra 4.0 rede [...] +With over 1,000 bug fixes, improvements and new features and the project’s wholehearted https://cassandra.apache.org/blog/2018/08/21/testing_apache_cassandra.html;>focus on quality with https://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html;>replay, fuzz, property-based, fault-injection, and performance tests on clusters as large as 1,000 nodes and with hundreds of real world use cases and schemas tested, Cassandra 4.0 rede [...] There will be no new features or breaking API changes in future Beta or GA builds. You can expect the time you put into the beta to translate into transitioning your production workloads to 4.0 in the near future. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15191) stop_paranoid disk failure policy is ignored on CorruptSSTableException after node is up
[
https://issues.apache.org/jira/browse/CASSANDRA-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161586#comment-17161586
]
David Capwell commented on CASSANDRA-15191:
---
python dtests failed; it looks like exceptions were not logged before and all
are logged now. Simple example is with the auth tests found in
https://app.circleci.com/pipelines/github/dcapwell/cassandra/297/workflows/aefdb912-4395-498a-a1b6-b16770d46a45/jobs/1438
test_udf_permissions_validation - auth_test.TestAuthRoles
{code}
Unexpected error found in node logs (see stdout for full details). Errors:
[ERROR [Native-Transport-Requests-11] 2020-07-20 21:51:31,717
JVMStabilityInspector.java:81 - Uncaught exception in thread
Thread[Native-Transport-Requests-11,10,main]
org.apache.cassandra.exceptions.UnauthorizedException: User mike has no ALTER
permission on or any of its parents
at
org.apache.cassandra.service.ClientState.ensurePermissionOnResourceChain(ClientState.java:430)
at
org.apache.cassandra.service.ClientState.ensurePermission(ClientState.java:404)
at
org.apache.cassandra.cql3.statements.schema.CreateFunctionStatement.authorize(CreateFunctionStatement.java:177)
at
org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:203)
at
org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:253)
at
org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:240)
at
org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:108)
at
org.apache.cassandra.transport.Message$Request.execute(Message.java:253)
at
org.apache.cassandra.transport.Message$Dispatcher.processRequest(Message.java:725)
at
org.apache.cassandra.transport.Message$Dispatcher.lambda$channelRead0$0(Message.java:630)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
{code}
This exception wasn't logged before and was sent back to the user, with this
patch we now log all these hidden exceptions.
> stop_paranoid disk failure policy is ignored on CorruptSSTableException after
> node is up
>
>
> Key: CASSANDRA-15191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15191
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
>Reporter: Vincent White
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.11.x, 4.0-beta
>
> Attachments: log.txt
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> There is a bug when disk_failure_policy is set to stop_paranoid and
> CorruptSSTableException is thrown after server is up. The problem is that
> this setting is ignored. Normally, it should stop gossip and transport but it
> just continues to serve requests and an exception is just logged.
>
> This patch unifies the exception handling in JVMStabilityInspector and code
> is reworked in such way that this inspector acts as a central place where
> such exceptions are inspected.
>
> The core reason for ignoring that exception is that thrown exception in
> AbstractLocalAwareExecturorService is not CorruptSSTableException but it is
> RuntimeException and that exception is as its cause. Hence it is better if we
> handle this in JVMStabilityInspector which can recursively examine it, hence
> act accordingly.
> Behaviour before:
> stop_paranoid of disk_failure_policy is ignored when CorruptSSTableException
> is thrown, e.g. on a regular select statement
> Behaviour after:
> Gossip and transport (cql) is turned off, JVM is still up for further
> investigation e.g. by jmx.
--
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-14128) Prune dead links from cassandra.apache.org
[ https://issues.apache.org/jira/browse/CASSANDRA-14128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-14128: --- Resolution: Duplicate Status: Resolved (was: Open) > Prune dead links from cassandra.apache.org > -- > > Key: CASSANDRA-14128 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14128 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website, Legacy/Documentation and Website >Reporter: Jeff Jirsa >Assignee: Kurt Greaves >Priority: Low > Labels: lhf > Attachments: 14128-site.patch > > > Lots of dead links on the site, including the homepage. Should do some > pruning cleanup. > Site repo is [here|https://svn.apache.org/repos/asf/cassandra/site/] (in svn) > for anyone who wishes to give this a shot. -- 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-14128) Prune dead links from cassandra.apache.org
[ https://issues.apache.org/jira/browse/CASSANDRA-14128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161584#comment-17161584 ] Michael Semb Wever commented on CASSANDRA-14128: closing as done (in CASSANDRA-19540) > Prune dead links from cassandra.apache.org > -- > > Key: CASSANDRA-14128 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14128 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website, Legacy/Documentation and Website >Reporter: Jeff Jirsa >Assignee: Kurt Greaves >Priority: Low > Labels: lhf > Attachments: 14128-site.patch > > > Lots of dead links on the site, including the homepage. Should do some > pruning cleanup. > Site repo is [here|https://svn.apache.org/repos/asf/cassandra/site/] (in svn) > for anyone who wishes to give this a shot. -- 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-15940) Create better third-party page
[ https://issues.apache.org/jira/browse/CASSANDRA-15940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161582#comment-17161582 ] Michael Semb Wever edited comment on CASSANDRA-15940 at 7/20/20, 10:35 PM: --- Committed as [7d367b75032f49712ec5c9c3afa178c82e8e3fb2 |https://github.com/apache/cassandra-website/commit/7d367b75032f49712ec5c9c3afa178c82e8e3fb2]. (it still needs to be merged from staged to live) was (Author: michaelsembwever): Committed as [7d367b75032f49712ec5c9c3afa178c82e8e3fb2 |https://github.com/apache/cassandra-website/commit/7d367b75032f49712ec5c9c3afa178c82e8e3fb2]. > Create better third-party page > -- > > Key: CASSANDRA-15940 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15940 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta2 > > > Create a better third-party page based on dev mailing list conversation. > https://lists.apache.org/thread.html/r90076db617bf8615ae03567fa089bfe0ae31f1aa63ef8e2242bd9701%40%3Cdev.cassandra.apache.org%3E -- 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-15940) Create better third-party page
[ https://issues.apache.org/jira/browse/CASSANDRA-15940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15940: --- Fix Version/s: (was: 4.0-beta) 4.0-beta2 Source Control Link: https://github.com/apache/cassandra-website/commit/7d367b75032f49712ec5c9c3afa178c82e8e3fb2 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as [7d367b75032f49712ec5c9c3afa178c82e8e3fb2 |https://github.com/apache/cassandra-website/commit/7d367b75032f49712ec5c9c3afa178c82e8e3fb2]. > Create better third-party page > -- > > Key: CASSANDRA-15940 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15940 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta2 > > > Create a better third-party page based on dev mailing list conversation. > https://lists.apache.org/thread.html/r90076db617bf8615ae03567fa089bfe0ae31f1aa63ef8e2242bd9701%40%3Cdev.cassandra.apache.org%3E -- 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-website] branch master updated: make changes to index.html to update companies, add third-party page
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-website.git The following commit(s) were added to refs/heads/master by this push: new 7d367b7 make changes to index.html to update companies, add third-party page 7d367b7 is described below commit 7d367b75032f49712ec5c9c3afa178c82e8e3fb2 Author: polandll AuthorDate: Mon Jul 20 14:43:12 2020 -0700 make changes to index.html to update companies, add third-party page patch by Lorina Poland; reviewed by Mick Semb Wever for CASSANDRA-15940 --- src/community.md | 12 + src/index.html | 22 +++ src/third-party.md | 79 ++ 3 files changed, 97 insertions(+), 16 deletions(-) diff --git a/src/community.md b/src/community.md index 401270f..10f5cf7 100644 --- a/src/community.md +++ b/src/community.md @@ -46,20 +46,22 @@ You can also check the [Q about using Cassandra](http://stackoverflow.com/ques Overflow. -### Books and Publications +### Books and publications * [Cassandra: The Definitive Guide, 3rd Edition](http://shop.oreilly.com/product/0636920299837.do), by Jeff Carpenter and Eben Hewitt. Updated for Cassandra 4.0 * [Mastering Apache Cassandra, 2nd Edition](https://www.amazon.com/Mastering-Apache-Cassandra-Nishant-Neeraj/dp/1784392618/), by Nishant Neeraj * [Learning Apache Cassandra - Manage Fault Tolerant and Scalable Real-Time Data](https://www.amazon.com/Learning-Apache-Cassandra-Tolerant-Real-Time/dp/1783989203/), by Mat Brown * [Cassandra: a decentralized structured storage system](https://dl.acm.org/citation.cfm?id=1773922), by Avinash Lakshman and Prashant Malik +### Third-party projects + +There are a number of third-party Cassandra projects that could be useful. Check out this [listing](https://cassandra.apache.org/third-party/). ### Reporting bugs If you encounter a problem with Cassandra, the first places to ask for help are the [user mailing list](#mailing) -and the `#cassandra` [IRC channel](#irc). +and the `#cassandra` [Slack channel](https://s.apache.org/slack-invite). If, after having asked for help, you suspect that you have found a bug in Cassandra, you should report it by opening a -ticket through the [Apache Cassandra JIRA](https://issues.apache.org/jira/browse/CASSANDRA). Please provide as much -details as you can on your problem, and don't forget to indicate which version of Cassandra you are running and on which -environment. +ticket through the [Apache Cassandra JIRA tracking system](https://issues.apache.org/jira/browse/CASSANDRA). Please provide as much +detail as you can on your problem. Don't forget to indicate which version of Cassandra you are running and on which environment. diff --git a/src/index.html b/src/index.html index 0bc44ae..74e14f8 100644 --- a/src/index.html +++ b/src/index.html @@ -22,20 +22,20 @@ is_homepage: true Proven Cassandra is in use at +https://www.dataversity.net/case-study-cassandra-meets-call-of-duty/;>Activision, http://www.slideshare.net/daveconnors/cassandra-puppet-scaling-data-at-15-per-month;>Constant Contact, -http://planetcassandra.org/blog/post/cassandra-at-cern-large-hadron-collider/;>CERN, + http://www.slideshare.net/planetcassandra/nyc-tech-day-using-cassandra-for-dvr-scheduling-at-comcast;>Comcast, http://www.slideshare.net/jaykumarpatel/cassandra-at-ebay-13920376;>eBay, -http://planetcassandra.org/blog/post/analytics-at-github-with-apache-cassandra/;>GitHub, -http://planetcassandra.org/blog/post/godaddy-worlds-largest-domain-name-registrar-and-web-host-provider-utilizes-cassandra-for-replication-and-scalability/;>GoDaddy, -http://planetcassandra.org/blog/post/cassandra-used-to-build-scalable-and-highly-available-systems-at-hulu-streaming-content-to-over-5-million-subscribers/;>Hulu, -http://planetcassandra.org/blog/post/instagram-making-the-switch-to-cassandra-from-redis-75-instasavings/;>Instagram, -http://www.slideshare.net/planetcassandra/3-mohit-anchlia;>Intuit, -http://www.slideshare.net/adrianco/migrating-netflix-from-oracle-to-global-cassandra;>Netflix, -http://planetcassandra.org/blog/post/reddit-upvotes-apache-cassandras-horizontal-scaling-managing-1700-votes-daily/;>Reddit, -http://planetcassandra.org/blog/post/make-it-rain-apache-cassandra-at-the-weather-channel-for-severe-weather-alerts/;>The Weather Channel, -and http://planetcassandra.org/companies/;>over 1500 more companies that have large, active data -sets. + + + https://www.datastax.com/blog/2020/04/accelerate-rewind-how-instagram-uses-cassandra-operate-global-scale-2;>Instagram, + +
[jira] [Updated] (CASSANDRA-15940) Create better third-party page
[ https://issues.apache.org/jira/browse/CASSANDRA-15940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15940: --- Reviewers: Michael Semb Wever, Michael Semb Wever (was: Michael Semb Wever) Michael Semb Wever, Michael Semb Wever Status: Review In Progress (was: Patch Available) > Create better third-party page > -- > > Key: CASSANDRA-15940 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15940 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta > > > Create a better third-party page based on dev mailing list conversation. > https://lists.apache.org/thread.html/r90076db617bf8615ae03567fa089bfe0ae31f1aa63ef8e2242bd9701%40%3Cdev.cassandra.apache.org%3E -- 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-website] branch master updated: ninja-fix: download link in blog post
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-website.git The following commit(s) were added to refs/heads/master by this push: new c5b7637 ninja-fix: download link in blog post c5b7637 is described below commit c5b763764af1cbb13929d8e994a97fab055a51f4 Author: mck AuthorDate: Tue Jul 21 00:06:01 2020 +0200 ninja-fix: download link in blog post --- src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown b/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown index 744796e..0fab207 100644 --- a/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown +++ b/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown @@ -7,7 +7,7 @@ categories: blog --- -This is the most **stable** Apache Cassandra in history; you should start using Apache Cassandra 4.0 Beta today in your test and QA environments, head to the [downloads site](https://www.apache.org/dyn/closer.lua/cassandra/4.0-beta1/apache-cassandra-4.0-beta1-bin.tar.gz) to get your hands on it. The Cassandra community is on a mission to deliver a 4.0 GA release that is ready to be deployed to production. You can guarantee this holds true by running your application workloads against the [...] +This is the most **stable** Apache Cassandra in history; you should start using Apache Cassandra 4.0 Beta today in your test and QA environments, head to the [downloads site](https://cassandra.apache.org/download/) to get your hands on it. The Cassandra community is on a mission to deliver a 4.0 GA release that is ready to be deployed to production. You can guarantee this holds true by running your application workloads against the Beta release and contributing to the community's validat [...] With over 1,000 bug fixes, improvements and new features and the project's wholehearted [focus on quality](https://cassandra.apache.org/blog/2018/08/21/testing_apache_cassandra.html) with [replay, fuzz, property-based, fault-injection](https://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html), and performance tests on clusters as large as 1,000 nodes and with hundreds of real world use cases and schemas tested, Cassandra 4.0 redefines what users should e [...] - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15940) Create better third-party page
[ https://issues.apache.org/jira/browse/CASSANDRA-15940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15940: --- Status: Ready to Commit (was: Review In Progress) > Create better third-party page > -- > > Key: CASSANDRA-15940 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15940 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta > > > Create a better third-party page based on dev mailing list conversation. > https://lists.apache.org/thread.html/r90076db617bf8615ae03567fa089bfe0ae31f1aa63ef8e2242bd9701%40%3Cdev.cassandra.apache.org%3E -- 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-15940) Create better third-party page
[ https://issues.apache.org/jira/browse/CASSANDRA-15940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15940: --- Test and Documentation Plan: cassandra.staged.apache.org Status: Patch Available (was: Open) > Create better third-party page > -- > > Key: CASSANDRA-15940 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15940 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > Labels: pull-request-available > Fix For: 4.0-beta > > > Create a better third-party page based on dev mailing list conversation. > https://lists.apache.org/thread.html/r90076db617bf8615ae03567fa089bfe0ae31f1aa63ef8e2242bd9701%40%3Cdev.cassandra.apache.org%3E -- 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: ninja-fix: small fix in finish_release.sh (need debian svn co in place first)
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 9f1c936 ninja-fix: small fix in finish_release.sh (need debian svn co
in place first)
9f1c936 is described below
commit 9f1c9365324f5af4e3999ede654318ee30f1baae
Author: mck
AuthorDate: Tue Jul 21 00:26:54 2020 +0200
ninja-fix: small fix in finish_release.sh (need debian svn co in place
first)
---
cassandra-release/finish_release.sh | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/cassandra-release/finish_release.sh
b/cassandra-release/finish_release.sh
index 75edfe2..1f03492 100755
--- a/cassandra-release/finish_release.sh
+++ b/cassandra-release/finish_release.sh
@@ -102,7 +102,7 @@ exec 3>&1 4>&2
if [ $verbose -eq 0 ]
then
-# Not verbose, redirect all ouptut to a logfile
+# Not verbose, redirect all ouptut to a logfile
logfile="release-${release}.log"
[ ! -e "$logfile" ] || rm $logfile
touch $logfile
@@ -160,7 +160,8 @@ rm _tmp_msg_
echo "Deploying debian packages ..." 1>&3 2>&4
# Upload to bintray
-debian_dist_dir=$tmp_dir/cassandra-dist-$release
+debian_dist_dir=$tmp_dir/cassandra-dist-$release-debian
+execute "svn co
https://dist.apache.org/repos/dist/release/cassandra/$release/debian
$debian_dist_dir"
[ -e "$debian_dist_dir" ] || mkdir $debian_dist_dir # create it for fake mode,
to satisfy `find …` command below
execute "cd $debian_dist_dir"
@@ -251,7 +252,7 @@ echo "[3]: https://issues.apache.org/jira/browse/CASSANDRA;
>> $mail_file
echo 'Done deploying artifacts. Please make sure to:'
echo ' 1) release artifacts from repository.apache.org'
echo ' 2) wait for the artifacts to sync at
https://downloads.apache.org/cassandra/'
-echo ' 3) login to bintray and \"publish\" the uploaded artifacts'
+echo ' 3) login to bintray and \"publish\" the uploaded artifacts, at
https://bintray.com/apache/cassandra'
echo ' 4) update the website (TODO provide link)' # TODO - this is old info
and needs updating..
echo ' 5) update CQL doc if appropriate'
echo ' 6) update wikipedia page if appropriate'
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40593 - in /release/cassandra/debian/pool/main/c/cassandra: cassandra_4.0~alpha4.dsc cassandra_4.0~alpha4.tar.gz cassandra_4.0~alpha4_all.deb
Author: mck Date: Mon Jul 20 22:25:12 2020 New Revision: 40593 Log: apache cassandra 4.0-beta1 Removed: release/cassandra/debian/pool/main/c/cassandra/cassandra_4.0~alpha4.dsc release/cassandra/debian/pool/main/c/cassandra/cassandra_4.0~alpha4.tar.gz release/cassandra/debian/pool/main/c/cassandra/cassandra_4.0~alpha4_all.deb - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40592 - in /release/cassandra/debian/pool/main/c/cassandra: cassandra-tools_4.0~alpha3_all.deb cassandra-tools_4.0~alpha4_all.deb
Author: mck Date: Mon Jul 20 22:24:38 2020 New Revision: 40592 Log: apache cassandra 4.0-beta1 Removed: release/cassandra/debian/pool/main/c/cassandra/cassandra-tools_4.0~alpha3_all.deb release/cassandra/debian/pool/main/c/cassandra/cassandra-tools_4.0~alpha4_all.deb - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15964) Update Home index.html and remove all dead links
[ https://issues.apache.org/jira/browse/CASSANDRA-15964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorina Poland updated CASSANDRA-15964: -- Description: There are a number of tickets for home page improvement. Do all the work and republish. Linked to: CASSANDRA-14128 CASSANDRA-15237 In addition, Mick Semb Wever suggested the following be added to the list of companies using Cassandra: Can we find links for the following? * Apple * Uber, * ING, * Fidelity, * NY Times, * Outbrain, * BazaarVoice, * Best Buy, * Hulu, * Sky, * Pearson Education, * Walmart, * Microsoft, * Macy's™, * McDonalds, * Macquarie Bank, * GitHub, was:There are a number of tickets for home page improvement. Do all the work and republish. > Update Home index.html and remove all dead links > > > Key: CASSANDRA-15964 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15964 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Lorina Poland >Assignee: Lorina Poland >Priority: Normal > > There are a number of tickets for home page improvement. Do all the work and > republish. > Linked to: > CASSANDRA-14128 > CASSANDRA-15237 > In addition, Mick Semb Wever suggested the following be added to the list of > companies using Cassandra: > Can we find links for the following? > * Apple > * Uber, > * ING, > * Fidelity, > * NY Times, > * Outbrain, > * BazaarVoice, > * Best Buy, > * Hulu, > * Sky, > * Pearson Education, > * Walmart, > * Microsoft, > * Macy's™, > * McDonalds, > * Macquarie Bank, > * GitHub, -- 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
svn commit: r40591 - /release/cassandra/4.0-alpha4/
Author: mck Date: Mon Jul 20 22:16:19 2020 New Revision: 40591 Log: apache cassandra 4.0-beta1 Removed: release/cassandra/4.0-alpha4/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15191) stop_paranoid disk failure policy is ignored on CorruptSSTableException after node is up
[ https://issues.apache.org/jira/browse/CASSANDRA-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Semb Wever updated CASSANDRA-15191: --- Fix Version/s: (was: 4.0-beta1) (was: 3.11.7) 4.0-beta 3.11.x > stop_paranoid disk failure policy is ignored on CorruptSSTableException after > node is up > > > Key: CASSANDRA-15191 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15191 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Vincent White >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.x, 4.0-beta > > Attachments: log.txt > > Time Spent: 3h 20m > Remaining Estimate: 0h > > There is a bug when disk_failure_policy is set to stop_paranoid and > CorruptSSTableException is thrown after server is up. The problem is that > this setting is ignored. Normally, it should stop gossip and transport but it > just continues to serve requests and an exception is just logged. > > This patch unifies the exception handling in JVMStabilityInspector and code > is reworked in such way that this inspector acts as a central place where > such exceptions are inspected. > > The core reason for ignoring that exception is that thrown exception in > AbstractLocalAwareExecturorService is not CorruptSSTableException but it is > RuntimeException and that exception is as its cause. Hence it is better if we > handle this in JVMStabilityInspector which can recursively examine it, hence > act accordingly. > Behaviour before: > stop_paranoid of disk_failure_policy is ignored when CorruptSSTableException > is thrown, e.g. on a regular select statement > Behaviour after: > Gossip and transport (cql) is turned off, JVM is still up for further > investigation e.g. by jmx. -- 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-15964) Update Home index.html and remove all dead links
Lorina Poland created CASSANDRA-15964: - Summary: Update Home index.html and remove all dead links Key: CASSANDRA-15964 URL: https://issues.apache.org/jira/browse/CASSANDRA-15964 Project: Cassandra Issue Type: Improvement Components: Documentation/Website Reporter: Lorina Poland Assignee: Lorina Poland There are a number of tickets for home page improvement. Do all the work and republish. -- 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-website] branch asf-site updated: ninja-fix: download link in blog post
This is an automated email from the ASF dual-hosted git repository. mck pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/asf-site by this push: new 545f16e ninja-fix: download link in blog post 545f16e is described below commit 545f16e64fb0637bb3d7ca26522759b7d4801513 Author: mck AuthorDate: Tue Jul 21 00:04:01 2020 +0200 ninja-fix: download link in blog post --- content/blog/2020/07/20/apache-cassandra-4-0-beta1.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2020/07/20/apache-cassandra-4-0-beta1.html b/content/blog/2020/07/20/apache-cassandra-4-0-beta1.html index 4259db1..6972093 100644 --- a/content/blog/2020/07/20/apache-cassandra-4-0-beta1.html +++ b/content/blog/2020/07/20/apache-cassandra-4-0-beta1.html @@ -98,7 +98,7 @@ Posted on July 20, 2020 by The Apache Cassandra Community Back to the Apache Cassandra Blog - This is the most stable Apache Cassandra in history; you should start using Apache Cassandra 4.0 Beta today in your test and QA environments, head to the https://www.apache.org/dyn/closer.lua/cassandra/4.0-beta1/apache-cassandra-4.0-beta1-bin.tar.gz;>downloads site to get your hands on it. The Cassandra community is on a mission to deliver a 4.0 GA release that is ready to be deployed to production. You can guarantee this holds true by running your appl [...] + This is the most stable Apache Cassandra in history; you should start using Apache Cassandra 4.0 Beta today in your test and QA environments, head to the https://cassandra.apache.org/download/;>downloads site to get your hands on it. The Cassandra community is on a mission to deliver a 4.0 GA release that is ready to be deployed to production. You can guarantee this holds true by running your application workloads against the Beta release and contributi [...] With over 1,000 bug fixes, improvements and new features and the project’s wholehearted https://cassandra.apache.org/blog/2018/08/21/testing_apache_cassandra.html;>focus on quality with https://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html;>replay, fuzz, property-based, fault-injection, and performance tests on clusters as large as 1,000 nodes and with hundreds of real world use cases and schemas tested, Cassandra 4.0 rede [...] - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-site updated (76000d6 -> 3edfa83)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch asf-site in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. discard 76000d6 generate docs for 729e2903 add 2395cfd blog post on Apache Cassandra 4.0-beta1 ref: - https://lists.apache.org/thread.html/r4a5c9c471a64b93c8ea6b85d23f7592f8586b57071ac76ba75f07e78%40%3Cdev.cassandra.apache.org%3E - https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E - https://lists.apache.org/thread.html/r80c4fc2679dc76560feea42c49d771daf0434ce2a66d318f1532861a%40%3Cprivate.cassandra.apache.org%3E - https://github.com/apache [...] add 39d5bcc ninja-fix: small fixes on 4.0-beta1 blog post add 3edfa83 generate docs for 39d5bcc8 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (76000d6) \ N -- N -- N refs/heads/asf-site (3edfa83) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: .../2020/07/20/apache-cassandra-4-0-beta1.html | 211 + content/blog/index.html| 18 +- content/blog/page2/index.html | 9 + content/feed.xml | 60 +- .../apache-cassandra-infographic-final.jpg | Bin 0 -> 714941 bytes .../2020-07-20-apache-cassandra-4-0-beta1.markdown | 72 +++ .../apache-cassandra-infographic-final.jpg | Bin 0 -> 714941 bytes 7 files changed, 359 insertions(+), 11 deletions(-) create mode 100644 content/blog/2020/07/20/apache-cassandra-4-0-beta1.html create mode 100644 content/img/blog-post-apache-cassandra-4-0-beta1/apache-cassandra-infographic-final.jpg create mode 100644 src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown create mode 100644 src/img/blog-post-apache-cassandra-4-0-beta1/apache-cassandra-infographic-final.jpg - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (a8e8c0d -> 3edfa83)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git.
discard a8e8c0d generate docs for 2395cfde
add 39d5bcc ninja-fix: small fixes on 4.0-beta1 blog post
new 3edfa83 generate docs for 39d5bcc8
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (a8e8c0d)
\
N -- N -- N refs/heads/asf-staging (3edfa83)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../2020/07/{19 => 20}/apache-cassandra-4-0-beta1.html | 18 +++---
content/blog/index.html| 8
content/feed.xml | 10 +++---
.../2020-07-20-apache-cassandra-4-0-beta1.markdown | 7 +++
4 files changed, 17 insertions(+), 26 deletions(-)
rename content/blog/2020/07/{19 => 20}/apache-cassandra-4-0-beta1.html (91%)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch master updated: ninja-fix: small fixes on 4.0-beta1 blog post
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-website.git The following commit(s) were added to refs/heads/master by this push: new 39d5bcc ninja-fix: small fixes on 4.0-beta1 blog post 39d5bcc is described below commit 39d5bcc8c7462da785c03ffc5d3efb156d45330a Author: mck AuthorDate: Mon Jul 20 23:49:53 2020 +0200 ninja-fix: small fixes on 4.0-beta1 blog post --- src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown b/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown index bb95903..744796e 100644 --- a/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown +++ b/src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown @@ -1,12 +1,11 @@ --- layout: post -title: "Apache Cassandra 4.0 Beta: Battle Tested From Day One" -date: 2020-07-20 01:00:00 +0200 +title: "Introducing Apache Cassandra 4.0 Beta: Battle Tested From Day One" +date: 2020-07-20 23:00:00 +0200 author: The Apache Cassandra Community categories: blog --- -## **Introducing Apache Cassandra 4.0 Beta: Battle Tested From Day One** This is the most **stable** Apache Cassandra in history; you should start using Apache Cassandra 4.0 Beta today in your test and QA environments, head to the [downloads site](https://www.apache.org/dyn/closer.lua/cassandra/4.0-beta1/apache-cassandra-4.0-beta1-bin.tar.gz) to get your hands on it. The Cassandra community is on a mission to deliver a 4.0 GA release that is ready to be deployed to production. You can guarantee this holds true by running your application workloads against the [...] @@ -68,6 +67,6 @@ The Last Pickle Blog: [Virtual tables are coming in Cassandra 4.0](https://thela The Last Pickle Blog: [Java 11 Support in Apache Cassandra 4.0](https://thelastpickle.com/blog/2018/08/16/java11.html) -### +  - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (76000d6 -> a8e8c0d)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. omit 76000d6 generate docs for 729e2903 add 2395cfd blog post on Apache Cassandra 4.0-beta1 ref: - https://lists.apache.org/thread.html/r4a5c9c471a64b93c8ea6b85d23f7592f8586b57071ac76ba75f07e78%40%3Cdev.cassandra.apache.org%3E - https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E - https://lists.apache.org/thread.html/r80c4fc2679dc76560feea42c49d771daf0434ce2a66d318f1532861a%40%3Cprivate.cassandra.apache.org%3E - https://github.com/apache [...] new a8e8c0d generate docs for 2395cfde This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (76000d6) \ N -- N -- N refs/heads/asf-staging (a8e8c0d) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../2020/07/19/apache-cassandra-4-0-beta1.html | 215 + content/blog/index.html| 18 +- content/blog/page2/index.html | 9 + content/feed.xml | 64 +- .../apache-cassandra-infographic-final.jpg | Bin 0 -> 714941 bytes .../2020-07-20-apache-cassandra-4-0-beta1.markdown | 73 +++ .../apache-cassandra-infographic-final.jpg | Bin 0 -> 714941 bytes 7 files changed, 368 insertions(+), 11 deletions(-) create mode 100644 content/blog/2020/07/19/apache-cassandra-4-0-beta1.html create mode 100644 content/img/blog-post-apache-cassandra-4-0-beta1/apache-cassandra-infographic-final.jpg create mode 100644 src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown create mode 100644 src/img/blog-post-apache-cassandra-4-0-beta1/apache-cassandra-infographic-final.jpg - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15907) Operational Improvements & Hardening for Replica Filtering Protection
[
https://issues.apache.org/jira/browse/CASSANDRA-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161550#comment-17161550
]
Caleb Rackliffe edited comment on CASSANDRA-15907 at 7/20/20, 9:31 PM:
---
bq. As for tracking the cache size per replica o per query, I think it would be
nice if we used the same criteria that is used in the guardrail, so they
measure the same thing. That would mean either tracking the metric per query
and leaving the guardrail as it is, or changing the guardrail to be per-replica
instead of per-query.
Tracking the metric per query rather than changing the existing guardrail
sounds like the right move, although there isn't really a legitimate
multi-partition use-case yet, so most of the time a per-partition metric should
be equivalent to a per-query one. On the other hand, the whole point of the
metric is to help provide guidance for operators looking to set appropriate
warn/fail thresholds. I'll push something up today, along with slightly
modified inline docs, etc.
was (Author: maedhroz):
bq. As for tracking the cache size per replica o per query, I think it would be
nice if we used the same criteria that is used in the guardrail, so they
measure the same thing. That would mean either tracking the metric per query
and leaving the guardrail as it is, or changing the guardrail to be per-replica
instead of per-query.
Tracking the metric per query rather than changing the existing guardrail
sounds like the right move, although there isn't really a legitimate
multi-partition use-case yet, so most of the time a per-partition metric should
be equivalent to a per-query one. I'll push something up today, along with
slightly modified inline docs, etc.
> Operational Improvements & Hardening for Replica Filtering Protection
> -
>
> Key: CASSANDRA-15907
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15907
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination, Feature/2i Index
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Labels: 2i, memory
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> CASSANDRA-8272 uses additional space on the heap to ensure correctness for 2i
> and filtering queries at consistency levels above ONE/LOCAL_ONE. There are a
> few things we should follow up on, however, to make life a bit easier for
> operators and generally de-risk usage:
> (Note: Line numbers are based on {{trunk}} as of
> {{3cfe3c9f0dcf8ca8b25ad111800a21725bf152cb}}.)
> *Minor Optimizations*
> * {{ReplicaFilteringProtection:114}} - Given we size them up-front, we may be
> able to use simple arrays instead of lists for {{rowsToFetch}} and
> {{originalPartitions}}. Alternatively (or also), we may be able to null out
> references in these two collections more aggressively. (ex. Using
> {{ArrayList#set()}} instead of {{get()}} in {{queryProtectedPartitions()}},
> assuming we pass {{toFetch}} as an argument to {{querySourceOnKey()}}.)
> * {{ReplicaFilteringProtection:323}} - We may be able to use
> {{EncodingStats.merge()}} and remove the custom {{stats()}} method.
> * {{DataResolver:111 & 228}} - Cache an instance of
> {{UnaryOperator#identity()}} instead of creating one on the fly.
> * {{ReplicaFilteringProtection:217}} - We may be able to scatter/gather
> rather than serially querying every row that needs to be completed. This
> isn't a clear win perhaps, given it targets the latency of single queries and
> adds some complexity. (Certainly a decent candidate to kick even out of this
> issue.)
> *Documentation and Intelligibility*
> * There are a few places (CHANGES.txt, tracing output in
> {{ReplicaFilteringProtection}}, etc.) where we mention "replica-side
> filtering protection" (which makes it seem like the coordinator doesn't
> filter) rather than "replica filtering protection" (which sounds more like
> what we actually do, which is protect ourselves against incorrect replica
> filtering results). It's a minor fix, but would avoid confusion.
> * The method call chain in {{DataResolver}} might be a bit simpler if we put
> the {{repairedDataTracker}} in {{ResolveContext}}.
> *Testing*
> * I want to bite the bullet and get some basic tests for RFP (including any
> guardrails we might add here) onto the in-JVM dtest framework.
> *Guardrails*
> * As it stands, we don't have a way to enforce an upper bound on the memory
> usage of {{ReplicaFilteringProtection}} which caches row responses from the
> first round of requests. (Remember, these are later used to merged with the
> second round of results to complete the data for filtering.) Operators will
>
[jira] [Updated] (CASSANDRA-15907) Operational Improvements & Hardening for Replica Filtering Protection
[
https://issues.apache.org/jira/browse/CASSANDRA-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-15907:
Test and Documentation Plan:
The first line of defense against regression here is the set of dtests built
for CASSANDRA-8272 in {{replica_side_filtering}}. In addition to that, we'll
need at minimum a basic battery of in-JVM dtests around the new guardrails.
Once the implementation is reviewed, we'll use the \{{tlp-stress}} filtering
workload to stress things a bit, both to see how things behave with larger sets
of query results when filtering protection isn't activated, and to see how the
thresholds work when we have severely out-of-sync replicas.
In terms of documentation, we have two new {{cassandra.yaml}}
[options|https://github.com/apache/cassandra/pull/659/files?file-filters%5B%5D=.java%5B%5D=.xml%5B%5D=.yaml#diff-bdaab1104a93e723ce0b609a6477c9c4R664],
which have what should be reasonable documentation inline.
There is also a new metric in {{org.apache.cassandra.metrics}}:
{{type=Table}}
{{keyspace=}}
{{scope=}}
{{name=ReplicaFilteringProtectionRowsCachedPerQuery}}
This is a histogram of the number of rows cached per query that activates RFP.
was:
The first line of defense against regression here is the set of dtests built
for CASSANDRA-8272 in {{replica_side_filtering}}. In addition to that, we'll
need at minimum a basic battery of in-JVM dtests around the new guardrails.
Once the implementation is reviewed, we'll use the \{{tlp-stress}} filtering
workload to stress things a bit, both to see how things behave with larger sets
of query results when filtering protection isn't activated, and to see how the
thresholds work when we have severely out-of-sync replicas.
In terms of documentation, we have two new {{cassandra.yaml}}
[options|https://github.com/apache/cassandra/pull/659/files?file-filters%5B%5D=.java%5B%5D=.xml%5B%5D=.yaml#diff-bdaab1104a93e723ce0b609a6477c9c4R664],
which have what should be reasonable documentation inline.
There is also a new metric in {{org.apache.cassandra.metrics}}:
{{type=Table}}
{{keyspace=}}
{{scope=}}
{{name=ReplicaFilteringProtectionRowsCachedPerPartition}}
This is a histogram of the number of rows cached per partition during queries
that activate RFP.
> Operational Improvements & Hardening for Replica Filtering Protection
> -
>
> Key: CASSANDRA-15907
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15907
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination, Feature/2i Index
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Labels: 2i, memory
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> CASSANDRA-8272 uses additional space on the heap to ensure correctness for 2i
> and filtering queries at consistency levels above ONE/LOCAL_ONE. There are a
> few things we should follow up on, however, to make life a bit easier for
> operators and generally de-risk usage:
> (Note: Line numbers are based on {{trunk}} as of
> {{3cfe3c9f0dcf8ca8b25ad111800a21725bf152cb}}.)
> *Minor Optimizations*
> * {{ReplicaFilteringProtection:114}} - Given we size them up-front, we may be
> able to use simple arrays instead of lists for {{rowsToFetch}} and
> {{originalPartitions}}. Alternatively (or also), we may be able to null out
> references in these two collections more aggressively. (ex. Using
> {{ArrayList#set()}} instead of {{get()}} in {{queryProtectedPartitions()}},
> assuming we pass {{toFetch}} as an argument to {{querySourceOnKey()}}.)
> * {{ReplicaFilteringProtection:323}} - We may be able to use
> {{EncodingStats.merge()}} and remove the custom {{stats()}} method.
> * {{DataResolver:111 & 228}} - Cache an instance of
> {{UnaryOperator#identity()}} instead of creating one on the fly.
> * {{ReplicaFilteringProtection:217}} - We may be able to scatter/gather
> rather than serially querying every row that needs to be completed. This
> isn't a clear win perhaps, given it targets the latency of single queries and
> adds some complexity. (Certainly a decent candidate to kick even out of this
> issue.)
> *Documentation and Intelligibility*
> * There are a few places (CHANGES.txt, tracing output in
> {{ReplicaFilteringProtection}}, etc.) where we mention "replica-side
> filtering protection" (which makes it seem like the coordinator doesn't
> filter) rather than "replica filtering protection" (which sounds more like
> what we actually do, which is protect ourselves against incorrect replica
> filtering results). It's a minor fix, but would avoid confusion.
> * The method call chain in {{DataResolver}} might be a bit simpler if we
[jira] [Commented] (CASSANDRA-15907) Operational Improvements & Hardening for Replica Filtering Protection
[
https://issues.apache.org/jira/browse/CASSANDRA-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161550#comment-17161550
]
Caleb Rackliffe commented on CASSANDRA-15907:
-
bq. As for tracking the cache size per replica o per query, I think it would be
nice if we used the same criteria that is used in the guardrail, so they
measure the same thing. That would mean either tracking the metric per query
and leaving the guardrail as it is, or changing the guardrail to be per-replica
instead of per-query.
Tracking the metric per query rather than changing the existing guardrail
sounds like the right move, although there isn't really a legitimate
multi-partition use-case yet, so most of the time a per-partition metric should
be equivalent to a per-query one. I'll push something up today, along with
slightly modified inline docs, etc.
> Operational Improvements & Hardening for Replica Filtering Protection
> -
>
> Key: CASSANDRA-15907
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15907
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination, Feature/2i Index
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Labels: 2i, memory
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> CASSANDRA-8272 uses additional space on the heap to ensure correctness for 2i
> and filtering queries at consistency levels above ONE/LOCAL_ONE. There are a
> few things we should follow up on, however, to make life a bit easier for
> operators and generally de-risk usage:
> (Note: Line numbers are based on {{trunk}} as of
> {{3cfe3c9f0dcf8ca8b25ad111800a21725bf152cb}}.)
> *Minor Optimizations*
> * {{ReplicaFilteringProtection:114}} - Given we size them up-front, we may be
> able to use simple arrays instead of lists for {{rowsToFetch}} and
> {{originalPartitions}}. Alternatively (or also), we may be able to null out
> references in these two collections more aggressively. (ex. Using
> {{ArrayList#set()}} instead of {{get()}} in {{queryProtectedPartitions()}},
> assuming we pass {{toFetch}} as an argument to {{querySourceOnKey()}}.)
> * {{ReplicaFilteringProtection:323}} - We may be able to use
> {{EncodingStats.merge()}} and remove the custom {{stats()}} method.
> * {{DataResolver:111 & 228}} - Cache an instance of
> {{UnaryOperator#identity()}} instead of creating one on the fly.
> * {{ReplicaFilteringProtection:217}} - We may be able to scatter/gather
> rather than serially querying every row that needs to be completed. This
> isn't a clear win perhaps, given it targets the latency of single queries and
> adds some complexity. (Certainly a decent candidate to kick even out of this
> issue.)
> *Documentation and Intelligibility*
> * There are a few places (CHANGES.txt, tracing output in
> {{ReplicaFilteringProtection}}, etc.) where we mention "replica-side
> filtering protection" (which makes it seem like the coordinator doesn't
> filter) rather than "replica filtering protection" (which sounds more like
> what we actually do, which is protect ourselves against incorrect replica
> filtering results). It's a minor fix, but would avoid confusion.
> * The method call chain in {{DataResolver}} might be a bit simpler if we put
> the {{repairedDataTracker}} in {{ResolveContext}}.
> *Testing*
> * I want to bite the bullet and get some basic tests for RFP (including any
> guardrails we might add here) onto the in-JVM dtest framework.
> *Guardrails*
> * As it stands, we don't have a way to enforce an upper bound on the memory
> usage of {{ReplicaFilteringProtection}} which caches row responses from the
> first round of requests. (Remember, these are later used to merged with the
> second round of results to complete the data for filtering.) Operators will
> likely need a way to protect themselves, i.e. simply fail queries if they hit
> a particular threshold rather than GC nodes into oblivion. (Having control
> over limits and page sizes doesn't quite get us there, because stale results
> _expand_ the number of incomplete results we must cache.) The fun question is
> how we do this, with the primary axes being scope (per-query, global, etc.)
> and granularity (per-partition, per-row, per-cell, actual heap usage, etc.).
> My starting disposition on the right trade-off between
> performance/complexity and accuracy is having something along the lines of
> cached rows per query. Prior art suggests this probably makes sense alongside
> things like {{tombstone_failure_threshold}} in {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
[cassandra-website] branch master updated (729e290 -> 2395cfd)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. from 729e290 Upload download links/versions post 4.0-beta1 release add 2395cfd blog post on Apache Cassandra 4.0-beta1 ref: - https://lists.apache.org/thread.html/r4a5c9c471a64b93c8ea6b85d23f7592f8586b57071ac76ba75f07e78%40%3Cdev.cassandra.apache.org%3E - https://lists.apache.org/thread.html/r537fe799e7d5e6d72ac791fdbe9098ef0344c55400c7f68ff65abe51%40%3Cdev.cassandra.apache.org%3E - https://lists.apache.org/thread.html/r80c4fc2679dc76560feea42c49d771daf0434ce2a66d318f1532861a%40%3Cprivate.cassandra.apache.org%3E - https://github.com/apache [...] No new revisions were added by this update. Summary of changes: .../2020-07-20-apache-cassandra-4-0-beta1.markdown | 73 + .../apache-cassandra-infographic-final.jpg | Bin 0 -> 714941 bytes 2 files changed, 73 insertions(+) create mode 100644 src/_posts/2020-07-20-apache-cassandra-4-0-beta1.markdown create mode 100644 src/img/blog-post-apache-cassandra-4-0-beta1/apache-cassandra-infographic-final.jpg - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15963) Flaky dtest test_dead_sync_initiator - repair_tests.repair_test.TestRepair
Yifan Cai created CASSANDRA-15963: - Summary: Flaky dtest test_dead_sync_initiator - repair_tests.repair_test.TestRepair Key: CASSANDRA-15963 URL: https://issues.apache.org/jira/browse/CASSANDRA-15963 Project: Cassandra Issue Type: Bug Reporter: Yifan Cai CI test link. [https://app.circleci.com/pipelines/github/yifan-c/cassandra/78/workflows/e89b96f1-c468-484f-9764-694b64fad95b/jobs/411] test teardown failure Unexpected error found in node logs (see stdout for full details). Errors: [ERROR [Stream-Deserializer-127.0.0.1:7000-56da8052] 2020-07-20 19:00:33,545 CassandraEntireSSTableStreamReader.java:145 - [Stream 48a43e80-cabb-11ea-a743-3578c769ed44] Error while reading sstable from stream for table = keyspace1.standard1 org.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted: /tmp/dtest-4ichr2ha/test/node3/data0/keyspace1/standard1-3b1f65f0cabb11eaa7433578c769ed44/na-1-big-Statistics.db at org.apache.cassandra.io.sstable.metadata.MetadataSerializer.maybeValidateChecksum(MetadataSerializer.java:219) at org.apache.cassandra.io.sstable.metadata.MetadataSerializer.deserialize(MetadataSerializer.java:198) at org.apache.cassandra.io.sstable.metadata.MetadataSerializer.deserialize(MetadataSerializer.java:129) at org.apache.cassandra.io.sstable.metadata.MetadataSerializer.mutate(MetadataSerializer.java:226) at org.apache.cassandra.db.streaming.CassandraEntireSSTableStreamReader.read(CassandraEntireSSTableStreamReader.java:140) at org.apache.cassandra.db.streaming.CassandraIncomingFile.read(CassandraIncomingFile.java:84) at org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:53) at org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:38) at org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:51) at org.apache.cassandra.streaming.async.StreamingInboundHandler$StreamDeserializingTask.run(StreamingInboundHandler.java:172) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: Checksums do not match for /tmp/dtest-4ichr2ha/test/node3/data0/keyspace1/standard1-3b1f65f0cabb11eaa7433578c769ed44/na-1-big-Statistics.db ... 12 common frames omitted, ERROR [Stream-Deserializer-127.0.0.1:7000-56da8052] 2020-07-20 19:00:33,545 CassandraEntireSSTableStreamReader.java:145 - [Stream 48a43e80-cabb-11ea-a743-3578c769ed44] Error while reading sstable from stream for table = keyspace1.standard1 org.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted: /tmp/dtest-4ichr2ha/test/node3/data0/keyspace1/standard1-3b1f65f0cabb11eaa7433578c769ed44/na-1-big-Statistics.db at org.apache.cassandra.io.sstable.metadata.MetadataSerializer.maybeValidateChecksum(MetadataSerializer.java:219) at org.apache.cassandra.io.sstable.metadata.MetadataSerializer.deserialize(MetadataSerializer.java:198) at org.apache.cassandra.io.sstable.metadata.MetadataSerializer.deserialize(MetadataSerializer.java:129) at org.apache.cassandra.io.sstable.metadata.MetadataSerializer.mutate(MetadataSerializer.java:226) at org.apache.cassandra.db.streaming.CassandraEntireSSTableStreamReader.read(CassandraEntireSSTableStreamReader.java:140) at org.apache.cassandra.db.streaming.CassandraIncomingFile.read(CassandraIncomingFile.java:84) at org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:53) at org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:38) at org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:51) at org.apache.cassandra.streaming.async.StreamingInboundHandler$StreamDeserializingTask.run(StreamingInboundHandler.java:172) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.IOException: Checksums do not match for /tmp/dtest-4ichr2ha/test/node3/data0/keyspace1/standard1-3b1f65f0cabb11eaa7433578c769ed44/na-1-big-Statistics.db ... 12 common frames omitted] -- 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-15963) Flaky dtest test_dead_sync_initiator - repair_tests.repair_test.TestRepair
[
https://issues.apache.org/jira/browse/CASSANDRA-15963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-15963:
--
Description:
CI test link.
[https://app.circleci.com/pipelines/github/yifan-c/cassandra/78/workflows/e89b96f1-c468-484f-9764-694b64fad95b/jobs/411]
{code:java}
test teardown failure
Unexpected error found in node logs (see stdout for full details). Errors:
[ERROR [Stream-Deserializer-127.0.0.1:7000-56da8052] 2020-07-20 19:00:33,545
CassandraEntireSSTableStreamReader.java:145 - [Stream
48a43e80-cabb-11ea-a743-3578c769ed44] Error while reading sstable from stream
for table = keyspace1.standard1
org.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted:
/tmp/dtest-4ichr2ha/test/node3/data0/keyspace1/standard1-3b1f65f0cabb11eaa7433578c769ed44/na-1-big-Statistics.db
at
org.apache.cassandra.io.sstable.metadata.MetadataSerializer.maybeValidateChecksum(MetadataSerializer.java:219)
at
org.apache.cassandra.io.sstable.metadata.MetadataSerializer.deserialize(MetadataSerializer.java:198)
at
org.apache.cassandra.io.sstable.metadata.MetadataSerializer.deserialize(MetadataSerializer.java:129)
at
org.apache.cassandra.io.sstable.metadata.MetadataSerializer.mutate(MetadataSerializer.java:226)
at
org.apache.cassandra.db.streaming.CassandraEntireSSTableStreamReader.read(CassandraEntireSSTableStreamReader.java:140)
at
org.apache.cassandra.db.streaming.CassandraIncomingFile.read(CassandraIncomingFile.java:84)
at
org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:53)
at
org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:38)
at
org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:51)
at
org.apache.cassandra.streaming.async.StreamingInboundHandler$StreamDeserializingTask.run(StreamingInboundHandler.java:172)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Checksums do not match for
/tmp/dtest-4ichr2ha/test/node3/data0/keyspace1/standard1-3b1f65f0cabb11eaa7433578c769ed44/na-1-big-Statistics.db
... 12 common frames omitted, ERROR
[Stream-Deserializer-127.0.0.1:7000-56da8052] 2020-07-20 19:00:33,545
CassandraEntireSSTableStreamReader.java:145 - [Stream
48a43e80-cabb-11ea-a743-3578c769ed44] Error while reading sstable from stream
for table = keyspace1.standard1
org.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted:
/tmp/dtest-4ichr2ha/test/node3/data0/keyspace1/standard1-3b1f65f0cabb11eaa7433578c769ed44/na-1-big-Statistics.db
at
org.apache.cassandra.io.sstable.metadata.MetadataSerializer.maybeValidateChecksum(MetadataSerializer.java:219)
at
org.apache.cassandra.io.sstable.metadata.MetadataSerializer.deserialize(MetadataSerializer.java:198)
at
org.apache.cassandra.io.sstable.metadata.MetadataSerializer.deserialize(MetadataSerializer.java:129)
at
org.apache.cassandra.io.sstable.metadata.MetadataSerializer.mutate(MetadataSerializer.java:226)
at
org.apache.cassandra.db.streaming.CassandraEntireSSTableStreamReader.read(CassandraEntireSSTableStreamReader.java:140)
at
org.apache.cassandra.db.streaming.CassandraIncomingFile.read(CassandraIncomingFile.java:84)
at
org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:53)
at
org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:38)
at
org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:51)
at
org.apache.cassandra.streaming.async.StreamingInboundHandler$StreamDeserializingTask.run(StreamingInboundHandler.java:172)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Checksums do not match for
/tmp/dtest-4ichr2ha/test/node3/data0/keyspace1/standard1-3b1f65f0cabb11eaa7433578c769ed44/na-1-big-Statistics.db
... 12 common frames omitted]{code}
was:
CI test link.
[https://app.circleci.com/pipelines/github/yifan-c/cassandra/78/workflows/e89b96f1-c468-484f-9764-694b64fad95b/jobs/411]
test teardown failure
Unexpected error found in node logs (see stdout for full details). Errors:
[ERROR [Stream-Deserializer-127.0.0.1:7000-56da8052] 2020-07-20 19:00:33,545
CassandraEntireSSTableStreamReader.java:145 - [Stream
48a43e80-cabb-11ea-a743-3578c769ed44] Error while reading sstable from stream
for table = keyspace1.standard1
org.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted:
/tmp/dtest-4ichr2ha/test/node3/data0/keyspace1/standard1-3b1f65f0cabb11eaa7433578c769ed44/na-1-big-Statistics.db
at
org.apache.cassandra.io.sstable.metadata.MetadataSerializer.maybeValidateChecksum(MetadataSerializer.java:219)
at
[cassandra-website] branch asf-site updated (cf25a53 -> 76000d6)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch asf-site in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. discard cf25a53 regenerated docs. add ecfec8f regenerated docs. add 9bc538d ninja-fix: undo https://github.com/apache/cassandra-website/commit/48a7cd3a4d3c68751f43a25bf42a8ffc813b9e56#diff-60713fb19f6c50a2473835df63ff17f9 (only the latest 3.11 docs are to get generated (as well as trunk)) add c909aba CASSANDRA-15732 - Updated details of new book 'Cassandra: The Definitive Guide' add 338bcc2 ninja-fix: Symlink for 3.11 should point to latest 3.11* (not earliest) the previous fix for this in 7ecaff4 wasn't sorting, so head or tail was meaningless add 398760d generate docs for 338bcc26 add eac9158 Make sure the home directory in the docker container has correct permissions add 06e2ad8 Update README.md for new simpler development cycle. Remove content/ folder as it is now served from asf-staging and asf-site branches. add 1ad5e74 Add a dummy file to keep the content directory in git, as it needs to exist to be mounted as a volume in the docker run. add 5f0c863 Fix broken link add 729e290 Upload download links/versions post 4.0-beta1 release add 76000d6 generate docs for 729e2903 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (cf25a53) \ N -- N -- N refs/heads/asf-site (76000d6) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: .asf.yaml |2 +- Dockerfile | 17 +- README.md | 32 +- content/community/index.html |2 +- content/doc/3.11.7/objects.inv | Bin 8167 -> 8123 bytes content/doc/3.11.7/searchindex.js |2 +- content/doc/3.11.7/tools/nodetool/bootstrap.html |5 +- .../3.11.7/tools/nodetool/enablefullquerylog.html |7 +- content/doc/3.11.7/tools/nodetool/getreplicas.html | 261 --- .../doc/3.11.7/tools/nodetool/handoffwindow.html | 251 --- content/doc/3.11.7/tools/nodetool/nodetool.html|7 +- content/doc/3.11/objects.inv | Bin 8167 -> 8123 bytes content/doc/3.11/searchindex.js|2 +- content/doc/3.11/tools/nodetool/bootstrap.html |5 +- .../3.11/tools/nodetool/enablefullquerylog.html|7 +- content/doc/3.11/tools/nodetool/getreplicas.html | 261 --- content/doc/3.11/tools/nodetool/handoffwindow.html | 251 --- content/doc/3.11/tools/nodetool/nodetool.html |7 +- .../doc/4.0-beta1}/_images/Figure_1_backups.jpg| Bin .../doc/4.0-beta1}/_images/Figure_1_data_model.jpg | Bin .../doc/4.0-beta1}/_images/Figure_1_guarantees.jpg | Bin .../4.0-beta1}/_images/Figure_1_read_repair.jpg| Bin .../doc/4.0-beta1}/_images/Figure_2_data_model.jpg | Bin .../4.0-beta1}/_images/Figure_2_read_repair.jpg| Bin .../4.0-beta1}/_images/Figure_3_read_repair.jpg| Bin .../4.0-beta1}/_images/Figure_4_read_repair.jpg| Bin .../4.0-beta1}/_images/Figure_5_read_repair.jpg| Bin .../4.0-beta1}/_images/Figure_6_read_repair.jpg| Bin .../_images/data_modeling_chebotko_logical.png | Bin .../_images/data_modeling_chebotko_physical.png| Bin .../_images/data_modeling_hotel_bucketing.png | Bin .../4.0-beta1}/_images/data_modeling_hotel_erd.png | Bin .../_images/data_modeling_hotel_logical.png| Bin .../_images/data_modeling_hotel_physical.png | Bin .../_images/data_modeling_hotel_queries.png| Bin .../_images/data_modeling_hotel_relational.png | Bin .../_images/data_modeling_reservation_logical.png | Bin .../_images/data_modeling_reservation_physical.png | Bin .../doc/4.0-beta1}/_images/docs_commit.png | Bin .../doc/4.0-beta1}/_images/docs_create_branch.png | Bin .../doc/4.0-beta1}/_images/docs_create_file.png| Bin .../doc/4.0-beta1}/_images/docs_editor.png | Bin .../doc/4.0-beta1}/_images/docs_fork.png | Bin .../doc/4.0-beta1}/_images/docs_pr.png | Bin .../doc/4.0-beta1}/_images/docs_preview.png| Bin .../doc/4.0-beta1}/_images/eclipse_debug0.png | Bin .../doc/4.0-beta1}/_images/eclipse_debug1.png | Bin
[cassandra-website] branch asf-site updated (06ef521 -> cf25a53)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to branch asf-site in repository https://gitbox.apache.org/repos/asf/cassandra-website.git. discard 06ef521 generate docs for 1ad5e747 omit 1ad5e74 Add a dummy file to keep the content directory in git, as it needs to exist to be mounted as a volume in the docker run. omit 06e2ad8 Update README.md for new simpler development cycle. Remove content/ folder as it is now served from asf-staging and asf-site branches. omit eac9158 Make sure the home directory in the docker container has correct permissions omit 398760d generate docs for 338bcc26 omit 338bcc2 ninja-fix: Symlink for 3.11 should point to latest 3.11* (not earliest) the previous fix for this in 7ecaff4 wasn't sorting, so head or tail was meaningless omit c909aba CASSANDRA-15732 - Updated details of new book 'Cassandra: The Definitive Guide' omit 9bc538d ninja-fix: undo https://github.com/apache/cassandra-website/commit/48a7cd3a4d3c68751f43a25bf42a8ffc813b9e56#diff-60713fb19f6c50a2473835df63ff17f9 (only the latest 3.11 docs are to get generated (as well as trunk)) omit ecfec8f regenerated docs. new cf25a53 regenerated docs. This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (06ef521) \ N -- N -- N refs/heads/asf-site (cf25a53) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .asf.yaml |2 +- Dockerfile | 17 +- README.md | 32 +- content/community/index.html |2 +- content/doc/3.11.7/objects.inv | Bin 8123 -> 8167 bytes content/doc/3.11.7/searchindex.js |2 +- content/doc/3.11.7/tools/nodetool/bootstrap.html |5 +- .../3.11.7/tools/nodetool/enablefullquerylog.html |7 +- .../tools/nodetool/getreplicas.html|4 +- .../tools/nodetool/handoffwindow.html |4 +- content/doc/3.11.7/tools/nodetool/nodetool.html|7 +- content/doc/3.11/objects.inv | Bin 8123 -> 8167 bytes content/doc/3.11/searchindex.js|2 +- content/doc/3.11/tools/nodetool/bootstrap.html |5 +- .../3.11/tools/nodetool/enablefullquerylog.html|7 +- .../tools/nodetool/getreplicas.html|4 +- .../tools/nodetool/handoffwindow.html |4 +- content/doc/3.11/tools/nodetool/nodetool.html |7 +- .../configuration/cass_cl_archive_file.html| 274 --- .../4.0-alpha5/configuration/cass_env_sh_file.html | 376 .../configuration/cass_jvm_options_file.html | 245 --- .../configuration/cass_logback_xml_file.html | 373 .../4.0-alpha5/configuration/cass_rackdc_file.html | 300 --- .../4.0-alpha5/configuration/cass_topo_file.html | 280 --- .../4.0-alpha5/configuration/cass_yaml_file.html | 2103 .../configuration/cassandra_config_file.html | 200 +- content/doc/4.0-alpha5/configuration/index.html| 20 +- content/doc/4.0-alpha5/development/ci.html |5 - .../4.0-alpha5/getting_started/configuring.html| 61 +- content/doc/4.0-alpha5/glossary.html | 247 --- content/doc/4.0-alpha5/new/auditlogging.html | 22 +- .../doc/4.0-alpha5/new/transientreplication.html |4 +- content/doc/4.0-alpha5/objects.inv | Bin 9641 -> 9472 bytes content/doc/4.0-alpha5/operating/index.html|4 +- content/doc/4.0-alpha5/searchindex.js |2 +- content/doc/4.0-alpha5/tools/cassandra_stress.html |2 - .../doc/4.0-alpha5/tools/nodetool/bootstrap.html |5 +- .../tools/nodetool/enablefullquerylog.html |7 +- .../tools/nodetool/getreplicas.html|4 +- .../tools/nodetool/handoffwindow.html |4 +- .../doc/4.0-alpha5/tools/nodetool/nodetool.html|7 +- .../latest/configuration/cass_cl_archive_file.html | 274 --- .../doc/latest/configuration/cass_env_sh_file.html | 376 .../configuration/cass_jvm_options_file.html | 245
[jira] [Commented] (CASSANDRA-15766) NoSpamLogger arguments building objects on hot paths
[
https://issues.apache.org/jira/browse/CASSANDRA-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161532#comment-17161532
]
Caleb Rackliffe commented on CASSANDRA-15766:
-
The J11 rerun is hitting CASSANDRA-15892 ({{test_resumable_rebuild}}),
CASSANDRA-13805 ({{test_simple_parallel_repair}}), and maybe even
CASSANDRA-15299. It's unlikely any of these is being caused by the patch. (The
issue w/ {{SimpleReadWriteTest}} looks JVM related.)
The J8 rerun looks clean, modulo the known issues already mentioned above.
> NoSpamLogger arguments building objects on hot paths
>
>
> Key: CASSANDRA-15766
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15766
> Project: Cassandra
> Issue Type: Bug
> Components: Observability/Logging
>Reporter: Jon Meredith
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0-beta
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> NoSpamLogger is used in hot logging paths to prevent logs being overrun. For
> that to be most effective the arguments to the logger need to be cheap to
> construct. During the internode messaging refactor CASSANDRA-15066,
> performance changes to BufferPool for CASSANDRA-14416
> were accidentally reverted in the merge up from 3.11.
> Reviewing other uses since, it looks like there are a few places where the
> arguments require some form of String building.
> org.apache.cassandra.net.InboundSink#accept
> org.apache.cassandra.net.InboundMessageHandler#processCorruptFrame
> org.apache.cassandra.net.InboundMessageHandler.LargeMessage#deserialize
> org.apache.cassandra.net.OutboundConnection#onOverloaded
> org.apache.cassandra.utils.memory.BufferPool.GlobalPool#allocateMoreChunks
> Formatting arguments should either be precomputed, or if expensive they
> should be computed after the decision on whether to noSpamLog has been made.
--
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-website] branch asf-staging updated (1e3eb93 -> 76000d6)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a change to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git.
discard 1e3eb93 generate docs for 5f0c863d
add 729e290 Upload download links/versions post 4.0-beta1 release
new 76000d6 generate docs for 729e2903
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (1e3eb93)
\
N -- N -- N refs/heads/asf-staging (76000d6)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../configuration/cassandra_config_file.html | 209 +++-
content/doc/4.0-alpha5/configuration/index.html| 20 +-
content/doc/4.0-alpha5/development/ci.html |5 -
.../4.0-alpha5/getting_started/configuring.html| 61 +-
content/doc/4.0-alpha5/new/auditlogging.html | 22 +-
.../doc/4.0-alpha5/new/transientreplication.html |4 +-
content/doc/4.0-alpha5/objects.inv | Bin 9641 -> 9472 bytes
content/doc/4.0-alpha5/operating/index.html|4 +-
content/doc/4.0-alpha5/searchindex.js |2 +-
content/doc/4.0-alpha5/tools/cassandra_stress.html |2 -
.../doc/4.0-alpha5/tools/nodetool/bootstrap.html |5 +-
.../tools/nodetool/enablefullquerylog.html |7 +-
.../tools/nodetool/getreplicas.html} | 14 +-
.../tools/nodetool/handoffwindow.html} | 12 +-
.../doc/4.0-alpha5/tools/nodetool/nodetool.html|7 +-
.../doc/4.0-beta1}/_images/Figure_1_backups.jpg| Bin
.../doc/4.0-beta1}/_images/Figure_1_data_model.jpg | Bin
.../doc/4.0-beta1}/_images/Figure_1_guarantees.jpg | Bin
.../4.0-beta1}/_images/Figure_1_read_repair.jpg| Bin
.../doc/4.0-beta1}/_images/Figure_2_data_model.jpg | Bin
.../4.0-beta1}/_images/Figure_2_read_repair.jpg| Bin
.../4.0-beta1}/_images/Figure_3_read_repair.jpg| Bin
.../4.0-beta1}/_images/Figure_4_read_repair.jpg| Bin
.../4.0-beta1}/_images/Figure_5_read_repair.jpg| Bin
.../4.0-beta1}/_images/Figure_6_read_repair.jpg| Bin
.../_images/data_modeling_chebotko_logical.png | Bin
.../_images/data_modeling_chebotko_physical.png| Bin
.../_images/data_modeling_hotel_bucketing.png | Bin
.../4.0-beta1}/_images/data_modeling_hotel_erd.png | Bin
.../_images/data_modeling_hotel_logical.png| Bin
.../_images/data_modeling_hotel_physical.png | Bin
.../_images/data_modeling_hotel_queries.png| Bin
.../_images/data_modeling_hotel_relational.png | Bin
.../_images/data_modeling_reservation_logical.png | Bin
.../_images/data_modeling_reservation_physical.png | Bin
.../doc/4.0-beta1}/_images/docs_commit.png | Bin
.../doc/4.0-beta1}/_images/docs_create_branch.png | Bin
.../doc/4.0-beta1}/_images/docs_create_file.png| Bin
.../doc/4.0-beta1}/_images/docs_editor.png | Bin
.../doc/4.0-beta1}/_images/docs_fork.png | Bin
.../doc/4.0-beta1}/_images/docs_pr.png | Bin
.../doc/4.0-beta1}/_images/docs_preview.png| Bin
.../doc/4.0-beta1}/_images/eclipse_debug0.png | Bin
.../doc/4.0-beta1}/_images/eclipse_debug1.png | Bin
.../doc/4.0-beta1}/_images/eclipse_debug2.png | Bin
.../doc/4.0-beta1}/_images/eclipse_debug3.png | Bin
.../doc/4.0-beta1}/_images/eclipse_debug4.png | Bin
.../doc/4.0-beta1}/_images/eclipse_debug5.png | Bin
.../doc/4.0-beta1}/_images/eclipse_debug6.png | Bin
.../4.0-beta1}/_images/example-stress-graph.png| Bin
.../doc/4.0-beta1}/_images/hints.svg |0
.../doc/4.0-beta1}/_images/ring.svg|0
.../doc/4.0-beta1}/_images/vnodes.svg |0
.../{latest => 4.0-beta1}/architecture/dynamo.html |4 +-
.../architecture/guarantees.html |4 +-
.../{latest => 4.0-beta1}/architecture/index.html |4 +-
.../architecture/overview.html |4 +-
.../architecture/storage_engine.html |4 +-
content/doc/{latest => 4.0-beta1}/bugs.html|4 +-
.../configuration/cass_cl_archive_file.html|4 +-
.../configuration/cass_env_sh_file.html|4 +-
[jira] [Commented] (CASSANDRA-15857) Frozen RawTuple is not annotated with frozen in the toString method
[
https://issues.apache.org/jira/browse/CASSANDRA-15857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161522#comment-17161522
]
Yifan Cai commented on CASSANDRA-15857:
---
Thanks for the review!
Here is the patch that backport to 3.11.
[https://github.com/apache/cassandra/pull/686]
Some noticeable difference than the patch to trunk.
# {{CQLSSTableWriterTest}} uses JUnit Rule, which does not exist in JUnit 4.6.
I added a separate commit to "Backport CASSANDRA-13360 Upgrade junit from 4.6
to 4.12 "
# {{testSchemaChange}} in {{AggregationTest}} and {{UFTest}} are adjusted
since in 3.11 branch we do not have CASSANDRA-14825, which removes {{frozen}}
from param
> Frozen RawTuple is not annotated with frozen in the toString method
> ---
>
> Key: CASSANDRA-15857
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15857
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/CQL
>Reporter: Yifan Cai
>Assignee: Yifan Cai
>Priority: Normal
> Fix For: 4.0, 3.11.x
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> All raw types (e.g. RawCollection, RawUT) that supports freezing wraps the
> type name with 'frozen<>' in the toString method, except RawTuple.
> Therefore, the RawTuple::toString output misses the frozen wrapper.
> Tuple is always frozen. However since CASSANDRA-15035, it throws when the
> inner tuple is not explicitly wrapped with frozen within a collection.
> The method, CQL3Type.Raw::toString, is referenced at multiple places in the
> source. For example, referenced in CreateTypeStatement.Raw and involved in
> CQLSSTableWriter. Another example is that it is called to produce the
> SchemaChange at several AlterSchemaStatement implementations.
> A test can prove that missing the frozen wrapper causes exception when
> building CQLSSTableWriter for user types defined like below. Note that the
> inner tuple is wrapped with frozen in the initial CQL statement.
> {code:java}
> CREATE TYPE ks.fooType ( f list>> )
> {code}
> {code:java}
> org.apache.cassandra.exceptions.InvalidRequestException: Non-frozen tuples
> are not allowed inside collections: list>
> at
> org.apache.cassandra.cql3.CQL3Type$Raw$RawCollection.throwNestedNonFrozenError(CQL3Type.java:710)
> at
> org.apache.cassandra.cql3.CQL3Type$Raw$RawCollection.prepare(CQL3Type.java:669)
> at
> org.apache.cassandra.cql3.CQL3Type$Raw$RawCollection.prepareInternal(CQL3Type.java:661)
> at
> org.apache.cassandra.schema.Types$RawBuilder$RawUDT.lambda$prepare$1(Types.java:341)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
> at
> org.apache.cassandra.schema.Types$RawBuilder$RawUDT.prepare(Types.java:342)
> at org.apache.cassandra.schema.Types$RawBuilder.build(Types.java:291)
> at
> org.apache.cassandra.io.sstable.CQLSSTableWriter$Builder.createTypes(CQLSSTableWriter.java:551)
> at
> org.apache.cassandra.io.sstable.CQLSSTableWriter$Builder.build(CQLSSTableWriter.java:527)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch master updated: Upload download links/versions post 4.0-beta1 release
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-website.git
The following commit(s) were added to refs/heads/master by this push:
new 729e290 Upload download links/versions post 4.0-beta1 release
729e290 is described below
commit 729e29030fff0894cd003535cd5696262a3a7d73
Author: mck
AuthorDate: Mon Jul 20 22:32:23 2020 +0200
Upload download links/versions post 4.0-beta1 release
---
src/_data/releases.yaml | 4
src/download.md | 10 +++---
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/src/_data/releases.yaml b/src/_data/releases.yaml
index 1b4212a..44f9aeb 100644
--- a/src/_data/releases.yaml
+++ b/src/_data/releases.yaml
@@ -1,4 +1,8 @@
latest:
+ name: "4.0-beta1"
+ date: 2020-07-20
+
+"3.11":
name: "3.11.6"
date: 2020-02-14
diff --git a/src/download.md b/src/download.md
index 6d2360b..384c79c 100644
--- a/src/download.md
+++ b/src/download.md
@@ -9,11 +9,15 @@ is_sphinx_doc: false
Downloading Cassandra
-
-### Latest version
+### Latest Beta Version
-Download the latest Apache Cassandra 3.11 release: {{ "latest" |
full_release_link }}.
+Download the latest Apache Cassandra 4.0 beta release: {{ "latest" |
full_release_link }}.
-### Older supported releases
+### Latest Stable Version
+
+Download the latest Apache Cassandra 3.11 release: {{ "3.11" |
full_release_link }}.
+
+### Older Supported Releases
The following older Cassandra releases are still supported:
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15945) Verify expected SSTable components are present at startup
[ https://issues.apache.org/jira/browse/CASSANDRA-15945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-15945: - Fix Version/s: (was: 4.0) 4.0-beta2 > Verify expected SSTable components are present at startup > - > > Key: CASSANDRA-15945 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15945 > Project: Cassandra > Issue Type: Bug > Components: Local/SSTable >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 4.0-beta2 > > Time Spent: 1h > Remaining Estimate: 0h > > When Cassandra batch opens all sstables at startup, it should check that all > components listed in the TOC.txt are available. Compression is optional, so > there may not be a Compression.db component for all sstables, but if there > should be and it's missing we continue to load the sstable. The sstable is > unreadable without the compression metadata though, but we won't know this > until it's touched by a query or compaction. > To reliably use TOC.txt for verification, it needs CASSANDRA-10709 -- 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-15945) Verify expected SSTable components are present at startup
[ https://issues.apache.org/jira/browse/CASSANDRA-15945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-15945: - Since Version: 2.0.0 Source Control Link: https://github.com/apache/cassandra/commit/f3198c45067f753444ffafbc83b6aa563cb392ac Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed, thanks! > Verify expected SSTable components are present at startup > - > > Key: CASSANDRA-15945 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15945 > Project: Cassandra > Issue Type: Bug > Components: Local/SSTable >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 4.0 > > Time Spent: 1h > Remaining Estimate: 0h > > When Cassandra batch opens all sstables at startup, it should check that all > components listed in the TOC.txt are available. Compression is optional, so > there may not be a Compression.db component for all sstables, but if there > should be and it's missing we continue to load the sstable. The sstable is > unreadable without the compression metadata though, but we won't know this > until it's touched by a query or compaction. > To reliably use TOC.txt for verification, it needs CASSANDRA-10709 -- 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-15945) Verify expected SSTable components are present at startup
[ https://issues.apache.org/jira/browse/CASSANDRA-15945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-15945: - Reviewers: Brandon Williams, David Capwell (was: David Capwell) > Verify expected SSTable components are present at startup > - > > Key: CASSANDRA-15945 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15945 > Project: Cassandra > Issue Type: Bug > Components: Local/SSTable >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 4.0 > > Time Spent: 1h > Remaining Estimate: 0h > > When Cassandra batch opens all sstables at startup, it should check that all > components listed in the TOC.txt are available. Compression is optional, so > there may not be a Compression.db component for all sstables, but if there > should be and it's missing we continue to load the sstable. The sstable is > unreadable without the compression metadata though, but we won't know this > until it's touched by a query or compaction. > To reliably use TOC.txt for verification, it needs CASSANDRA-10709 -- 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: Verify sstable components on startup
This is an automated email from the ASF dual-hosted git repository.
brandonwilliams 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 f3198c4 Verify sstable components on startup
f3198c4 is described below
commit f3198c45067f753444ffafbc83b6aa563cb392ac
Author: yifan-c
AuthorDate: Thu Jul 16 13:12:11 2020 -0700
Verify sstable components on startup
Patch by Yifan Cai, reviewed by David Capwell and brandonwilliams for
CASSANDRA-15945
---
CHANGES.txt| 2 +
.../org/apache/cassandra/io/sstable/SSTable.java | 12 +++-
.../cassandra/io/sstable/format/SSTableReader.java | 36 +++-
.../cassandra/io/sstable/SSTableReaderTest.java| 67 ++
4 files changed, 115 insertions(+), 2 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index 10079b3..afb3d09 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,3 +1,5 @@
+4.0-beta2
+ * Verify sstable components on startup (CASSANDRA-15945)
4.0-beta1
* Remove BackPressureStrategy (CASSANDRA-15375)
* Improve messaging on indexing frozen collections (CASSANDRA-15908)
diff --git a/src/java/org/apache/cassandra/io/sstable/SSTable.java
b/src/java/org/apache/cassandra/io/sstable/SSTable.java
index 348d7f5..353b624 100644
--- a/src/java/org/apache/cassandra/io/sstable/SSTable.java
+++ b/src/java/org/apache/cassandra/io/sstable/SSTable.java
@@ -306,13 +306,23 @@ public abstract class SSTable
*/
protected static Set readTOC(Descriptor descriptor) throws
IOException
{
+return readTOC(descriptor, true);
+}
+
+/**
+ * Reads the list of components from the TOC component.
+ * @param skipMissing, skip adding the component to the returned set if
the corresponding file is missing.
+ * @return set of components found in the TOC
+ */
+protected static Set readTOC(Descriptor descriptor, boolean
skipMissing) throws IOException
+{
File tocFile = new File(descriptor.filenameFor(Component.TOC));
List componentNames = Files.readLines(tocFile,
Charset.defaultCharset());
Set components =
Sets.newHashSetWithExpectedSize(componentNames.size());
for (String componentName : componentNames)
{
Component component = new
Component(Component.Type.fromRepresentation(componentName), componentName);
-if (!new File(descriptor.filenameFor(component)).exists())
+if (skipMissing && !new
File(descriptor.filenameFor(component)).exists())
logger.error("Missing component: {}",
descriptor.filenameFor(component));
else
components.add(component);
diff --git a/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java
b/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java
index 04c4826..c7e0201 100644
--- a/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java
+++ b/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java
@@ -58,12 +58,12 @@ import org.apache.cassandra.dht.Range;
import org.apache.cassandra.dht.Token;
import org.apache.cassandra.exceptions.UnknownColumnException;
import org.apache.cassandra.io.FSError;
+import org.apache.cassandra.io.FSReadError;
import org.apache.cassandra.io.compress.CompressionMetadata;
import org.apache.cassandra.io.sstable.*;
import org.apache.cassandra.io.sstable.metadata.*;
import org.apache.cassandra.io.util.*;
import org.apache.cassandra.metrics.RestorableMeter;
-import org.apache.cassandra.metrics.StorageMetrics;
import org.apache.cassandra.schema.CachingParams;
import org.apache.cassandra.schema.Schema;
import org.apache.cassandra.schema.SchemaConstants;
@@ -402,6 +402,7 @@ public abstract class SSTableReader extends SSTable
implements SelfRefCounted types = EnumSet.of(MetadataType.VALIDATION,
MetadataType.STATS, MetadataType.HEADER);
Map sstableMetadata;
@@ -501,6 +502,8 @@ public abstract class SSTableReader extends SSTable
implements SelfRefCounted types = EnumSet.of(MetadataType.VALIDATION,
MetadataType.STATS, MetadataType.HEADER);
Map sstableMetadata;
@@ -661,6 +664,37 @@ public abstract class SSTableReader extends SSTable
implements SelfRefCounted actualComponents)
+throws CorruptSSTableException, FSReadError
+{
+File tocFile = new File(descriptor.filenameFor(Component.TOC));
+if (tocFile.exists())
+{
+try
+{
+Set expectedComponents = readTOC(descriptor, false);
+if (expectedComponents.contains(Component.COMPRESSION_INFO) &&
!actualComponents.contains(Component.COMPRESSION_INFO))
+{
+String compressionInfoFileName =
descriptor.filenameFor(Component.COMPRESSION_INFO);
+throw new CorruptSSTableException(new
svn commit: r40587 - /release/cassandra/4.0-beta1/debian/pool/
Author: mck Date: Mon Jul 20 19:21:32 2020 New Revision: 40587 Log: Apache Cassandra 4.0-beta1 debian artifacts Removed: release/cassandra/4.0-beta1/debian/pool/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40586 - /release/cassandra/4.0-beta1/debian/dists/
Author: mck Date: Mon Jul 20 19:21:31 2020 New Revision: 40586 Log: Apache Cassandra 4.0-beta1 debian artifacts Removed: release/cassandra/4.0-beta1/debian/dists/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40588 - /release/cassandra/redhat/40x/
Author: mck Date: Mon Jul 20 19:21:34 2020 New Revision: 40588 Log: Apache Cassandra 4.0-beta1 redhat artifacts Removed: release/cassandra/redhat/40x/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40589 - in /release/cassandra: 4.0-beta1/redhat/ redhat/40x/
Author: mck Date: Mon Jul 20 19:21:35 2020 New Revision: 40589 Log: Apache Cassandra 4.0-beta1 redhat artifacts Added: release/cassandra/redhat/40x/ - copied from r40588, release/cassandra/4.0-beta1/redhat/ Removed: release/cassandra/4.0-beta1/redhat/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40579 - /dev/cassandra/4.0-beta1/ /release/cassandra/4.0-beta1/
Author: mck Date: Mon Jul 20 19:21:07 2020 New Revision: 40579 Log: Apache Cassandra 4.0-beta1 release Added: release/cassandra/4.0-beta1/ - copied from r40578, dev/cassandra/4.0-beta1/ Removed: dev/cassandra/4.0-beta1/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40585 - in /release/cassandra: 4.0-beta1/debian/dists/40x/ debian/dists/40x/
Author: mck Date: Mon Jul 20 19:21:29 2020 New Revision: 40585 Log: Apache Cassandra 4.0-beta1 debian artifacts Added: release/cassandra/debian/dists/40x/ - copied from r40584, release/cassandra/4.0-beta1/debian/dists/40x/ Removed: release/cassandra/4.0-beta1/debian/dists/40x/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40581 - in /release/cassandra: 4.0-beta1/debian/pool/main/c/cassandra/cassandra_4.0~beta1.dsc debian/pool/main/c/cassandra/cassandra_4.0~beta1.dsc
Author: mck Date: Mon Jul 20 19:21:16 2020 New Revision: 40581 Log: Apache Cassandra 4.0-beta1 debian artifact cassandra_4.0~beta1.dsc Added: release/cassandra/debian/pool/main/c/cassandra/cassandra_4.0~beta1.dsc - copied unchanged from r40580, release/cassandra/4.0-beta1/debian/pool/main/c/cassandra/cassandra_4.0~beta1.dsc Removed: release/cassandra/4.0-beta1/debian/pool/main/c/cassandra/cassandra_4.0~beta1.dsc - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40583 - in /release/cassandra: 4.0-beta1/debian/pool/main/c/cassandra/cassandra_4.0~beta1_all.deb debian/pool/main/c/cassandra/cassandra_4.0~beta1_all.deb
Author: mck Date: Mon Jul 20 19:21:24 2020 New Revision: 40583 Log: Apache Cassandra 4.0-beta1 debian artifact cassandra_4.0~beta1_all.deb Added: release/cassandra/debian/pool/main/c/cassandra/cassandra_4.0~beta1_all.deb - copied unchanged from r40582, release/cassandra/4.0-beta1/debian/pool/main/c/cassandra/cassandra_4.0~beta1_all.deb Removed: release/cassandra/4.0-beta1/debian/pool/main/c/cassandra/cassandra_4.0~beta1_all.deb - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40584 - /release/cassandra/debian/dists/40x/
Author: mck Date: Mon Jul 20 19:21:25 2020 New Revision: 40584 Log: Apache Cassandra 4.0-beta1 debian artifacts Removed: release/cassandra/debian/dists/40x/ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] tag 4.0-beta1-tentative deleted (was 972da6f)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to tag 4.0-beta1-tentative in repository https://gitbox.apache.org/repos/asf/cassandra.git. *** WARNING: tag 4.0-beta1-tentative was deleted! *** was 972da6f Prepare debian changelog for 4.0-beta1 The revisions that were on this tag are still contained in other references; therefore, this change does not discard any commits from the repository. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40580 - in /release/cassandra: 4.0-beta1/debian/pool/main/c/cassandra/cassandra-tools_4.0~beta1_all.deb debian/pool/main/c/cassandra/cassandra-tools_4.0~beta1_all.deb
Author: mck Date: Mon Jul 20 19:21:13 2020 New Revision: 40580 Log: Apache Cassandra 4.0-beta1 debian artifact cassandra-tools_4.0~beta1_all.deb Added: release/cassandra/debian/pool/main/c/cassandra/cassandra-tools_4.0~beta1_all.deb - copied unchanged from r40579, release/cassandra/4.0-beta1/debian/pool/main/c/cassandra/cassandra-tools_4.0~beta1_all.deb Removed: release/cassandra/4.0-beta1/debian/pool/main/c/cassandra/cassandra-tools_4.0~beta1_all.deb - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
svn commit: r40582 - in /release/cassandra: 4.0-beta1/debian/pool/main/c/cassandra/cassandra_4.0~beta1.tar.gz debian/pool/main/c/cassandra/cassandra_4.0~beta1.tar.gz
Author: mck Date: Mon Jul 20 19:21:20 2020 New Revision: 40582 Log: Apache Cassandra 4.0-beta1 debian artifact cassandra_4.0~beta1.tar.gz Added: release/cassandra/debian/pool/main/c/cassandra/cassandra_4.0~beta1.tar.gz - copied unchanged from r40581, release/cassandra/4.0-beta1/debian/pool/main/c/cassandra/cassandra_4.0~beta1.tar.gz Removed: release/cassandra/4.0-beta1/debian/pool/main/c/cassandra/cassandra_4.0~beta1.tar.gz - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] annotated tag cassandra-4.0-beta1 created (now 7fcc004)
This is an automated email from the ASF dual-hosted git repository. mck pushed a change to annotated tag cassandra-4.0-beta1 in repository https://gitbox.apache.org/repos/asf/cassandra.git. at 7fcc004 (tag) tagging 972da6fcffa87b3a1684362a2bab97db853372d8 (commit) replaces cassandra-4.0-alpha4 by Mick Semb Wever on Mon Jul 20 21:20:28 2020 +0200 - Log - Apache Cassandra 4.0-beta1 release --- No new revisions were added by this update. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15945) Verify expected SSTable components are present at startup
[ https://issues.apache.org/jira/browse/CASSANDRA-15945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15945: -- Status: Ready to Commit (was: Review In Progress) > Verify expected SSTable components are present at startup > - > > Key: CASSANDRA-15945 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15945 > Project: Cassandra > Issue Type: Bug > Components: Local/SSTable >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 4.0 > > Time Spent: 1h > Remaining Estimate: 0h > > When Cassandra batch opens all sstables at startup, it should check that all > components listed in the TOC.txt are available. Compression is optional, so > there may not be a Compression.db component for all sstables, but if there > should be and it's missing we continue to load the sstable. The sstable is > unreadable without the compression metadata though, but we won't know this > until it's touched by a query or compaction. > To reliably use TOC.txt for verification, it needs CASSANDRA-10709 -- 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-15945) Verify expected SSTable components are present at startup
[ https://issues.apache.org/jira/browse/CASSANDRA-15945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161461#comment-17161461 ] David Capwell commented on CASSANDRA-15945: --- LGTM. +1 > Verify expected SSTable components are present at startup > - > > Key: CASSANDRA-15945 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15945 > Project: Cassandra > Issue Type: Bug > Components: Local/SSTable >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Fix For: 4.0 > > Time Spent: 1h > Remaining Estimate: 0h > > When Cassandra batch opens all sstables at startup, it should check that all > components listed in the TOC.txt are available. Compression is optional, so > there may not be a Compression.db component for all sstables, but if there > should be and it's missing we continue to load the sstable. The sstable is > unreadable without the compression metadata though, but we won't know this > until it's touched by a query or compaction. > To reliably use TOC.txt for verification, it needs CASSANDRA-10709 -- 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-15191) stop_paranoid disk failure policy is ignored on CorruptSSTableException after node is up
[ https://issues.apache.org/jira/browse/CASSANDRA-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161457#comment-17161457 ] David Capwell commented on CASSANDRA-15191: --- Overall the patch LGTM (only reviewed trunk so far), my main comments were in the tests; hope the example given helps. [~stefan.miklosovic] do you have any CI runs for this patch? > stop_paranoid disk failure policy is ignored on CorruptSSTableException after > node is up > > > Key: CASSANDRA-15191 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15191 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Vincent White >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.7, 4.0-beta1 > > Attachments: log.txt > > Time Spent: 3h 10m > Remaining Estimate: 0h > > There is a bug when disk_failure_policy is set to stop_paranoid and > CorruptSSTableException is thrown after server is up. The problem is that > this setting is ignored. Normally, it should stop gossip and transport but it > just continues to serve requests and an exception is just logged. > > This patch unifies the exception handling in JVMStabilityInspector and code > is reworked in such way that this inspector acts as a central place where > such exceptions are inspected. > > The core reason for ignoring that exception is that thrown exception in > AbstractLocalAwareExecturorService is not CorruptSSTableException but it is > RuntimeException and that exception is as its cause. Hence it is better if we > handle this in JVMStabilityInspector which can recursively examine it, hence > act accordingly. > Behaviour before: > stop_paranoid of disk_failure_policy is ignored when CorruptSSTableException > is thrown, e.g. on a regular select statement > Behaviour after: > Gossip and transport (cql) is turned off, JVM is still up for further > investigation e.g. by jmx. -- 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-15191) stop_paranoid disk failure policy is ignored on CorruptSSTableException after node is up
[ https://issues.apache.org/jira/browse/CASSANDRA-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161451#comment-17161451 ] David Capwell commented on CASSANDRA-15191: --- Thanks for the changes. To help show what I was trying (and failing) to say in the PR, I posted different tests that hit the read stage and show this is a problem. > stop_paranoid disk failure policy is ignored on CorruptSSTableException after > node is up > > > Key: CASSANDRA-15191 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15191 > Project: Cassandra > Issue Type: Bug > Components: Local/Config >Reporter: Vincent White >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.7, 4.0-beta1 > > Attachments: log.txt > > Time Spent: 2h 40m > Remaining Estimate: 0h > > There is a bug when disk_failure_policy is set to stop_paranoid and > CorruptSSTableException is thrown after server is up. The problem is that > this setting is ignored. Normally, it should stop gossip and transport but it > just continues to serve requests and an exception is just logged. > > This patch unifies the exception handling in JVMStabilityInspector and code > is reworked in such way that this inspector acts as a central place where > such exceptions are inspected. > > The core reason for ignoring that exception is that thrown exception in > AbstractLocalAwareExecturorService is not CorruptSSTableException but it is > RuntimeException and that exception is as its cause. Hence it is better if we > handle this in JVMStabilityInspector which can recursively examine it, hence > act accordingly. > Behaviour before: > stop_paranoid of disk_failure_policy is ignored when CorruptSSTableException > is thrown, e.g. on a regular select statement > Behaviour after: > Gossip and transport (cql) is turned off, JVM is still up for further > investigation e.g. by jmx. -- 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-15766) NoSpamLogger arguments building objects on hot paths
[ https://issues.apache.org/jira/browse/CASSANDRA-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-15766: -- Reviewers: Aleksey Yeschenko, ZhaoYang (was: ZhaoYang) > NoSpamLogger arguments building objects on hot paths > > > Key: CASSANDRA-15766 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15766 > Project: Cassandra > Issue Type: Bug > Components: Observability/Logging >Reporter: Jon Meredith >Assignee: Caleb Rackliffe >Priority: Normal > Fix For: 4.0-beta > > Time Spent: 1h 40m > Remaining Estimate: 0h > > NoSpamLogger is used in hot logging paths to prevent logs being overrun. For > that to be most effective the arguments to the logger need to be cheap to > construct. During the internode messaging refactor CASSANDRA-15066, > performance changes to BufferPool for CASSANDRA-14416 > were accidentally reverted in the merge up from 3.11. > Reviewing other uses since, it looks like there are a few places where the > arguments require some form of String building. > org.apache.cassandra.net.InboundSink#accept > org.apache.cassandra.net.InboundMessageHandler#processCorruptFrame > org.apache.cassandra.net.InboundMessageHandler.LargeMessage#deserialize > org.apache.cassandra.net.OutboundConnection#onOverloaded > org.apache.cassandra.utils.memory.BufferPool.GlobalPool#allocateMoreChunks > Formatting arguments should either be precomputed, or if expensive they > should be computed after the decision on whether to noSpamLog has been made. -- 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-15921) 4.0 quality testing: Materialized View
[ https://issues.apache.org/jira/browse/CASSANDRA-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-15921: - Description: The main purpose of this ticket to get a better understanding about 4.0 MV status as a guideline for future improvements. I don't think it should block 4.0 release since it's already marked as experimental. Main areas to test: * Write perf: We expect to see [10% write throughput drop per MV added|https://www.datastax.com/blog/2016/05/materialized-view-performance-cassandra-3x]. ** Attached C40_MV.png is alpha-4, 5-node, rf3 MV write tests: with 1 mv, throughput dropped 50% * Read perf: identical to normal table * Bootstrap/Decommision: no write-path required since CASSANDRA-13065 * Repair: write path required * Chaos monkey: take down coordinator/base-replica/view-replica during read/write/token-movement and verify data consistency (may need a tool) * Hint Replay: able to throttle if table has MV - CASSANDRA-13810 * Schema race: create/drop - CASSANDRA-15845/CASSANDRA-15918 was: The main purpose of this ticket to get a better understanding about 4.0 MV status as a guideline for future improvements. I don't think it should block 4.0 release since it's already marked as experimental. Main areas to test: * Write perf: We expect to see [10% write throughput drop per MV added|https://www.datastax.com/blog/2016/05/materialized-view-performance-cassandra-3x]. ** Attached C40_MV.png is alpha-4, 5-node, rf3 MV write tests. * Read perf: identical to normal table * Bootstrap/Decommision: no write-path required since CASSANDRA-13065 * Repair: write path required * Chaos monkey: take down coordinator/base-replica/view-replica during read/write/token-movement and verify data consistency (may need a tool) * Hint Replay: able to throttle if table has MV - CASSANDRA-13810 * Schema race: create/drop - CASSANDRA-15845/CASSANDRA-15918 > 4.0 quality testing: Materialized View > -- > > Key: CASSANDRA-15921 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15921 > Project: Cassandra > Issue Type: Task > Components: Feature/Materialized Views >Reporter: ZhaoYang >Assignee: ZhaoYang >Priority: Normal > Fix For: 4.x > > Attachments: C40_MV.png > > > The main purpose of this ticket to get a better understanding about 4.0 MV > status as a guideline for future improvements. I don't think it should block > 4.0 release since it's already marked as experimental. > Main areas to test: > * Write perf: We expect to see [10% write throughput drop per MV > added|https://www.datastax.com/blog/2016/05/materialized-view-performance-cassandra-3x]. > ** Attached C40_MV.png is alpha-4, 5-node, rf3 MV write tests: with 1 mv, > throughput dropped 50% > * Read perf: identical to normal table > * Bootstrap/Decommision: no write-path required since CASSANDRA-13065 > * Repair: write path required > * Chaos monkey: take down coordinator/base-replica/view-replica during > read/write/token-movement and verify data consistency (may need a tool) > * Hint Replay: able to throttle if table has MV - CASSANDRA-13810 > * Schema race: create/drop - CASSANDRA-15845/CASSANDRA-15918 -- 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-15921) 4.0 quality testing: Materialized View
[ https://issues.apache.org/jira/browse/CASSANDRA-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-15921: - Description: The main purpose of this ticket to get a better understanding about 4.0 MV status as a guideline for future improvements. I don't think it should block 4.0 release since it's already marked as experimental. Main areas to test: * Write perf: We expect to see [10% write throughput drop per MV added|https://www.datastax.com/blog/2016/05/materialized-view-performance-cassandra-3x]. ** Attached C40_MV.png is alpha-4, 5-node, rf3 MV write tests. * Read perf: identical to normal table * Bootstrap/Decommision: no write-path required since CASSANDRA-13065 * Repair: write path required * Chaos monkey: take down coordinator/base-replica/view-replica during read/write/token-movement and verify data consistency (may need a tool) * Hint Replay: able to throttle if table has MV - CASSANDRA-13810 * Schema race: create/drop - CASSANDRA-15845/CASSANDRA-15918 was: The main purpose of this ticket to get a better understanding about 4.0 MV status as a guideline for future improvements. I don't think it should block 4.0 release since it's already marked as experimental. Main areas to test: * Write perf: We expect to see [10% write throughput drop per MV added|https://www.datastax.com/blog/2016/05/materialized-view-performance-cassandra-3x]. * Read perf: identical to normal table * Bootstrap/Decommision: no write-path required since CASSANDRA-13065 * Repair: write path required * Chaos monkey: take down coordinator/base-replica/view-replica during read/write/token-movement and verify data consistency (may need a tool) * Hint Replay: able to throttle if table has MV - CASSANDRA-13810 * Schema race: create/drop - CASSANDRA-15845/CASSANDRA-15918 > 4.0 quality testing: Materialized View > -- > > Key: CASSANDRA-15921 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15921 > Project: Cassandra > Issue Type: Task > Components: Feature/Materialized Views >Reporter: ZhaoYang >Assignee: ZhaoYang >Priority: Normal > Fix For: 4.x > > Attachments: C40_MV.png > > > The main purpose of this ticket to get a better understanding about 4.0 MV > status as a guideline for future improvements. I don't think it should block > 4.0 release since it's already marked as experimental. > Main areas to test: > * Write perf: We expect to see [10% write throughput drop per MV > added|https://www.datastax.com/blog/2016/05/materialized-view-performance-cassandra-3x]. > ** Attached C40_MV.png is alpha-4, 5-node, rf3 MV write tests. > * Read perf: identical to normal table > * Bootstrap/Decommision: no write-path required since CASSANDRA-13065 > * Repair: write path required > * Chaos monkey: take down coordinator/base-replica/view-replica during > read/write/token-movement and verify data consistency (may need a tool) > * Hint Replay: able to throttle if table has MV - CASSANDRA-13810 > * Schema race: create/drop - CASSANDRA-15845/CASSANDRA-15918 -- 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-15921) 4.0 quality testing: Materialized View
[ https://issues.apache.org/jira/browse/CASSANDRA-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoYang updated CASSANDRA-15921: - Attachment: C40_MV.png > 4.0 quality testing: Materialized View > -- > > Key: CASSANDRA-15921 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15921 > Project: Cassandra > Issue Type: Task > Components: Feature/Materialized Views >Reporter: ZhaoYang >Assignee: ZhaoYang >Priority: Normal > Fix For: 4.x > > Attachments: C40_MV.png > > > The main purpose of this ticket to get a better understanding about 4.0 MV > status as a guideline for future improvements. I don't think it should block > 4.0 release since it's already marked as experimental. > Main areas to test: > * Write perf: We expect to see [10% write throughput drop per MV > added|https://www.datastax.com/blog/2016/05/materialized-view-performance-cassandra-3x]. > * Read perf: identical to normal table > * Bootstrap/Decommision: no write-path required since CASSANDRA-13065 > * Repair: write path required > * Chaos monkey: take down coordinator/base-replica/view-replica during > read/write/token-movement and verify data consistency (may need a tool) > * Hint Replay: able to throttle if table has MV - CASSANDRA-13810 > * Schema race: create/drop - CASSANDRA-15845/CASSANDRA-15918 -- 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-15960) Error while configuring cassandra
[ https://issues.apache.org/jira/browse/CASSANDRA-15960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-15960: - Resolution: Invalid Status: Resolved (was: Triage Needed) I recommend taking this to the user mailing list or our slack instance for help, Jira is for tracking bugs and not a good support system. > Error while configuring cassandra > - > > Key: CASSANDRA-15960 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15960 > Project: Cassandra > Issue Type: Bug >Reporter: Sanddep gupta >Priority: Normal > > Hi All , > I am pretty new to cassandra.. > i am trying to configure it my laptop but when configuring i write below on > CMD > C:\Program Files\cassandra\bin>cassandra > i am getting error > > "WARNING! Powershell script execution unavailable. > Please use 'powershell Set-ExecutionPolicy Unrestricted' > on this user-account to run cassandra with fully featured > functionality on this platform. > Starting with legacy startup options > Starting Cassandra Server > The system cannot find the path specified." > > version:-apache-cassandra-3.11.6 > can anyone help me with this. > thank in advance > -- 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-15814) order by descending on frozen list not working
[
https://issues.apache.org/jira/browse/CASSANDRA-15814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161294#comment-17161294
]
Andres de la Peña commented on CASSANDRA-15814:
---
[~Bereng] I'm adding the requested additional tests to the PR for 2.2, and also
some additional tests for the related already existing tests that aren't
verifying every collection type. If they look good to you I'll merge them up to
the other PRs and run CI for them.
The CircleCI run for the updated 2.2 PR is
[here|https://app.circleci.com/pipelines/github/adelapena/cassandra/66/workflows/8314df8a-ebf4-4ba1-95ce-2e85aedb3851].
> order by descending on frozen list not working
> --
>
> Key: CASSANDRA-15814
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15814
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Felipe Perez
>Assignee: Andres de la Peña
>Priority: Normal
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> By creating a table like the following:
> {code:java}
> CREATE TABLE IF NOT EXISTS software (
> name ascii,
> version frozen>,
> data ascii,
> PRIMARY KEY(name,version)
> )
> {code}
> It works and version is ordered in an ascending order. But when trying to
> order in descending order:
> {code:java}
> CREATE TABLE IF NOT EXISTS software (
> name ascii,
> version frozen>,
> data ascii,
> PRIMARY KEY(name,version)
> ) WITH CLUSTERING ORDER BY (version DESC);
> {code}
> The table is created normally, but when trying to insert a row:
> {code:java}
> insert into software(name, version) values ('t1', [2,10,30,40,50]);
> {code}
> Cassandra throws an error:
> {code:java}
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Invalid
> list literal for version of type frozen>"
> {code}
> The goal here is that I would like to get the last version of a software.
>
--
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-15956) 15583 - Ensure tooling surface area coverage
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Summary: 15583 - Ensure tooling surface area coverage (was: 15583 - Tooling surface area coverage) > 15583 - Ensure tooling surface area coverage > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) Added/Enhanced|(/) Added/enhanced|(/)|(/)|Use UT if possible. > Otherwise dtests if you need a full multinode env| > |Cqlsh|(/) Added|(/) Added|(/)|(/)|Easy Cqlsh UT is now possible and an > example is included| > |Cassandra-stress|(/) Added and existing|(/) Added|(/)|(x)| > |debug-cql|(/)|(x)|(/)|(x)| > |fqltool|(/) Existing|(/) Existing|(/)|(/)| > |auditlogviewer|(/) Existing|(/) Existing|(/)|(/)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| -- 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-15956) 15583 - Tooling surface area coverage
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Summary: 15583 - Tooling surface area coverage (was: 15583 - Tooling width first test) > 15583 - Tooling surface area coverage > - > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) Added/Enhanced|(/) Added/enhanced|(/)|(/)|Use UT if possible. > Otherwise dtests if you need a full multinode env| > |Cqlsh|(/) Added|(/) Added|(/)|(/)|Easy Cqlsh UT is now possible and an > example is included| > |Cassandra-stress|(/) Added and existing|(/) Added|(/)|(x)| > |debug-cql|(/)|(x)|(/)|(x)| > |fqltool|(/) Existing|(/) Existing|(/)|(/)| > |auditlogviewer|(/) Existing|(/) Existing|(/)|(/)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| -- 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-15962) Digest for some queries is different depending whether the data are retrieved from sstable or memtable
Jacek Lewandowski created CASSANDRA-15962:
-
Summary: Digest for some queries is different depending whether
the data are retrieved from sstable or memtable
Key: CASSANDRA-15962
URL: https://issues.apache.org/jira/browse/CASSANDRA-15962
Project: Cassandra
Issue Type: Bug
Components: Consistency/Coordination
Reporter: Jacek Lewandowski
Assignee: Jacek Lewandowski
Attachments: DigestTest.java
Not sure into which category should I assign this ticket.
Basically when reading using certain column filters, the digest is different
depending whether we read from sstable and memtable. This happens on {{trunk}}
and {{cassandra-3.11}} branches. However it works properly on {{cassandra-3.0}}
branch.
I'm attaching a simple test for trunk to demonstrate what I mean.
Please verify my test and my conclusions
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) Added/Enhanced|(/) Added/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) Added|(/) Added|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) Added and existing|(/) Added|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |fqltool|(/) Existing|(/) Existing|(/)|(/)| |auditlogviewer|(/) Existing|(/) Existing|(/)|(/)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) Added/Enhanced|(/) Added/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) Added|(/) Added|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) Added and existing|(/) Added|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |fqltool|(/) Existing|(/) Existing|(/)|(/)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) Added/Enhanced|(/) Added/enhanced|(/)|(/)|Use UT if possible. > Otherwise dtests if you need a full multinode env| > |Cqlsh|(/) Added|(/) Added|(/)|(/)|Easy Cqlsh UT is now possible and an > example is included| > |Cassandra-stress|(/) Added and existing|(/) Added|(/)|(x)| > |debug-cql|(/)|(x)|(/)|(x)| > |fqltool|(/) Existing|(/) Existing|(/)|(/)| > |auditlogviewer|(/) Existing|(/) Existing|(/)|(/)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/)
[jira] [Updated] (CASSANDRA-15933) Forbid adding new fields to UDTs used in partition key columns
[ https://issues.apache.org/jira/browse/CASSANDRA-15933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-15933: -- Reviewers: Alex Petrov, Sam Tunnicliffe > Forbid adding new fields to UDTs used in partition key columns > -- > > Key: CASSANDRA-15933 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15933 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Schema >Reporter: Aleksey Yeschenko >Assignee: Aleksey Yeschenko >Priority: Normal > Fix For: 4.0, 3.0.x, 3.11.x > > -- 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-15933) Forbid adding new fields to UDTs used in partition key columns
[ https://issues.apache.org/jira/browse/CASSANDRA-15933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-15933: -- Test and Documentation Plan: Unit test included Status: Patch Available (was: In Progress) 3.0 branch: https://github.com/iamaleksey/cassandra/commits/15933-3.0 4.0 branch: https://github.com/iamaleksey/cassandra/commits/15933-4.0 3.0 CI: https://app.circleci.com/pipelines/github/iamaleksey/cassandra/5/workflows/a327ef34-8873-4b4d-bec2-0557d90e6353 4.0 CI: https://app.circleci.com/pipelines/github/iamaleksey/cassandra/4/workflows/212ebf06-0462-4b46-aece-f0855ea42ebf > Forbid adding new fields to UDTs used in partition key columns > -- > > Key: CASSANDRA-15933 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15933 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Schema >Reporter: Aleksey Yeschenko >Assignee: Aleksey Yeschenko >Priority: Normal > Fix For: 4.0, 3.0.x, 3.11.x > > -- 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-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) Added/Enhanced|(/) Added/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) Added|(/) Added|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) Added and existing|(/) Added|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |fqltool|(/) Existing|(/) Existing|(/)|(/)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) Added/Enhanced|(/) Added/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) Added|(/) Added|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) Added and existing|(/) New|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |fqltool|(/) Existing|(/) Existing|(/)|(/)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) Added/Enhanced|(/) Added/enhanced|(/)|(/)|Use UT if possible. > Otherwise dtests if you need a full multinode env| > |Cqlsh|(/) Added|(/) Added|(/)|(/)|Easy Cqlsh UT is now possible and an > example is included| > |Cassandra-stress|(/) Added and existing|(/) Added|(/)|(x)| > |debug-cql|(/)|(x)|(/)|(x)| > |fqltool|(/) Existing|(/) Existing|(/)|(/)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| >
[jira] [Updated] (CASSANDRA-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) Added/Enhanced|(/) Added/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) Added|(/) Added|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) Added and existing|(/) New|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |fqltool|(/) Existing|(/) Existing|(/)|(/)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New and existing|(/) New|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |fqltool|(/) Existing|(/) Existing|(/)|(/)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) Added/Enhanced|(/) Added/enhanced|(/)|(/)|Use UT if possible. > Otherwise dtests if you need a full multinode env| > |Cqlsh|(/) Added|(/) Added|(/)|(/)|Easy Cqlsh UT is now possible and an > example is included| > |Cassandra-stress|(/) Added and existing|(/) New|(/)|(x)| > |debug-cql|(/)|(x)|(/)|(x)| > |fqltool|(/) Existing|(/) Existing|(/)|(/)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| >
[jira] [Updated] (CASSANDRA-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New and existing|(/) New|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |fqltool|(/)Existing|(/) Existing|(/)|(/)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/) New|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. > Otherwise dtests if you need a full multinode env| > |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example > is included| > |Cassandra-stress|(/) New and existing|(/) New|(/)|(x)| > |debug-cql|(/)|(x)|(/)|(x)| > |fqltool|(/)Existing|(/) Existing|(/)|(/)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableupgrade|(/) enhanced|(/)
[jira] [Updated] (CASSANDRA-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New and existing|(/) New|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |fqltool|(/) Existing|(/) Existing|(/)|(/)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New and existing|(/) New|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |fqltool|(/)Existing|(/) Existing|(/)|(/)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. > Otherwise dtests if you need a full multinode env| > |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example > is included| > |Cassandra-stress|(/) New and existing|(/) New|(/)|(x)| > |debug-cql|(/)|(x)|(/)|(x)| > |fqltool|(/) Existing|(/) Existing|(/)|(/)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablesplit|(/) enhanced|(/)
[jira] [Updated] (CASSANDRA-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/) New|(/)|(x)| |debug-cql|(/)|(x)|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/) New|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. > Otherwise dtests if you need a full multinode env| > |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example > is included| > |Cassandra-stress|(/) New|(/) New|(/)|(x)| > |debug-cql|(/)|(x)|(/)|(x)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| -- This message was
[jira] [Commented] (CASSANDRA-15907) Operational Improvements & Hardening for Replica Filtering Protection
[
https://issues.apache.org/jira/browse/CASSANDRA-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161154#comment-17161154
]
Andres de la Peña commented on CASSANDRA-15907:
---
[~maedhroz] Having a metric for the cache size is really nice. However, I think
it would be more useful to track the max per-query cache size, rather than the
per-partition size. This is because a single advance in the first phase merge
iterator can still insert an indefinite amount of partitions in the cache. For
example, let's consider this scenario when all the rows from an outdated
replica are superseded by the updated replica:
{code:java}
self._prepare_cluster(
create_table="CREATE TABLE t (k int, c int, v text, PRIMARY KEY(k, c))",
create_index="CREATE INDEX ON t(v)",
both_nodes=["INSERT INTO t (k, c, v) VALUES (0, 0, 'old')",
"INSERT INTO t (k, c, v) VALUES (0, 1, 'old')",
"INSERT INTO t (k, c, v) VALUES (1, 0, 'old')",
"INSERT INTO t (k, c, v) VALUES (1, 1, 'old')",
"INSERT INTO t (k, c, v) VALUES (2, 0, 'old')",
"INSERT INTO t (k, c, v) VALUES (2, 1, 'old')",
"INSERT INTO t (k, c, v) VALUES (3, 0, 'old')",
"INSERT INTO t (k, c, v) VALUES (3, 1, 'old')"],
only_node1=["DELETE FROM t WHERE k = 0",
"DELETE FROM t WHERE k = 1",
"DELETE FROM t WHERE k = 2",
"DELETE FROM t WHERE k = 3"])
self._assert_none("SELECT c FROM t WHERE v = 'old' LIMIT 1")
{code}
In this test all the 4 partitions are cached with a single advance of the
merged iterator, so the cache contains 16 rows at its maximum. However, the
metric records 8 times a per-partition cache size of 2. I think it would be
more useful either having a single metric with that max cache size of 12, or
two records (one per replica) with a value of 6. This would make it easier to
detect cases as the exposed in the example.
Also, being a per-query metric, it would be easier to advice operators to start
worrying about the consistency among replicas when the RFP metric starts to get
higher than the fetch size, independently of whether the queries are
single-partition or not.
As for tracking the cache size per replica o per query, I think it would be
nice if we used the same criteria that is used in the guardrail, so they
measure the same thing. That would mean either tracking the metric per query
and leaving the guardrail as it is, or changing the guardrail to be per-replica
instead of per-query.
WDYT?
> Operational Improvements & Hardening for Replica Filtering Protection
> -
>
> Key: CASSANDRA-15907
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15907
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination, Feature/2i Index
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Labels: 2i, memory
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> CASSANDRA-8272 uses additional space on the heap to ensure correctness for 2i
> and filtering queries at consistency levels above ONE/LOCAL_ONE. There are a
> few things we should follow up on, however, to make life a bit easier for
> operators and generally de-risk usage:
> (Note: Line numbers are based on {{trunk}} as of
> {{3cfe3c9f0dcf8ca8b25ad111800a21725bf152cb}}.)
> *Minor Optimizations*
> * {{ReplicaFilteringProtection:114}} - Given we size them up-front, we may be
> able to use simple arrays instead of lists for {{rowsToFetch}} and
> {{originalPartitions}}. Alternatively (or also), we may be able to null out
> references in these two collections more aggressively. (ex. Using
> {{ArrayList#set()}} instead of {{get()}} in {{queryProtectedPartitions()}},
> assuming we pass {{toFetch}} as an argument to {{querySourceOnKey()}}.)
> * {{ReplicaFilteringProtection:323}} - We may be able to use
> {{EncodingStats.merge()}} and remove the custom {{stats()}} method.
> * {{DataResolver:111 & 228}} - Cache an instance of
> {{UnaryOperator#identity()}} instead of creating one on the fly.
> * {{ReplicaFilteringProtection:217}} - We may be able to scatter/gather
> rather than serially querying every row that needs to be completed. This
> isn't a clear win perhaps, given it targets the latency of single queries and
> adds some complexity. (Certainly a decent candidate to kick even out of this
> issue.)
> *Documentation and Intelligibility*
> * There are a few places (CHANGES.txt, tracing output in
> {{ReplicaFilteringProtection}}, etc.) where we mention "replica-side
> filtering protection" (which makes it seem like the coordinator doesn't
> filter) rather than
[jira] [Created] (CASSANDRA-15961) Reference CASSANDRA-12607
Kapil Shewate created CASSANDRA-15961: - Summary: Reference CASSANDRA-12607 Key: CASSANDRA-15961 URL: https://issues.apache.org/jira/browse/CASSANDRA-15961 Project: Cassandra Issue Type: Bug Reporter: Kapil Shewate Assignee: Mattias W In cassandra 3.11.0 , the issue of commit logs being corrupted is still observed. Will this be fixed in higher versions of Cassandra? 02 19:58:33,677 JVMStabilityInspector.java:82 - Exiting due to error while processing commit log during initialization.org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException: Mutation checksum failure at 191598541 in Next section at 191590263 in CommitLog-6-1592895482005.log at org.apache.cassandra.db.commitlog.CommitLogReader.readSection(CommitLogReader.java:344) [apache-cassandra-3.11.0.jar:3.11.0] at org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:201) [apache-cassandra-3.11.0.jar:3.11.0] at org.apache.cassandra.db.commitlog.CommitLogReader.readAllFiles(CommitLogReader.java:84) [apache-cassandra-3.11.0.jar:3.11.0] at org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:140) [apache-cassandra-3.11.0.jar:3.11.0] at org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:177) [apache-cassandra-3.11.0.jar:3.11.0] at org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:158) [apache-cassandra-3.11.0.jar:3.11.0] at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:325) [apache-cassandra-3.11.0.jar:3.11.0] at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600) [apache-cassandra-3.11.0.jar:3.11.0] at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689) [apache-cassandra-3.11.0.jar:3.11.0][WARN] [main] 2020-07-02 20:31:30,334 DatabaseDescriptor.java:540 - Only 2.339GiB free across all data volumes. Consider adding more capacity to your cluster or removing obsolete snapshots[WARN] [main] 2020-07-02 20:31:30,763 NativeLibrary.java:187 - Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out, especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or run Cassandra as root.[WARN] [main] 2020-07-02 20:31:30,764 StartupChecks.java:127 - jemalloc shared library could not be preloaded to speed up memory allocations[WARN] [main] 2020-07-02 20:31:30,764 StartupChecks.java:201 - Non-Oracle JVM detected. Some features, such as immediate unmap of compacted SSTables, may not work as intended[WARN] [main] 2020-07-02 20:31:30,786 SigarLibrary.java:174 - Cassandra server running in degraded mode. Is swap disabled? : false, Address space adequate? : true, nofile limit adequate? : false, nproc limit adequate? : true [WARN] [main] 2020-07-02 20:31:30,789 StartupChecks.java:265 - Maximum number of memory map areas per process (vm.max_map_count) 65530 is too low, recommended value: 1048575, you can change it with sysctl. -- 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-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/) New|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New/Enhanced|(/) New|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/) New|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) New/Enhanced|(/) New/enhanced|(/)|(/)|Use UT if possible. > Otherwise dtests if you need a full multinode env| > |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example > is included| > |Cassandra-stress|(/) New|(/) New|(/)|(x)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CASSANDRA-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New/Enhanced|(/) New|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/) New|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New|(/) New|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/) New|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) New/Enhanced|(/) New|(/)|(/)|Use UT if possible. Otherwise > dtests if you need a full multinode env| > |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example > is included| > |Cassandra-stress|(/) New|(/) New|(/)|(x)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CASSANDRA-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New|(/) New|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/) New|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New|(/) New|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/)|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) New|(/) New|(/)|(/)|Use UT if possible. Otherwise dtests if you > need a full multinode env| > |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example > is included| > |Cassandra-stress|(/) New|(/) New|(/)|(x)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| -- This message was sent by Atlassian Jira (v8.3.4#803005) - To
[jira] [Updated] (CASSANDRA-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New|(/) New|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/)|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/)|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/)|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/)|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/)|(/)|(/)|| |sstableloader|(/) enhanced|(/)|(/)|(/)|| |sstablemetadata|(/) enhanced|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/)|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/)|(/)|(/)|| |sstablesplit|(/) enhanced|(/)|(/)|(/)|| |sstableupgrade|(/) enhanced|(/)|(/)|(/)|| |sstableutil|(/) enhanced|(/)|(/)|(/)|| |sstableverify|(/) enhanced|(/)|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) New|(/) New|(/)|(/)|Use UT if possible. Otherwise dtests if you > need a full multinode env| > |Cqlsh|(/) New|(/) New|(/)|(/)|Easy Cqlsh UT is now possible and an example > is included| > |Cassandra-stress|(/) New|(/)|(/)|(x)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableloader|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstableofflinerelevel|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/) enhanced|(/)|(!)|Ran in dtests, no > dedicated test| > |sstablescrub|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstablesplit|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableupgrade|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableutil|(/) enhanced|(/) enhanced|(/)|(/)|| > |sstableverify|(/) enhanced|(/) enhanced|(/)|(/)|| -- 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-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/)|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/) enhanced|(/)|(/)|(/)|| |sstableexpiredblockers|(/) enhanced|(/)|(/)|(/)|| |sstablelevelreset|(/) enhanced|(/)|(/)|(/)|| |sstableloader|(/) enhanced|(/)|(/)|(/)|| |sstablemetadata|(/) enhanced|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/) enhanced|(/)|(/)|(/)|| |sstablerepairedset|(/) enhanced|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/) enhanced|(/)|(/)|(/)|| |sstablesplit|(/) enhanced|(/)|(/)|(/)|| |sstableupgrade|(/) enhanced|(/)|(/)|(/)|| |sstableutil|(/) enhanced|(/)|(/)|(/)|| |sstableverify|(/) enhanced|(/)|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has some UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) sample only|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/) Sample only|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/)|(/)|(/)|(/)|| |sstablesplit|(/)|(/)|(/)|(/)|| |sstableupgrade|(/)|(/)|(/)|(/)|| |sstableutil|(/)|(/)|(/)|(/)|| |sstableverify|(/)|(/)|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||UT Sample||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) New|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you > need a full multinode env| > |Cqlsh|(/) New|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is > included| > |Cassandra-stress|(/) New|(/)|(/)|(x)| > |*Sstable utilities*|| > |sstabledump|(/) enhanced|(/)|(/)|(/)|| > |sstableexpiredblockers|(/) enhanced|(/)|(/)|(/)|| > |sstablelevelreset|(/) enhanced|(/)|(/)|(/)|| > |sstableloader|(/) enhanced|(/)|(/)|(/)|| > |sstablemetadata|(/) enhanced|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstableofflinerelevel|(/) enhanced|(/)|(/)|(/)|| > |sstablerepairedset|(/) enhanced|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstablescrub|(/) enhanced|(/)|(/)|(/)|| > |sstablesplit|(/) enhanced|(/)|(/)|(/)|| > |sstableupgrade|(/) enhanced|(/)|(/)|(/)|| > |sstableutil|(/) enhanced|(/)|(/)|(/)|| > |sstableverify|(/) enhanced|(/)|(/)|(/)|| -- 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-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has some UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/) New|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/) New|(/) sample only|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |Cassandra-stress|(/) New|(/) Sample only|(/)|(x)| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/)|(/)|(/)|(/)|| |sstablesplit|(/)|(/)|(/)|(/)|| |sstableupgrade|(/)|(/)|(/)|(/)|| |sstableutil|(/)|(/)|(/)|(/)|| |sstableverify|(/)|(/)|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/)|(/)|(/)|(/)|| |sstablesplit|(/)|(/)|(/)|(/)|| |sstableupgrade|(/)|(/)|(/)|(/)|| |sstableutil|(/)|(/)|(/)|(/)|| |sstableverify|(/)|(/)|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||Has some UT||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/) New|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you > need a full multinode env| > |Cqlsh|(/) New|(/) sample only|(/)|(/)|Easy Cqlsh UT is now possible and an > example is included| > |Cassandra-stress|(/) New|(/) Sample only|(/)|(x)| > |*Sstable utilities*|| > |sstabledump|(/)|(/)|(/)|(/)|| > |sstableexpiredblockers|(/)|(/)|(/)|(/)|| > |sstablelevelreset|(/)|(/)|(/)|(/)|| > |sstableloader|(/)|(/)|(/)|(/)|| > |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstablescrub|(/)|(/)|(/)|(/)|| > |sstablesplit|(/)|(/)|(/)|(/)|| > |sstableupgrade|(/)|(/)|(/)|(/)|| > |sstableutil|(/)|(/)|(/)|(/)|| > |sstableverify|(/)|(/)|(/)|(/)|| -- 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-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/)|(/)|(/)|(/)|| |sstablesplit|(/)|(/)|(/)|(/)|| |sstableupgrade|(/)|(/)|(/)|(/)|| |sstableutil|(/)|(/)|(/)|(/)|| |sstableverify|(/)|(/)|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/)|(/)|(/)|(/)|| |sstablesplit|(/)|(/)|(/)|(/)|| |sstableupgrade|(/)|(/)|(/)|(/)|| |sstableutil|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| > |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a > full multinode env| > |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is > included| > |*Sstable utilities*|| > |sstabledump|(/)|(/)|(/)|(/)|| > |sstableexpiredblockers|(/)|(/)|(/)|(/)|| > |sstablelevelreset|(/)|(/)|(/)|(/)|| > |sstableloader|(/)|(/)|(/)|(/)|| > |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstablescrub|(/)|(/)|(/)|(/)|| > |sstablesplit|(/)|(/)|(/)|(/)|| > |sstableupgrade|(/)|(/)|(/)|(/)|| > |sstableutil|(/)|(/)|(/)|(/)|| > |sstableverify|(/)|(/)|(/)|(/)|| -- 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-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/)|(/)|(/)|(/)|| |sstablesplit|(/)|(/)|(/)|(/)|| |sstableupgrade|(/)|(/)|(/)|(/)|| |sstableutil|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/)|(/)|(/)|(/)|| |sstablesplit|(/)|(/)|(/)|(/)|| |sstableupgrade|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| > |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a > full multinode env| > |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is > included| > |*Sstable utilities*|| > |sstabledump|(/)|(/)|(/)|(/)|| > |sstableexpiredblockers|(/)|(/)|(/)|(/)|| > |sstablelevelreset|(/)|(/)|(/)|(/)|| > |sstableloader|(/)|(/)|(/)|(/)|| > |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstablescrub|(/)|(/)|(/)|(/)|| > |sstablesplit|(/)|(/)|(/)|(/)|| > |sstableupgrade|(/)|(/)|(/)|(/)|| > |sstableutil|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| -- 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-15956) 15583 - Tooling width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Summary: 15583 - Tooling width first test (was: 15583 - Toolinng width first test) > 15583 - Tooling width first test > > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| > |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a > full multinode env| > |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is > included| > |*Sstable utilities*|| > |sstabledump|(/)|(/)|(/)|(/)|| > |sstableexpiredblockers|(/)|(/)|(/)|(/)|| > |sstablelevelreset|(/)|(/)|(/)|(/)|| > |sstableloader|(/)|(/)|(/)|(/)|| > |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstablescrub|(/)|(/)|(/)|(/)|| > |sstablesplit|(/)|(/)|(/)|(/)|| > |sstableupgrade|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| -- 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-15956) 15583 - Toolinng width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| |sstablescrub|(/)|(/)|(/)|(/)|| |sstablesplit|(/)|(/)|(/)|(/)|| |sstableupgrade|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in some dtests indirectly, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test|| |sstablescrub|(/)|(/)|(/)|(/)|| |sstablesplit|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > 15583 - Toolinng width first test > - > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| > |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a > full multinode env| > |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is > included| > |*Sstable utilities*|| > |sstabledump|(/)|(/)|(/)|(/)|| > |sstableexpiredblockers|(/)|(/)|(/)|(/)|| > |sstablelevelreset|(/)|(/)|(/)|(/)|| > |sstableloader|(/)|(/)|(/)|(/)|| > |sstablemetadata|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test| > |sstablescrub|(/)|(/)|(/)|(/)|| > |sstablesplit|(/)|(/)|(/)|(/)|| > |sstableupgrade|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| -- 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-15956) 15583 - Toolinng width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in some dtests indirectly, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test|| |sstablescrub|(/)|(/)|(/)|(/)|| |sstablesplit|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in some dtests indirectly, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test|| |sstablescrub|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > 15583 - Toolinng width first test > - > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| > |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a > full multinode env| > |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is > included| > |*Sstable utilities*|| > |sstabledump|(/)|(/)|(/)|(/)|| > |sstableexpiredblockers|(/)|(/)|(/)|(/)|| > |sstablelevelreset|(/)|(/)|(/)|(/)|| > |sstableloader|(/)|(/)|(/)|(/)|| > |sstablemetadata|(/)|(/)|(/)|(!)|Ran in some dtests indirectly, no dedicated > test| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test|| > |sstablescrub|(/)|(/)|(/)|(/)|| > |sstablesplit|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| -- 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-15956) 15583 - Toolinng width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(!)|Ran in some dtests indirectly, no dedicated test| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test|| |sstablescrub|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(/)|sstablemetadata is ran in some dtests indirectly| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(x)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > 15583 - Toolinng width first test > - > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| > |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a > full multinode env| > |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is > included| > |*Sstable utilities*|| > |sstabledump|(/)|(/)|(/)|(/)|| > |sstableexpiredblockers|(/)|(/)|(/)|(/)|| > |sstablelevelreset|(/)|(/)|(/)|(/)|| > |sstableloader|(/)|(/)|(/)|(/)|| > |sstablemetadata|(/)|(/)|(/)|(!)|Ran in some dtests indirectly, no dedicated > test| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstablerepairedset|(/)|(/)|(/)|(!)|Ran in dtests, no dedicated test|| > |sstablescrub|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| -- 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-15956) 15583 - Toolinng width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(/)|sstablemetadata is ran in some dtests indirectly| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstablerepairedset|(/)|(/)|(/)|(x)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Cmd Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(/)|sstablemetadata is ran in some dtests indirectly| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > 15583 - Toolinng width first test > - > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| > |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a > full multinode env| > |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is > included| > |*Sstable utilities*|| > |sstabledump|(/)|(/)|(/)|(/)|| > |sstableexpiredblockers|(/)|(/)|(/)|(/)|| > |sstablelevelreset|(/)|(/)|(/)|(/)|| > |sstableloader|(/)|(/)|(/)|(/)|| > |sstablemetadata|(/)|(/)|(/)|(/)|sstablemetadata is ran in some dtests > indirectly| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstablerepairedset|(/)|(/)|(/)|(x)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| -- 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-15956) 15583 - Toolinng width first test
[ https://issues.apache.org/jira/browse/CASSANDRA-15956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Berenguer Blasi updated CASSANDRA-15956: Description: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Cmd Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| |*Sstable utilities*|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(/)|sstablemetadata is ran in some dtests indirectly| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| was: Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other tools and scenarios in a width first approach to make sure enough surface area is covered. This should suffice to confirm our framework should enable devs to test any tools when needed. Tools: https://cassandra.apache.org/doc/latest/tools/index.html ||Cmd Tool||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a full multinode env| |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is included| ||Sstable utilities||Easy UT possible||Has UT||Easy dtest possible||Has dtest||Comments|| |sstabledump|(/)|(/)|(/)|(/)|| |sstableexpiredblockers|(/)|(/)|(/)|(/)|| |sstablelevelreset|(/)|(/)|(/)|(/)|| |sstableloader|(/)|(/)|(/)|(/)|| |sstablemetadata|(/)|(/)|(/)|(/)|sstablemetadata is ran in some dtests indirectly| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > 15583 - Toolinng width first test > - > > Key: CASSANDRA-15956 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15956 > Project: Cassandra > Issue Type: Improvement > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-beta > > > Given CASSANDRA-15942 POC seems ok so far. Now we'll extend that to other > tools and scenarios in a width first approach to make sure enough surface > area is covered. This should suffice to confirm our framework should enable > devs to test any tools when needed. > Tools: https://cassandra.apache.org/doc/latest/tools/index.html > ||Cmd Tool||Easy UT possible||Has UT||Easy dtest possible||Has > dtest||Comments|| > |Nodetool|(/)|(/)|(/)|(/)|Use UT if possible. Otherwise dtests if you need a > full multinode env| > |Cqlsh|(/)|(/)|(/)|(/)|Easy Cqlsh UT is now possible and an example is > included| > |*Sstable utilities*|| > |sstabledump|(/)|(/)|(/)|(/)|| > |sstableexpiredblockers|(/)|(/)|(/)|(/)|| > |sstablelevelreset|(/)|(/)|(/)|(/)|| > |sstableloader|(/)|(/)|(/)|(/)|| > |sstablemetadata|(/)|(/)|(/)|(/)|sstablemetadata is ran in some dtests > indirectly| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| > |sstableofflinerelevel|(/)|(/)|(/)|(/)|| -- 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
