[jira] [Updated] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17356: -- Status: Review In Progress (was: Patch Available) > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez reassigned CASSANDRA-17356: - Assignee: Erick Ramirez > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17356: -- Fix Version/s: 4.0.x (was: NA) > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17356: -- Source Control Link: (was: https://github.com/apache/cassandra-website/pull/98/commits/1b06344161091e80f8c78d8ab009183cae751e3c) > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17360) WEBSITE - Change publish date for "Tightening Security Pt 2" blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17360: -- Status: Ready to Commit (was: Review In Progress) Ready to commit + publish. Cheers! > WEBSITE - Change publish date for "Tightening Security Pt 2" blog post > -- > > Key: CASSANDRA-17360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17360 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Diogenese Topper >Priority: Normal > Fix For: 4.0.x > > > Blog post didn't get published in time. CASSANDRA-17343 was only published > yesterday so the blog post publish date needs to be changed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17342) Performance problem for node restart with incremental range repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-17342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488626#comment-17488626 ] Marcus Eriksson commented on CASSANDRA-17342: - It would be the git author field, to show that it is your patch. Something like [this|https://www.git-tower.com/learn/git/faq/change-author-name-email] > Performance problem for node restart with incremental range repairs > --- > > Key: CASSANDRA-17342 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17342 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Repair >Reporter: Paul Chandler >Assignee: Paul Chandler >Priority: Normal > Fix For: 4.0.x > > Attachments: BulkRepairStateTest.java, > IncrementalRepairStartupTest.java, LocalSessions.java, RepairedState.java > > > There is a performance problem when restarting cassandra for clusters doing > incremental repairs with range repairs. > We have clusters with 16 vnodes per node, and are splitting each vnode into > 100 ranges, this causes a node to take over 30 minutes to process the data > stored in the system.repairs table before the node can restart. Even when we > reduce this to 10 ranges per vnode this still takes 2 minutes to process. The > cluster has 22 keyspaces and a rf of 3, this creates around 8100 records in > the system.repairs table. > > The problem seems to occur in the > org.apache.cassandra.repair.consistent.RepairState class where the add method > re processes the complete list, including sorting, every time a new Range is > added. This leads is an exponential growth in processing time, this is > demonstrated in the attached unit test. > > I have created a change, that collects the data read in from the > system.repairs table, in the > org.apache.cassandra.repair.consistent.LocalSessions class, before processing > it as a group at the end, this reduces the processing time to a couple of > seconds even for the 100 range version. > > This is my first attempt at changing the cassandra code, so I am in need of a > mentor to help me with the process, and validate what I have done. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17359) Harry: Update Model validations to return ModelResult instead of void
[ https://issues.apache.org/jira/browse/CASSANDRA-17359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abe Ratnofsky updated CASSANDRA-17359: -- Impacts: (was: None) > Harry: Update Model validations to return ModelResult instead of void > - > > Key: CASSANDRA-17359 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17359 > Project: Cassandra > Issue Type: Improvement > Components: Test/fuzz >Reporter: Abe Ratnofsky >Priority: Normal > > From this PR discussion: > [https://github.com/apache/cassandra/pull/1382#discussion_r791222990] > > Currently, Model validations return void, so they cannot be used in > assertions. There are situations where it would be useful to know what a > validation actually did, in terms of queries run, partitions validated, etc. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17358) Harry: refactor usage of primitive long to use specialized types
[ https://issues.apache.org/jira/browse/CASSANDRA-17358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-17358: Component/s: Test/fuzz > Harry: refactor usage of primitive long to use specialized types > > > Key: CASSANDRA-17358 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17358 > Project: Cassandra > Issue Type: Improvement > Components: Test/fuzz >Reporter: Abe Ratnofsky >Priority: Normal > > From this PR discussion: > [https://github.com/apache/cassandra/pull/1382#discussion_r801209270] > > Currently, Harry uses primitive long types extensively (logical timestamps, > operation IDs, partition descriptors, clustering descriptors, etc). These are > allocated on the stack so they are performant, but they are not type-safe. > There's nothing preventing an accident like trying to inflate a clustering > descriptor where a partition descriptor is expected. > > To get around this, we could migrate these types to be non-primitive, with a > negative impact on performance. When Value Objects arrive (with JEP 169), > there may be new possibilities with different trade-offs. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17359) Harry: Update Model validations to return ModelResult instead of void
[ https://issues.apache.org/jira/browse/CASSANDRA-17359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-17359: Component/s: Test/fuzz > Harry: Update Model validations to return ModelResult instead of void > - > > Key: CASSANDRA-17359 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17359 > Project: Cassandra > Issue Type: Improvement > Components: Test/fuzz >Reporter: Abe Ratnofsky >Priority: Normal > > From this PR discussion: > [https://github.com/apache/cassandra/pull/1382#discussion_r791222990] > > Currently, Model validations return void, so they cannot be used in > assertions. There are situations where it would be useful to know what a > validation actually did, in terms of queries run, partitions validated, etc. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17360) WEBSITE - Change publish date for "Tightening Security Pt 2" blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17360: -- Status: Review In Progress (was: Patch Available) > WEBSITE - Change publish date for "Tightening Security Pt 2" blog post > -- > > Key: CASSANDRA-17360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17360 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Diogenese Topper >Priority: Normal > Fix For: 4.0.x > > > Blog post didn't get published in time. CASSANDRA-17343 was only published > yesterday so the blog post publish date needs to be changed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17360) WEBSITE - Change publish date for "Tightening Security Pt 2" blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17360: -- Test and Documentation Plan: Blog published date changed to February 7 on both blog index + post. Status: Patch Available (was: Open) https://github.com/apache/cassandra-website/pull/97 > WEBSITE - Change publish date for "Tightening Security Pt 2" blog post > -- > > Key: CASSANDRA-17360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17360 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Diogenese Topper >Priority: Normal > Fix For: 4.0.x > > > Blog post didn't get published in time. CASSANDRA-17343 was only published > yesterday so the blog post publish date needs to be changed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17360) WEBSITE - Change publish date for "Tightening Security Pt 2" blog post
[ https://issues.apache.org/jira/browse/CASSANDRA-17360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17360: -- Change Category: Semantic Complexity: Normal Component/s: Documentation/Blog Fix Version/s: 4.0.x Reviewers: Erick Ramirez Status: Open (was: Triage Needed) > WEBSITE - Change publish date for "Tightening Security Pt 2" blog post > -- > > Key: CASSANDRA-17360 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17360 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Erick Ramirez >Assignee: Diogenese Topper >Priority: Normal > Fix For: 4.0.x > > > Blog post didn't get published in time. CASSANDRA-17343 was only published > yesterday so the blog post publish date needs to be changed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17360) WEBSITE - Change publish date for "Tightening Security Pt 2" blog post
Erick Ramirez created CASSANDRA-17360: - Summary: WEBSITE - Change publish date for "Tightening Security Pt 2" blog post Key: CASSANDRA-17360 URL: https://issues.apache.org/jira/browse/CASSANDRA-17360 Project: Cassandra Issue Type: Task Reporter: Erick Ramirez Assignee: Diogenese Topper Blog post didn't get published in time. CASSANDRA-17343 was only published yesterday so the blog post publish date needs to be changed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17359) Harry: Update Model validations to return ModelResult instead of void
Abe Ratnofsky created CASSANDRA-17359: - Summary: Harry: Update Model validations to return ModelResult instead of void Key: CASSANDRA-17359 URL: https://issues.apache.org/jira/browse/CASSANDRA-17359 Project: Cassandra Issue Type: Improvement Reporter: Abe Ratnofsky >From this PR discussion: >[https://github.com/apache/cassandra/pull/1382#discussion_r791222990] Currently, Model validations return void, so they cannot be used in assertions. There are situations where it would be useful to know what a validation actually did, in terms of queries run, partitions validated, etc. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17358) Harry: refactor usage of primitive long to use specialized types
Abe Ratnofsky created CASSANDRA-17358: - Summary: Harry: refactor usage of primitive long to use specialized types Key: CASSANDRA-17358 URL: https://issues.apache.org/jira/browse/CASSANDRA-17358 Project: Cassandra Issue Type: Improvement Reporter: Abe Ratnofsky >From this PR discussion: >[https://github.com/apache/cassandra/pull/1382#discussion_r801209270] Currently, Harry uses primitive long types extensively (logical timestamps, operation IDs, partition descriptors, clustering descriptors, etc). These are allocated on the stack so they are performant, but they are not type-safe. There's nothing preventing an accident like trying to inflate a clustering descriptor where a partition descriptor is expected. To get around this, we could migrate these types to be non-primitive, with a negative impact on performance. When Value Objects arrive (with JEP 169), there may be new possibilities with different trade-offs. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17351) Pip doesn't install ccm every time
[ https://issues.apache.org/jira/browse/CASSANDRA-17351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488519#comment-17488519 ] Ekaterina Dimitrova commented on CASSANDRA-17351: - I see Jenkins and Circle CI run absolutely the same command: _pip3 install --exists-action w --upgrade -r ~/cassandra-dtest/requirements.txt_ Then in my mind the only difference is versions. Seems to me Jenkins uses 21.2.4 for pip3 and 20.8.1 for virtualenv, but CircleCI uses different ones - 21.0.1 for pip and 20.4.2 for virtualenv. I see different venv used, [~mck], is this intentional? > Pip doesn't install ccm every time > -- > > Key: CASSANDRA-17351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17351 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Urgent > Fix For: 4.x > > > In CASSANDRA-16688 we fixed requirements.txt in DTest repo, pip install to > run without -e for ccm in order to address the moveable tag. That worked for > some time until last night. I successfully retagged and now ccm is not > re-installed in Circle CI. > Jenkins picked stuff though. But it was acting unreliably and weird so > rerunning now things there. Results pending. > Now I added -e for ccm in requirements.txt and it worked in CircleCI. Still > pending results. I don't think this will be permanent solution and I am not > sure whether it will affect also the previous branches in a way. We need to > further investigate it and test. > For now I will ask people to test with -e until we figure it out. > CC [~mck] , [~bereng] , [~dcapwell] and [~stefan.miklosovic] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15297) nodetool can not create snapshot with snapshot name that have special character
[
https://issues.apache.org/jira/browse/CASSANDRA-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488516#comment-17488516
]
Saranya Krishnakumar commented on CASSANDRA-15297:
--
Thanks for pointing, made the change to use
{code:java}
File.pathSeparator() {code}
> nodetool can not create snapshot with snapshot name that have special
> character
> ---
>
> Key: CASSANDRA-15297
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15297
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: maxwellguo
>Assignee: Saranya Krishnakumar
>Priority: Normal
> Labels: pull-request-available
> Fix For: 4.x
>
> Attachments: after-fix.jpg, image.png, listsnapshots-p-s.jpg,
> snapshot-listsnapshot-.jpg, snapshot-p-s.jpg
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> we make snapshot through "nodetool snapshot -t snapshotname " , when
> snapshotname contains special characters like "/", the make snapshot process
> successfully , but the result
> can be different ,when we check the data file directory or use "nodetool
> listsnapshots".
> here is some case :
> 1. nodetool snapshot -t "p/s"
> the listsnapshot resturns snapshot p for all table but actually the snapshot
> name is "p/s";
> also the data directory is like the format :
> datapath/snapshots/p/s/snapshot-datafile-link
> !snapshot-p-s.jpg!
> !listsnapshots-p-s.jpg!
> 2. nodetool snapshot -t "/"
> the listsnapshot resturns "there is not snapshot"; but the make snapshot
> process return successfully and the data directory is like the format :
> datapath/snapshots/snapshot-datafile-link
> !snapshot-listsnapshot-.jpg!
> the Attachements are the result under our environment.
> so for me , we suggest that the snapshot name should not contains special
> character. just throw exception and told the user not to use special
> character.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488501#comment-17488501
]
David Capwell commented on CASSANDRA-17353:
---
+1 the latest commit
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17267) Snapshot true size is miscalculated
[
https://issues.apache.org/jira/browse/CASSANDRA-17267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488499#comment-17488499
]
Paulo Motta commented on CASSANDRA-17267:
-
Curiously this did not reproduce on 3.0, so I used the same approach of
comparing the names of the snapshot files with the files present in the live
set to skip accounting live sstables during snapshot true size calculation.
ccm repro after fix:
{noformat}
% ccm node1 nodetool -- snapshot -t test test_ks
Requested creating snapshot(s) for [test_ks] with snapshot name [test]
Snapshot directory: test
% ccm node1 nodetool tablestats test_ks.tbl | grep -i snapshot
Space used by snapshots (total): 0
% ccm node1 nodetool listsnapshots
Snapshot Details:
Snapshot name Keyspace name Column family name True size Size on disk
test test_ks tbl0 bytes 5.74 KB
Total TrueDiskSpaceUsed: 0 bytes
% ccm node1 nodetool compact test_ks tbl
% ccm node1 nodetool tablestats test_ks.tbl | grep -i snapshot
Space used by snapshots (total): 5044
% ccm node1 nodetool listsnapshots
Snapshot Details:
Snapshot name Keyspace name Column family name True size Size on disk
test test_ks tbl4.93 KB 5.74 KB
Total TrueDiskSpaceUsed: 4.93 KB
{noformat}
I will use the new approach of using only the directory structure to decide
whether a snapshot file is present in the live set when decoupling snapshot
size computation from {{ColumnFamilyStore}} on CASSANDRA-16843.
While working on this I noticed that secondary indexes are not included in the
computation of the true size so I created CASSANDRA-17357 to address this
separately.
3.11+ patches and CI below:
|[3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...pauloricardomg:CASSANDRA-17267-3.11]|[tests|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1414/]|
|[4.0|https://github.com/apache/cassandra/compare/cassandra-4.0...pauloricardomg:CASSANDRA-17267-4.0]|[tests|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1415/]|
|[trunk|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:CASSANDRA-17267-trunk]|[tests|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1416/]|
> Snapshot true size is miscalculated
> ---
>
> Key: CASSANDRA-17267
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17267
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Snapshots
>Reporter: Paulo Motta
>Assignee: Paulo Motta
>Priority: Normal
>
> As far as I understand, the snapshot "size on disk" is the total size of the
> snapshot, while the "true size" is the (size_on_disk - size_of_live_sstables).
> I created a snapshot on a 3.11 node without traffic and I expected the "true
> size" to be 0KB since the original sstables were still present, but this
> didn't seem to be the case:
> {noformat}
> $ nodetool listsnapshots
> Snapshot Details:
> Snapshot name Keyspace name Column family name True size Size on disk
> test ks1 tbl1 4.86 KiB 5.69 KiB
> Total TrueDiskSpaceUsed: 4.86 KiB
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17356: - Impacts: Docs (was: None) Status: Patch Available (was: Open) https://github.com/apache/cassandra-website/pull/98 > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17356: - Source Control Link: https://github.com/apache/cassandra-website/pull/98/commits/1b06344161091e80f8c78d8ab009183cae751e3c > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17355) Performance degradation with Counter tables when the data size grows
[
https://issues.apache.org/jira/browse/CASSANDRA-17355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488486#comment-17488486
]
Brandon Williams commented on CASSANDRA-17355:
--
On the surface, I would be more surprised if performance worked the other way.
> Performance degradation with Counter tables when the data size grows
>
>
> Key: CASSANDRA-17355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17355
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Normal
>
> Hello Everyone,
> I am noticing a huge perf drop (spike in latency and CPU utilization) for the
> counter type tables when the data size grows. To better understand/simulate I
> have done the following perf test with `cassandra-stress` instead of my
> use-case and I can reproduce the performance issue consistently. When using
> the counter type tables, when the datasize grows the read latency and cpu
> spikes to very high number.
>
> *Test Setup:*
> # Setup a cluster with 3 nodes.
> # Run a test with cassandra-stress and I see the latency and CPU are okay
> without much spike.
> # Send a lot of counter traffic using `cassandra-stress` tool (Replication
> Factory = 3)
> # Now the data size on the cluster is ~300G.
> # Now run another test with cassandra-stress with 3:1 read write mixed
> workload.
> # At this point I see the CPU spikes to double (32 on a 16 core CPU) and the
> latency reaches ~1 seconds (which earlier was < 5ms).
> # Another interesting observation is the disk reads goes to a higher number
> and it keeps going higher with the increase in the disk size.
> # It pretty much looked like a disk bottleneck issue but the same result
> shows very low disk reads, cpu, latency with less amount of data.
> # Below is the configuration I have used for testing this.
>
> {quote}C* Version: 3.11.9
> CPU: 16
> Memory: 64G
> Heap: 16G
> GC: G1GC
> Disk: 500G GCP Persistent disk
>
> {quote}
> I understand that, with growth in disk the number of lookup grows high, but
> this looked to be a big performance drop.
> Please let me know if you need more details. Also let me know this is known
> limitation with the counter type and if there is a work around.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17356: - Status: Open (was: Triage Needed) > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diogenese Topper updated CASSANDRA-17356: - Authors: Chris Thornett Change Category: Semantic Complexity: Normal Fix Version/s: NA Reviewers: Erick Ramirez Test and Documentation Plan: * Add blog post titled "Apache Cassandra Changelog #12" * Modify blog index page * Add image for blog Tester: Erick Ramirez Labels: pull-request-available (was: ) > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17357) Snapshot true size computation does not include secondary indexes
[
https://issues.apache.org/jira/browse/CASSANDRA-17357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-17357:
Bug Category: Parent values: Correctness(12982)Level 1 values: API /
Semantic Definition(13162)
Complexity: Normal
Discovered By: Code Inspection
Fix Version/s: 4.1
Severity: Low
Status: Open (was: Triage Needed)
> Snapshot true size computation does not include secondary indexes
> -
>
> Key: CASSANDRA-17357
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17357
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Snapshots
>Reporter: Paulo Motta
>Assignee: Paulo Motta
>Priority: Normal
> Fix For: 4.1
>
>
> The true size is supposed to show the total size of the snapshot minus any
> live sstables.
> Nevertheless, sstables from secondary indexes are not included in the
> computation of the true size, causing a mismatch between the true size and
> snapshot size when there are indexes and no live sstables.
> It's possible to fetch the global snapshot size per table and indexes
> separately via nodetool tablestats, but not for individual snapshots.
> This behavior seems to be there since before 3.0, so I think it has always
> been like this.
> Reproduction steps:
> {noformat}
> % ccm node1 nodetool -- snapshot -t test test_ks
> Requested creating snapshot(s) for [test_ks] with snapshot name [test]
> Snapshot directory: test
> % ccm node1 nodetool listsnapshots
> Snapshot Details:
> Snapshot name Keyspace name Column family name True size Size on disk
> test test_ks tbl0 bytes 10.76 KB
> Total TrueDiskSpaceUsed: 0 bytes
> % ccm node1 nodetool tablestats test_ks.tbl | grep -i snapshot
> Space used by snapshots (total): 0
> % ccm node1 nodetool tablestats test_ks.tbl.tbl_val_idx | grep -i snapshot
> Space used by snapshots (total): 0
> % ccm node1 nodetool compact test_ks tbl.tbl_val_idx
> % ccm node1 nodetool compact test_ks tbl_val_idx
> % ccm node1 nodetool tablestats test_ks.tbl | grep -i snapshot
> Space used by snapshots (total): 5027
> % ccm node1 nodetool tablestats test_ks.tbl.tbl_val_idx | grep -i snapshot
> Space used by snapshots (total): 5060
> % ccm node1 nodetool listsnapshots
> Snapshot Details:
> Snapshot name Keyspace name Column family name True size Size on disk
> test test_ks tbl4.91 KB 10.76 KB
> Total TrueDiskSpaceUsed: 4.91 KB
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-in-jvm-dtest-api] branch trunk updated: Add support for vnodes in jvm-dtest
This is an automated email from the ASF dual-hosted git repository.
dcapwell pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-in-jvm-dtest-api.git
The following commit(s) were added to refs/heads/trunk by this push:
new c629105 Add support for vnodes in jvm-dtest
c629105 is described below
commit c629105d15a10d6166ddf393dc38d0b0ab87743d
Author: dcapwell
AuthorDate: Mon Feb 7 15:15:51 2022 -0800
Add support for vnodes in jvm-dtest
Patch by David Capwell; reviewed by Alex Petrov, Josh McKenzie for
CASSANDRA-17332
---
pom.xml| 6 ++
.../apache/cassandra/distributed/api/ICluster.java | 11 +++-
.../cassandra/distributed/api/QueryResults.java| 2 +-
.../org/apache/cassandra/distributed/api/Row.java | 22 +--
.../distributed/api/SimpleQueryResult.java | 14 ++--
.../cassandra/distributed/api/TokenSupplier.java | 41 ++--
.../distributed/shared/AbstractBuilder.java| 58 -
.../cassandra/distributed/shared/Versions.java | 10 ++-
.../distributed/api/TokenSupplierTest.java | 75 ++
9 files changed, 216 insertions(+), 23 deletions(-)
diff --git a/pom.xml b/pom.xml
index 534390e..7dc5603 100644
--- a/pom.xml
+++ b/pom.xml
@@ -80,6 +80,12 @@
3.5.10
test
+
+org.quicktheories
+quicktheories
+0.26
+test
+
diff --git a/src/main/java/org/apache/cassandra/distributed/api/ICluster.java
b/src/main/java/org/apache/cassandra/distributed/api/ICluster.java
index 4af4ae5..f5ff75d 100644
--- a/src/main/java/org/apache/cassandra/distributed/api/ICluster.java
+++ b/src/main/java/org/apache/cassandra/distributed/api/ICluster.java
@@ -24,13 +24,14 @@ import java.net.InetSocketAddress;
import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;
+import java.util.Iterator;
import java.util.function.BiPredicate;
import java.util.function.Predicate;
import java.util.stream.Stream;
-public interface ICluster extends AutoCloseable
+public interface ICluster extends AutoCloseable,
Iterable
{
-public static final String PROPERTY_PREFIX = "cassandra.test";
+String PROPERTY_PREFIX = "cassandra.test";
void startup();
@@ -54,6 +55,12 @@ public interface ICluster extends
AutoCloseable
Stream stream(String dcName, String rackName);
+@Override
+default Iterator iterator()
+{
+return stream().iterator();
+}
+
IMessageFilters filters();
default void setMessageSink(IMessageSink messageSink) { throw new
UnsupportedOperationException(); }
diff --git
a/src/main/java/org/apache/cassandra/distributed/api/QueryResults.java
b/src/main/java/org/apache/cassandra/distributed/api/QueryResults.java
index 081d06a..b1c5ca7 100644
--- a/src/main/java/org/apache/cassandra/distributed/api/QueryResults.java
+++ b/src/main/java/org/apache/cassandra/distributed/api/QueryResults.java
@@ -58,7 +58,7 @@ public final class QueryResults
@Override
public Row next()
{
-row.setResults(iterator.next());
+row.unsafeSetResults(iterator.next());
return row;
}
});
diff --git a/src/main/java/org/apache/cassandra/distributed/api/Row.java
b/src/main/java/org/apache/cassandra/distributed/api/Row.java
index ff4efbe..5487d5f 100644
--- a/src/main/java/org/apache/cassandra/distributed/api/Row.java
+++ b/src/main/java/org/apache/cassandra/distributed/api/Row.java
@@ -19,10 +19,8 @@
package org.apache.cassandra.distributed.api;
import java.util.Arrays;
-import java.util.Collections;
import java.util.Date;
import java.util.HashMap;
-import java.util.List;
import java.util.Map;
import java.util.NoSuchElementException;
import java.util.Objects;
@@ -62,8 +60,24 @@ public class Row
this.nameIndex = nameIndex;
}
-void setResults(Object[] results)
+public static Row of(Object... results)
{
+String[] names = new String[results.length];
+for (int i = 0; i < names.length; i++)
+names[i] = "c" + i;
+Row row = new Row(names);
+row.setResults(results);
+return row;
+}
+
+void unsafeSetResults(Object[] results)
+{
+this.results = results;
+}
+
+public void setResults(Object... results)
+{
+assert names.length == results.length : "Column names " +
Arrays.toString(names) + " does not have the same length as results " +
Arrays.toString(results);
this.results = results;
}
@@ -73,7 +87,7 @@ public class Row
public Row copy()
{
Row copy = new Row(names, nameIndex);
-copy.setResults(results);
+copy.unsafeSetResults(results);
return copy;
}
diff --git
[jira] [Commented] (CASSANDRA-17332) Add support for vnodes in jvm-dtest
[ https://issues.apache.org/jira/browse/CASSANDRA-17332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488485#comment-17488485 ] David Capwell commented on CASSANDRA-17332: --- Merged jvm-dtest api changes https://github.com/apache/cassandra-in-jvm-dtest-api/commit/c629105d15a10d6166ddf393dc38d0b0ab87743d > Add support for vnodes in jvm-dtest > --- > > Key: CASSANDRA-17332 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17332 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: 4.x > > > Right now python dtests need to keep running after being ported to jvm-dtests > as vnode support is not present, to fully deprecate the python dtests, we > need vnode support in jvm-dtest. > Sadly, to add support we need to break binary compatibility, but can maintain > source compatibility… so will need to bump every jar across every branch > (mostly due to TokenSupplier) -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17357) Snapshot true size computation does not include secondary indexes
Paulo Motta created CASSANDRA-17357:
---
Summary: Snapshot true size computation does not include secondary
indexes
Key: CASSANDRA-17357
URL: https://issues.apache.org/jira/browse/CASSANDRA-17357
Project: Cassandra
Issue Type: Bug
Components: Local/Snapshots
Reporter: Paulo Motta
Assignee: Paulo Motta
The true size is supposed to show the total size of the snapshot minus any live
sstables.
Nevertheless, sstables from secondary indexes are not included in the
computation of the true size, causing a mismatch between the true size and
snapshot size when there are indexes and no live sstables.
It's possible to fetch the global snapshot size per table and indexes
separately via nodetool tablestats, but not for individual snapshots.
This behavior seems to be there since before 3.0, so I think it has always been
like this.
Reproduction steps:
{noformat}
% ccm node1 nodetool -- snapshot -t test test_ks
Requested creating snapshot(s) for [test_ks] with snapshot name [test]
Snapshot directory: test
% ccm node1 nodetool listsnapshots
Snapshot Details:
Snapshot name Keyspace name Column family name True size Size on disk
test test_ks tbl0 bytes 10.76 KB
Total TrueDiskSpaceUsed: 0 bytes
% ccm node1 nodetool tablestats test_ks.tbl | grep -i snapshot
Space used by snapshots (total): 0
% ccm node1 nodetool tablestats test_ks.tbl.tbl_val_idx | grep -i snapshot
Space used by snapshots (total): 0
% ccm node1 nodetool compact test_ks tbl.tbl_val_idx
% ccm node1 nodetool compact test_ks tbl_val_idx
% ccm node1 nodetool tablestats test_ks.tbl | grep -i snapshot
Space used by snapshots (total): 5027
% ccm node1 nodetool tablestats test_ks.tbl.tbl_val_idx | grep -i snapshot
Space used by snapshots (total): 5060
% ccm node1 nodetool listsnapshots
Snapshot Details:
Snapshot name Keyspace name Column family name True size Size on disk
test test_ks tbl4.91 KB 10.76 KB
Total TrueDiskSpaceUsed: 4.91 KB
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17355) Performance degradation with Counter tables when the data size grows
[
https://issues.apache.org/jira/browse/CASSANDRA-17355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488484#comment-17488484
]
Jai Bheemsen Rao Dhanwada commented on CASSANDRA-17355:
---
I will reach out to the community user group but the issue i see here is the
performance drops as soon as the data size grows. Is that expected?
> Performance degradation with Counter tables when the data size grows
>
>
> Key: CASSANDRA-17355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17355
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Normal
>
> Hello Everyone,
> I am noticing a huge perf drop (spike in latency and CPU utilization) for the
> counter type tables when the data size grows. To better understand/simulate I
> have done the following perf test with `cassandra-stress` instead of my
> use-case and I can reproduce the performance issue consistently. When using
> the counter type tables, when the datasize grows the read latency and cpu
> spikes to very high number.
>
> *Test Setup:*
> # Setup a cluster with 3 nodes.
> # Run a test with cassandra-stress and I see the latency and CPU are okay
> without much spike.
> # Send a lot of counter traffic using `cassandra-stress` tool (Replication
> Factory = 3)
> # Now the data size on the cluster is ~300G.
> # Now run another test with cassandra-stress with 3:1 read write mixed
> workload.
> # At this point I see the CPU spikes to double (32 on a 16 core CPU) and the
> latency reaches ~1 seconds (which earlier was < 5ms).
> # Another interesting observation is the disk reads goes to a higher number
> and it keeps going higher with the increase in the disk size.
> # It pretty much looked like a disk bottleneck issue but the same result
> shows very low disk reads, cpu, latency with less amount of data.
> # Below is the configuration I have used for testing this.
>
> {quote}C* Version: 3.11.9
> CPU: 16
> Memory: 64G
> Heap: 16G
> GC: G1GC
> Disk: 500G GCP Persistent disk
>
> {quote}
> I understand that, with growth in disk the number of lookup grows high, but
> this looked to be a big performance drop.
> Please let me know if you need more details. Also let me know this is known
> limitation with the counter type and if there is a work around.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
Diogenese Topper created CASSANDRA-17356: Summary: WEBSITE - February 2022 changelog #12 Key: CASSANDRA-17356 URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 Project: Cassandra Issue Type: Task Components: Documentation/Blog Reporter: Diogenese Topper This ticket is to capture the work associated with publishing the January 2022 changelog blog #12 If this blog cannot be published by the *February 10, 2022 publish date*, please contact me, suggest changes, or correct the date when possible in the pull request for the appropriate time that the blog will go live (on both the blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17332) Add support for vnodes in jvm-dtest
[ https://issues.apache.org/jira/browse/CASSANDRA-17332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17332: -- Reviewers: Alex Petrov, Josh McKenzie (was: Josh McKenzie) > Add support for vnodes in jvm-dtest > --- > > Key: CASSANDRA-17332 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17332 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: 4.x > > > Right now python dtests need to keep running after being ported to jvm-dtests > as vnode support is not present, to fully deprecate the python dtests, we > need vnode support in jvm-dtest. > Sadly, to add support we need to break binary compatibility, but can maintain > source compatibility… so will need to bump every jar across every branch > (mostly due to TokenSupplier) -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17031) Add support for PEM based key material for SSL
[
https://issues.apache.org/jira/browse/CASSANDRA-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488471#comment-17488471
]
Stefan Miklosovic commented on CASSANDRA-17031:
---
https://github.com/apache/cassandra/commit/3655b26adf8d3b94095924920d05cc1a16d0f4c0
> Add support for PEM based key material for SSL
> --
>
> Key: CASSANDRA-17031
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17031
> Project: Cassandra
> Issue Type: Improvement
> Components: Messaging/Internode
>Reporter: Maulin Vasavada
>Assignee: Maulin Vasavada
>Priority: Normal
> Fix For: 4.1
>
> Time Spent: 7h 50m
> Remaining Estimate: 0h
>
> h1. Scope
> Currently Cassandra supports standard keystore types for SSL
> keys/certificates. The scope of this enhancement is to add support for PEM
> based key material (keys/certificate) given that PEM is widely used common
> format for the same. We intend to add support for Unencrypted and Password
> Based Encrypted (PBE) PKCS#8 formatted Private Keys in PEM format with
> standard algorithms (RSA, DSA and EC) along with the certificate chain for
> the private key and PEM based X509 certificates. The work here is going to be
> built on top of [CEP-9: Make SSLContext creation
> pluggable|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-9%3A+Make+SSLContext+creation+pluggable]
> for which the code is merged for Apache Cassandra 4.1 release.
> We intend to support the key material be configured as direct PEM values
> input OR via the file (configured with keystore and truststore configurations
> today). We are not going to model PEM as a valid 'store_type' given that
> 'store_type' has a [specific
> definition|https://docs.oracle.com/en/java/javase/11/security/java-cryptography-architecture-jca-reference-guide.html#GUID-AB51DEFD-5238-4F96-967F-082F6D34FBEA].
>
> h1. Approach
> Create an implementation for
> [ISslContextFactory|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/security/ISslContextFactory.java]
> extending
> [FileBasedSslContextFactory|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/security/FileBasedSslContextFactory.java]
> implementation to add PEM formatted key/certificates.
> h1. Motivation
> PEM is a widely used format for encoding Private Keys and X.509 Certificates
> and Apache Cassandra's current implementation lacks the support for
> specifying the PEM formatted key material for SSL configurations. This means
> operators have to re-create the key material to comply to the supported
> formats (using key/trust store types - jks, pkcs12 etc) and deal with an
> operational task for managing it. This is an operational overhead we can
> avoid by supporting the PEM format making Apache Cassandra even more customer
> friendly and drive more adoption.
> h1. Proposed Changes
> # A new implementation for ISslContextFactory - PEMBasedSslContextFactory
> with the following supported configuration
> {panel:title=New configurations}
> {panel}
> |{{encryption_options: }}
> {{}}{{ssl_context_factory:}}
> {{}}{{class_name:
> org.apache.cassandra.security.PEMBasedSslContextFactory}}
> {{}}{{parameters:}}
> {{ }}{{private_key: certificate chain>}}
> {{ }}{{private_key_password: }}{{private}} {{key }}{{if}} {{it is encrypted>}}
> {{ }}{{trusted_certificates: }}|
> *NOTE:* We could reuse 'keystore_password' instead of the
> 'private_key_password'. However PEM encoded private key is not a 'keystore'
> in itself hence it would be inappropriate to piggyback on that other than
> avoid duplicating similar fields.
> # The PEMBasedSslContextFactory will also support file based key material
> (and the corresponding HOT Reloading based on file timestamp updates) for the
> PEM format via existing 'keystore' and 'truststore' encryption options.
> However in that case the 'truststore_password' configuration won't be used
> since generally PEM formatted certificates for truststore don't get encrypted
> with a password.
> # The PEMBasedSslContextFactory will internally create PKCS12 keystore for
> private key and the trusted certificates. However, this doesn't impact the
> user of the implementation in anyway and it is mentioned for clarity only.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17031) Add support for PEM based key material for SSL
[
https://issues.apache.org/jira/browse/CASSANDRA-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17031:
--
Source Control Link:
https://github.com/apache/cassandra/commit/3655b26adf8d3b94095924920d05cc1a16d0f4c0
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Add support for PEM based key material for SSL
> --
>
> Key: CASSANDRA-17031
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17031
> Project: Cassandra
> Issue Type: Improvement
> Components: Messaging/Internode
>Reporter: Maulin Vasavada
>Assignee: Maulin Vasavada
>Priority: Normal
> Fix For: 4.1
>
> Time Spent: 7h 50m
> Remaining Estimate: 0h
>
> h1. Scope
> Currently Cassandra supports standard keystore types for SSL
> keys/certificates. The scope of this enhancement is to add support for PEM
> based key material (keys/certificate) given that PEM is widely used common
> format for the same. We intend to add support for Unencrypted and Password
> Based Encrypted (PBE) PKCS#8 formatted Private Keys in PEM format with
> standard algorithms (RSA, DSA and EC) along with the certificate chain for
> the private key and PEM based X509 certificates. The work here is going to be
> built on top of [CEP-9: Make SSLContext creation
> pluggable|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-9%3A+Make+SSLContext+creation+pluggable]
> for which the code is merged for Apache Cassandra 4.1 release.
> We intend to support the key material be configured as direct PEM values
> input OR via the file (configured with keystore and truststore configurations
> today). We are not going to model PEM as a valid 'store_type' given that
> 'store_type' has a [specific
> definition|https://docs.oracle.com/en/java/javase/11/security/java-cryptography-architecture-jca-reference-guide.html#GUID-AB51DEFD-5238-4F96-967F-082F6D34FBEA].
>
> h1. Approach
> Create an implementation for
> [ISslContextFactory|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/security/ISslContextFactory.java]
> extending
> [FileBasedSslContextFactory|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/security/FileBasedSslContextFactory.java]
> implementation to add PEM formatted key/certificates.
> h1. Motivation
> PEM is a widely used format for encoding Private Keys and X.509 Certificates
> and Apache Cassandra's current implementation lacks the support for
> specifying the PEM formatted key material for SSL configurations. This means
> operators have to re-create the key material to comply to the supported
> formats (using key/trust store types - jks, pkcs12 etc) and deal with an
> operational task for managing it. This is an operational overhead we can
> avoid by supporting the PEM format making Apache Cassandra even more customer
> friendly and drive more adoption.
> h1. Proposed Changes
> # A new implementation for ISslContextFactory - PEMBasedSslContextFactory
> with the following supported configuration
> {panel:title=New configurations}
> {panel}
> |{{encryption_options: }}
> {{}}{{ssl_context_factory:}}
> {{}}{{class_name:
> org.apache.cassandra.security.PEMBasedSslContextFactory}}
> {{}}{{parameters:}}
> {{ }}{{private_key: certificate chain>}}
> {{ }}{{private_key_password: }}{{private}} {{key }}{{if}} {{it is encrypted>}}
> {{ }}{{trusted_certificates: }}|
> *NOTE:* We could reuse 'keystore_password' instead of the
> 'private_key_password'. However PEM encoded private key is not a 'keystore'
> in itself hence it would be inappropriate to piggyback on that other than
> avoid duplicating similar fields.
> # The PEMBasedSslContextFactory will also support file based key material
> (and the corresponding HOT Reloading based on file timestamp updates) for the
> PEM format via existing 'keystore' and 'truststore' encryption options.
> However in that case the 'truststore_password' configuration won't be used
> since generally PEM formatted certificates for truststore don't get encrypted
> with a password.
> # The PEMBasedSslContextFactory will internally create PKCS12 keystore for
> private key and the trusted certificates. However, this doesn't impact the
> user of the implementation in anyway and it is mentioned for clarity only.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17355) Performance degradation with Counter tables when the data size grows
[
https://issues.apache.org/jira/browse/CASSANDRA-17355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17355:
-
Resolution: Not A Problem
Status: Resolved (was: Triage Needed)
> Performance degradation with Counter tables when the data size grows
>
>
> Key: CASSANDRA-17355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17355
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Normal
>
> Hello Everyone,
> I am noticing a huge perf drop (spike in latency and CPU utilization) for the
> counter type tables when the data size grows. To better understand/simulate I
> have done the following perf test with `cassandra-stress` instead of my
> use-case and I can reproduce the performance issue consistently. When using
> the counter type tables, when the datasize grows the read latency and cpu
> spikes to very high number.
>
> *Test Setup:*
> # Setup a cluster with 3 nodes.
> # Run a test with cassandra-stress and I see the latency and CPU are okay
> without much spike.
> # Send a lot of counter traffic using `cassandra-stress` tool (Replication
> Factory = 3)
> # Now the data size on the cluster is ~300G.
> # Now run another test with cassandra-stress with 3:1 read write mixed
> workload.
> # At this point I see the CPU spikes to double (32 on a 16 core CPU) and the
> latency reaches ~1 seconds (which earlier was < 5ms).
> # Another interesting observation is the disk reads goes to a higher number
> and it keeps going higher with the increase in the disk size.
> # It pretty much looked like a disk bottleneck issue but the same result
> shows very low disk reads, cpu, latency with less amount of data.
> # Below is the configuration I have used for testing this.
>
> {quote}C* Version: 3.11.9
> CPU: 16
> Memory: 64G
> Heap: 16G
> GC: G1GC
> Disk: 500G GCP Persistent disk
>
> {quote}
> I understand that, with growth in disk the number of lookup grows high, but
> this looked to be a big performance drop.
> Please let me know if you need more details. Also let me know this is known
> limitation with the counter type and if there is a work around.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17355) Performance degradation with Counter tables when the data size grows
[
https://issues.apache.org/jira/browse/CASSANDRA-17355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488458#comment-17488458
]
Brandon Williams commented on CASSANDRA-17355:
--
If you are seeing a large drop between versions that is something to be
investigated, but if you are experiencing that counters have different
performance characteristics in general, that is not surprising. I recommend
contacting the community for further guidance:
https://cassandra.apache.org/_/community.html
> Performance degradation with Counter tables when the data size grows
>
>
> Key: CASSANDRA-17355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17355
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Normal
>
> Hello Everyone,
> I am noticing a huge perf drop (spike in latency and CPU utilization) for the
> counter type tables when the data size grows. To better understand/simulate I
> have done the following perf test with `cassandra-stress` instead of my
> use-case and I can reproduce the performance issue consistently. When using
> the counter type tables, when the datasize grows the read latency and cpu
> spikes to very high number.
>
> *Test Setup:*
> # Setup a cluster with 3 nodes.
> # Run a test with cassandra-stress and I see the latency and CPU are okay
> without much spike.
> # Send a lot of counter traffic using `cassandra-stress` tool (Replication
> Factory = 3)
> # Now the data size on the cluster is ~300G.
> # Now run another test with cassandra-stress with 3:1 read write mixed
> workload.
> # At this point I see the CPU spikes to double (32 on a 16 core CPU) and the
> latency reaches ~1 seconds (which earlier was < 5ms).
> # Another interesting observation is the disk reads goes to a higher number
> and it keeps going higher with the increase in the disk size.
> # It pretty much looked like a disk bottleneck issue but the same result
> shows very low disk reads, cpu, latency with less amount of data.
> # Below is the configuration I have used for testing this.
>
> {quote}C* Version: 3.11.9
> CPU: 16
> Memory: 64G
> Heap: 16G
> GC: G1GC
> Disk: 500G GCP Persistent disk
>
> {quote}
> I understand that, with growth in disk the number of lookup grows high, but
> this looked to be a big performance drop.
> Please let me know if you need more details. Also let me know this is known
> limitation with the counter type and if there is a work around.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17355) Performance degradation with Counter tables when the data size grows
[
https://issues.apache.org/jira/browse/CASSANDRA-17355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jai Bheemsen Rao Dhanwada updated CASSANDRA-17355:
--
Description:
Hello Everyone,
I am noticing a huge perf drop (spike in latency and CPU utilization) for the
counter type tables when the data size grows. To better understand/simulate I
have done the following perf test with `cassandra-stress` instead of my
use-case and I can reproduce the performance issue consistently. When using the
counter type tables, when the datasize grows the read latency and cpu spikes to
very high number.
*Test Setup:*
# Setup a cluster with 3 nodes.
# Run a test with cassandra-stress and I see the latency and CPU are okay
without much spike.
# Send a lot of counter traffic using `cassandra-stress` tool (Replication
Factory = 3)
# Now the data size on the cluster is ~300G.
# Now run another test with cassandra-stress with 3:1 read write mixed
workload.
# At this point I see the CPU spikes to double (32 on a 16 core CPU) and the
latency reaches ~1 seconds (which earlier was < 5ms).
# Another interesting observation is the disk reads goes to a higher number
and it keeps going higher with the increase in the disk size.
# It pretty much looked like a disk bottleneck issue but the same result shows
very low disk reads, cpu, latency with less amount of data.
# Below is the configuration I have used for testing this.
{quote}C* Version: 3.11.9
CPU: 16
Memory: 64G
Heap: 16G
GC: G1GC
Disk: 500G GCP Persistent disk
{quote}
I understand that, with growth in disk the number of lookup grows high, but
this looked to be a big performance drop.
Please let me know if you need more details. Also let me know this is known
limitation with the counter type and if there is a work around.
was:
Hello Everyone,
I am noticing a huge perf drop (spike in latency and CPU utilization) for the
counter type tables when the data size grows. To better understand/simulate I
have done the following perf test with `cassandra-stress` instead of my
use-case and I can reproduce the performance issue consistently. When using the
counter type tables, when the datasize grows the read latency and cpu spikes to
very high number.
*Test Setup:*
# Setup a cluster with 3 nodes.
# Run a test with cassandra-stress and I see the latency and CPU are okay
without much spike.
# Send a lot of counter traffic using `cassandra-stress` tool (Replication
Factory = 3)
# Now the data size on the cluster is ~300G.
# Now run another test with cassandra-stress with 3:1 read write mixed
workload.
# At this point I see the CPU spikes to double (32 on a 16 core CPU) and the
latency reaches ~1 seconds (which earlier was < 5ms).
# Another interesting observation is the disk reads goes to a higher number
and it keeps going higher with the increase in the disk size.
# It pretty much looked like a disk bottleneck issue but the same result shows
very low disk reads, cpu, latency with less amount of data.
# Below is the configuration I have used for testing this.
```
C* Version: 3.11.9
CPU: 16
Memory: 64G
Heap: 16G
GC: G1GC
Disk: 500G GCP Persistent disk
```
I understand that, with growth in disk the number of lookup grows high, but
this looked to be a big performance drop.
Please let me know if you need more details. Also let me know this is known
limitation with the counter type and if there is a work around.
> Performance degradation with Counter tables when the data size grows
>
>
> Key: CASSANDRA-17355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17355
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Normal
>
> Hello Everyone,
> I am noticing a huge perf drop (spike in latency and CPU utilization) for the
> counter type tables when the data size grows. To better understand/simulate I
> have done the following perf test with `cassandra-stress` instead of my
> use-case and I can reproduce the performance issue consistently. When using
> the counter type tables, when the datasize grows the read latency and cpu
> spikes to very high number.
>
> *Test Setup:*
> # Setup a cluster with 3 nodes.
> # Run a test with cassandra-stress and I see the latency and CPU are okay
> without much spike.
> # Send a lot of counter traffic using `cassandra-stress` tool (Replication
> Factory = 3)
> # Now the data size on the cluster is ~300G.
> # Now run another test with cassandra-stress with 3:1 read write mixed
> workload.
> # At this point I see the CPU spikes to double (32 on a 16 core CPU) and the
> latency reaches ~1 seconds (which earlier was < 5ms).
> # Another interesting observation is the disk reads goes to a higher
[jira] [Created] (CASSANDRA-17355) Performance degradation with Counter tables when the data size grows
Jai Bheemsen Rao Dhanwada created CASSANDRA-17355: - Summary: Performance degradation with Counter tables when the data size grows Key: CASSANDRA-17355 URL: https://issues.apache.org/jira/browse/CASSANDRA-17355 Project: Cassandra Issue Type: Bug Reporter: Jai Bheemsen Rao Dhanwada Hello Everyone, I am noticing a huge perf drop (spike in latency and CPU utilization) for the counter type tables when the data size grows. To better understand/simulate I have done the following perf test with `cassandra-stress` instead of my use-case and I can reproduce the performance issue consistently. When using the counter type tables, when the datasize grows the read latency and cpu spikes to very high number. *Test Setup:* # Setup a cluster with 3 nodes. # Run a test with cassandra-stress and I see the latency and CPU are okay without much spike. # Send a lot of counter traffic using `cassandra-stress` tool (Replication Factory = 3) # Now the data size on the cluster is ~300G. # Now run another test with cassandra-stress with 3:1 read write mixed workload. # At this point I see the CPU spikes to double (32 on a 16 core CPU) and the latency reaches ~1 seconds (which earlier was < 5ms). # Another interesting observation is the disk reads goes to a higher number and it keeps going higher with the increase in the disk size. # It pretty much looked like a disk bottleneck issue but the same result shows very low disk reads, cpu, latency with less amount of data. # Below is the configuration I have used for testing this. ``` C* Version: 3.11.9 CPU: 16 Memory: 64G Heap: 16G GC: G1GC Disk: 500G GCP Persistent disk ``` I understand that, with growth in disk the number of lookup grows high, but this looked to be a big performance drop. Please let me know if you need more details. Also let me know this is known limitation with the counter type and if there is a work around. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15399) Add ability to track state in repair
[
https://issues.apache.org/jira/browse/CASSANDRA-15399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488434#comment-17488434
]
David Capwell commented on CASSANDRA-15399:
---
[~jasonstack] the main reasons I was thinking of a new table rather than an
enhancing are
1) `repairHistory` and `parentRepairHistory` tables include repairs that the
instance may not be aware of, including repairs its supposed to know about (if
its present in the table, doesn't mean any peer in the range is aware)
2) in order to get more frequent updates we would require constantly writing to
these tables; current tables see updates immediately.
#1 is the bigger one for me as I need to have some way to know what the actual
state of repair is, the goal is to leverage this to add resilience to repair
messaging
2) `repairHistory` maps to the repair_jobs table
3) `parentRepairHistory` maps to `repairs`
> Add ability to track state in repair
>
>
> Key: CASSANDRA-15399
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15399
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To enhance the visibility in repair, we should expose internal state via
> virtual tables; the state should include coordinator as well as participant
> state (validation, sync, etc.)
> I propose the following tables:
> repairs - high level summary of the global state of repair; this should be
> called on the coordinator.
> {code:sql}
> CREATE TABLE repairs (
> id uuid,
> keyspace_name text,
> table_names frozen>,
> ranges frozen>,
> coordinator text,
> participants frozen>,
> state text,
> progress_percentage float,
> last_updated_at_millis bigint,
> duration_micro bigint,
> failure_cause text,
> PRIMARY KEY ( (id) )
> )
> {code}
> repair_tasks - represents RepairJob and participants state. This will show
> if validations are running on participants and the progress they are making;
> this should be called on the coordinator.
> {code:sql}
> CREATE TABLE repair_tasks (
> id uuid,
> session_id uuid,
> keyspace_name text,
> table_name text,
> ranges frozen>,
> coordinator text,
> participant text,
> state text,
> state_description text,
> progress_percentage float, -- between 0.0 and 100.0
> last_updated_at_millis bigint,
> duration_micro bigint,
> failure_cause text,
> PRIMARY KEY ( (id), session_id, table_name, participant )
> )
> {code}
> repair_validations - shows the state of the validation task and updated
> periodically while validation is running; this should be called on the
> participants.
> {code:sql}
> CREATE TABLE repair_validations (
> id uuid,
> session_id uuid,
> ranges frozen>,
> keyspace_name text,
> table_name text,
> initiator text,
> state text,
> progress_percentage float,
> queue_duration_ms bigint,
> runtime_duration_ms bigint,
> total_duration_ms bigint,
> estimated_partitions bigint,
> partitions_processed bigint,
> estimated_total_bytes bigint,
> failure_cause text,
> PRIMARY KEY ( (id), session_id, table_name )
> )
> {code}
> The main reason for exposing virtual tables rather than exposing through
> durable tables is to make sure what is exposed is accurate. In cases of
> write failures or node failures, the durable tables could become in-accurate
> and could add edge cases where the repair is not running but the tables say
> it is; by relying on repair's internal in-memory bookkeeping, these problems
> go away.
> This jira does not try to solve the following:
> 1) repair resiliency - there are edge cases where repair hits an error and
> runs forever (at least from nodetool's perspective).
> 2) repair stream tracking - I have not learned the streaming side yet and
> what I see is multiple implementations exist, so seems like high scope. My
> hope is to punt from this jira and tackle separately.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17347) Instance failed to start up due to NPE in StartupClusterConnectivityChecker
[
https://issues.apache.org/jira/browse/CASSANDRA-17347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-17347:
--
Status: Ready to Commit (was: Review In Progress)
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||
|trunk|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17347-trunk-C63D5419-98C0-41CD-977E-D59055700079]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17347-trunk-C63D5419-98C0-41CD-977E-D59055700079]|
> Instance failed to start up due to NPE in StartupClusterConnectivityChecker
> ---
>
> Key: CASSANDRA-17347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17347
> Project: Cassandra
> Issue Type: Bug
> Components: Observability/Logging
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Instance is crashing during startup due to a NPE in
> StartupClusterConnectivityChecker with stack trace:
> {noformat}
> java.lang.NullPointerException: element cannot be mapped to a null key
> at java.util.Objects.requireNonNull(Objects.java:228)
> at
> java.util.stream.Collectors.lambda$groupingBy$45(Collectors.java:907)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> 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:566)
> at
> org.apache.cassandra.net.StartupClusterConnectivityChecker.execute(StartupClusterConnectivityChecker.java:173)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488376#comment-17488376
]
Andres de la Peña commented on CASSANDRA-17353:
---
Just added [a
commit|https://github.com/apache/cassandra/pull/1440/commits/2f12c72469ba73a6f9cd4f8f7e3bb44a76e60967]
renaming "abort" to "fail". The change is quite noisy but mostly trivial:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/1440]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1283/workflows/d624e34d-dd03-4db5-b8b6-c84d380777bd]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1283/workflows/48eb4c17-55ee-46d8-8c91-41beec84d2bb]
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17347) Instance failed to start up due to NPE in StartupClusterConnectivityChecker
[
https://issues.apache.org/jira/browse/CASSANDRA-17347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488374#comment-17488374
]
Stefan Miklosovic commented on CASSANDRA-17347:
---
+1 thanks!
> Instance failed to start up due to NPE in StartupClusterConnectivityChecker
> ---
>
> Key: CASSANDRA-17347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17347
> Project: Cassandra
> Issue Type: Bug
> Components: Observability/Logging
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Instance is crashing during startup due to a NPE in
> StartupClusterConnectivityChecker with stack trace:
> {noformat}
> java.lang.NullPointerException: element cannot be mapped to a null key
> at java.util.Objects.requireNonNull(Objects.java:228)
> at
> java.util.stream.Collectors.lambda$groupingBy$45(Collectors.java:907)
> at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> 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:566)
> at
> org.apache.cassandra.net.StartupClusterConnectivityChecker.execute(StartupClusterConnectivityChecker.java:173)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17353:
--
Reviewers: David Capwell
Status: Review In Progress (was: Patch Available)
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488331#comment-17488331
]
David Capwell commented on CASSANDRA-17353:
---
+1 from me.
I am ok renaming abort to fail in this patch or not.
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488304#comment-17488304
]
Ekaterina Dimitrova commented on CASSANDRA-17353:
-
No worries, there were too many discussions and venues for them lately. I am
absolutely fine to do it myself in follow up ticket, I also ended up not
changing the track warnings as it seems they might be even moved to JMX (maybe?
I just saw somewhere discussions on that). Just pointing it for the future.
Thanks :)
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488301#comment-17488301
]
Andres de la Peña commented on CASSANDRA-17353:
---
Oh, I missed that one. Guardrails were initially proposed with "fail" instead
of "abort", we changed to "abort" during the review of CASSANDRA-17147. If we
have agreed on consistently using "fail", this ticket seems a good place to
update that on guardrails config, I'll do it in a bit.
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17354) Bump java-driver dependency in Cassandra to latest 3.x series
[ https://issues.apache.org/jira/browse/CASSANDRA-17354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie updated CASSANDRA-17354: -- Summary: Bump java-driver dependency in Cassandra to latest 3.x series (was: Bump java-driver depependency in Cassandra to latest 3.x series ) > Bump java-driver dependency in Cassandra to latest 3.x series > -- > > Key: CASSANDRA-17354 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17354 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Alex Petrov >Priority: High > Fix For: 4.x > > > We depend on java-driver for testing, and developing/validating native > protocol changes. Unfortunately, the version of drvier that is included with > Cassandra is quite ancient: 3.0.1. We need to bump this dependency to latest > in 3.x series, without upgrading to 4.0 at least for now. Unfortunately, this > is not a trivial change in build.xml (otherwise I would’ve done it rather > than opening this ticket), and bumping version breaks a few tests in all > versions, so those need to be fixed, too. > This should be a prerequiste for the next minor version release, too. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488292#comment-17488292
]
Josh McKenzie commented on CASSANDRA-17078:
---
Committed to 4.0 and trunk.
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.1, 4.0.3
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17078:
--
Fix Version/s: 4.1
4.0.3
(was: 4.x)
(was: 4.0.x)
Since Version: 4.0
Source Control Link:
https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=f2816f5a7cd0e0416870bb21b8cec8f26c05d1f7
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.1, 4.0.3
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17078:
--
Status: Ready to Commit (was: Review In Progress)
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated: Better isolate tests from each other in SSTableReaderTest
This is an automated email from the ASF dual-hosted git repository.
jmckenzie pushed a commit to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/cassandra-4.0 by this push:
new f2816f5 Better isolate tests from each other in SSTableReaderTest
f2816f5 is described below
commit f2816f5a7cd0e0416870bb21b8cec8f26c05d1f7
Author: Josh McKenzie
AuthorDate: Thu Feb 3 14:35:52 2022 -0500
Better isolate tests from each other in SSTableReaderTest
Patch by Josh McKenzie; reviewed by Aleksei Zotov and Jeremiah Jordan for
CASSANDRA-17078
---
.../cassandra/io/sstable/SSTableReaderTest.java| 75 +-
1 file changed, 29 insertions(+), 46 deletions(-)
diff --git a/test/unit/org/apache/cassandra/io/sstable/SSTableReaderTest.java
b/test/unit/org/apache/cassandra/io/sstable/SSTableReaderTest.java
index f1fc4cb..1246130 100644
--- a/test/unit/org/apache/cassandra/io/sstable/SSTableReaderTest.java
+++ b/test/unit/org/apache/cassandra/io/sstable/SSTableReaderTest.java
@@ -69,6 +69,8 @@ public class SSTableReaderTest
public static final String KEYSPACE1 = "SSTableReaderTest";
public static final String CF_STANDARD = "Standard1";
public static final String CF_STANDARD2 = "Standard2";
+public static final String CF_STANDARD3 = "Standard3";
+public static final String CF_MOVE_AND_OPEN = "MoveAndOpen";
public static final String CF_COMPRESSED = "Compressed";
public static final String CF_INDEXED = "Indexed1";
public static final String CF_STANDARD_LOW_INDEX_INTERVAL =
"StandardLowIndexInterval";
@@ -89,6 +91,8 @@ public class SSTableReaderTest
KeyspaceParams.simple(1),
SchemaLoader.standardCFMD(KEYSPACE1,
CF_STANDARD),
SchemaLoader.standardCFMD(KEYSPACE1,
CF_STANDARD2),
+SchemaLoader.standardCFMD(KEYSPACE1,
CF_STANDARD3),
+SchemaLoader.standardCFMD(KEYSPACE1,
CF_MOVE_AND_OPEN),
SchemaLoader.standardCFMD(KEYSPACE1,
CF_COMPRESSED).compression(CompressionParams.DEFAULT),
SchemaLoader.compositeIndexCFMD(KEYSPACE1,
CF_INDEXED, true),
SchemaLoader.standardCFMD(KEYSPACE1,
CF_STANDARD_LOW_INDEX_INTERVAL)
@@ -107,9 +111,7 @@ public class SSTableReaderTest
@Test
public void testGetPositionsForRanges()
{
-Keyspace keyspace = Keyspace.open(KEYSPACE1);
-ColumnFamilyStore store = keyspace.getColumnFamilyStore(CF_STANDARD2);
-store.discardSSTables(System.currentTimeMillis());
+ColumnFamilyStore store = discardSSTables(KEYSPACE1, CF_STANDARD2);
partitioner = store.getPartitioner();
// insert data and compact to a single sstable
@@ -153,9 +155,7 @@ public class SSTableReaderTest
try
{
-Keyspace keyspace = Keyspace.open(KEYSPACE1);
-ColumnFamilyStore store =
keyspace.getColumnFamilyStore(CF_STANDARD);
-store.discardSSTables(System.currentTimeMillis());
+ColumnFamilyStore store = discardSSTables(KEYSPACE1, CF_STANDARD);
partitioner = store.getPartitioner();
// insert a bunch of data and compact to a single sstable
@@ -196,10 +196,7 @@ public class SSTableReaderTest
@Test
public void testPersistentStatistics()
{
-
-Keyspace keyspace = Keyspace.open(KEYSPACE1);
-ColumnFamilyStore store = keyspace.getColumnFamilyStore(CF_STANDARD);
-store.discardSSTables(System.currentTimeMillis());
+ColumnFamilyStore store = discardSSTables(KEYSPACE1, CF_STANDARD3);
partitioner = store.getPartitioner();
for (int j = 0; j < 100; j += 2)
@@ -226,9 +223,7 @@ public class SSTableReaderTest
public void testReadRateTracking()
{
// try to make sure CASSANDRA-8239 never happens again
-Keyspace keyspace = Keyspace.open(KEYSPACE1);
-ColumnFamilyStore store = keyspace.getColumnFamilyStore(CF_STANDARD);
-store.discardSSTables(System.currentTimeMillis());
+ColumnFamilyStore store = discardSSTables(KEYSPACE1, CF_STANDARD);
partitioner = store.getPartitioner();
for (int j = 0; j < 10; j++)
@@ -256,9 +251,7 @@ public class SSTableReaderTest
@Test
public void testGetPositionsForRangesWithKeyCache()
{
-Keyspace keyspace = Keyspace.open(KEYSPACE1);
-ColumnFamilyStore store = keyspace.getColumnFamilyStore(CF_STANDARD2);
-store.discardSSTables(System.currentTimeMillis());
+ColumnFamilyStore store = discardSSTables(KEYSPACE1, CF_STANDARD2);
partitioner = store.getPartitioner();
CacheService.instance.keyCache.setCapacity(100);
@@ -295,9 +288,7 @@ public class
[jira] [Updated] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17078:
Reviewers: Aleksei Zotov, Jeremiah Jordan, Ekaterina Dimitrova (was:
Aleksei Zotov, Jeremiah Jordan)
Aleksei Zotov, Jeremiah Jordan, Ekaterina Dimitrova (was:
Aleksei Zotov, Ekaterina Dimitrova, Jeremiah Jordan)
Status: Review In Progress (was: Patch Available)
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17078:
Reviewers: Aleksei Zotov, Jeremiah Jordan (was: Aleksei Zotov, Ekaterina
Dimitrova, Jeremiah Jordan)
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0' into trunk
This is an automated email from the ASF dual-hosted git repository. jmckenzie pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 72302adec8d4ffd8d7fe1c1a3542babe9b117196 Merge: 86de770 f2816f5 Author: Josh McKenzie AuthorDate: Mon Feb 7 12:47:57 2022 -0500 Merge branch 'cassandra-4.0' into trunk .../cassandra/io/sstable/SSTableReaderTest.java| 75 +- 1 file changed, 29 insertions(+), 46 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (86de770 -> 72302ad)
This is an automated email from the ASF dual-hosted git repository. jmckenzie pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 86de770 Merge branch 'cassandra-4.0' into trunk new f2816f5 Better isolate tests from each other in SSTableReaderTest new 72302ad Merge branch 'cassandra-4.0' into trunk The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../cassandra/io/sstable/SSTableReaderTest.java| 75 +- 1 file changed, 29 insertions(+), 46 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488282#comment-17488282
]
Ekaterina Dimitrova commented on CASSANDRA-17353:
-
[~adelapena] , thank you for all your work, not a review, but I just wanted to
mention that on 15234 we agreed last week to use "fail" instead of "abort" for
config. I agreed this change to be done in a follow up ticket as the patch was
already super big.
I can open a follow up ticket after you to change that but wanted to mention it
for next guardrails you work on. Also, it will be in the docs I work on
already.
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17354) Bump java-driver depependency in Cassandra to latest 3.x series
[ https://issues.apache.org/jira/browse/CASSANDRA-17354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-17354: Change Category: Quality Assurance Complexity: Low Hanging Fruit Component/s: Test/unit Fix Version/s: 4.x Priority: High (was: Normal) Status: Open (was: Triage Needed) > Bump java-driver depependency in Cassandra to latest 3.x series > > > Key: CASSANDRA-17354 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17354 > Project: Cassandra > Issue Type: Task > Components: Test/unit >Reporter: Alex Petrov >Priority: High > Fix For: 4.x > > > We depend on java-driver for testing, and developing/validating native > protocol changes. Unfortunately, the version of drvier that is included with > Cassandra is quite ancient: 3.0.1. We need to bump this dependency to latest > in 3.x series, without upgrading to 4.0 at least for now. Unfortunately, this > is not a trivial change in build.xml (otherwise I would’ve done it rather > than opening this ticket), and bumping version breaks a few tests in all > versions, so those need to be fixed, too. > This should be a prerequiste for the next minor version release, too. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17354) Bump java-driver depependency in Cassandra to latest 3.x series
Alex Petrov created CASSANDRA-17354: --- Summary: Bump java-driver depependency in Cassandra to latest 3.x series Key: CASSANDRA-17354 URL: https://issues.apache.org/jira/browse/CASSANDRA-17354 Project: Cassandra Issue Type: Task Reporter: Alex Petrov We depend on java-driver for testing, and developing/validating native protocol changes. Unfortunately, the version of drvier that is included with Cassandra is quite ancient: 3.0.1. We need to bump this dependency to latest in 3.x series, without upgrading to 4.0 at least for now. Unfortunately, this is not a trivial change in build.xml (otherwise I would’ve done it rather than opening this ticket), and bumping version breaks a few tests in all versions, so those need to be fixed, too. This should be a prerequiste for the next minor version release, too. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17353:
--
Test and Documentation Plan: It uses the current guardrails tests
Status: Patch Available (was: In Progress)
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17353:
--
Change Category: Operability
Complexity: Low Hanging Fruit
Fix Version/s: 4.x
Status: Open (was: Triage Needed)
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.x
>
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17353) Flatten guardrails configuration
[
https://issues.apache.org/jira/browse/CASSANDRA-17353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488279#comment-17488279
]
Andres de la Peña commented on CASSANDRA-17353:
---
Here is the patch flattening the configuration for guardrails, CI is still
running:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/1440]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1282/workflows/55a06910-8ede-4699-9d81-cd6e50fd00c4]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1282/workflows/2f54901b-4328-4097-ba4d-1ac217f94fd2]|
CC [~dcapwell] [~maedhroz]
> Flatten guardrails configuration
>
>
> Key: CASSANDRA-17353
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
> Project: Cassandra
> Issue Type: Task
> Components: Feature/Guardrails
>Reporter: Andres de la Peña
>Priority: Normal
>
> Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
> instead of the current nested format. This ticket comes from the discussion
> around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
> CASSANDRA-17212, and doesn't include any of the other nested properties on
> {{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488275#comment-17488275
]
Josh McKenzie edited comment on CASSANDRA-17078 at 2/7/22, 5:20 PM:
{quote}Should we backport them to 4.0 and 3.x branches?
{quote}
I'll take a look; if the tests isn't flaking out there I'd say we hold off and
I'll just keep an eye on it and backport if it starts to misbehave later. edit:
shows up on 4.0. I'll target 4.0.x and 4.x with this.
{quote}You missed removing store.discardSSTables(System.currentTimeMillis());
in testGetPositionsForRanges
{quote}
Good catch.
was (Author: jmckenzie):
bq. Should we backport them to 4.0 and 3.x branches?
I'll take a look; if the tests isn't flaking out there I'd say we hold off and
I'll just keep an eye on it and backport if it starts to misbehave later.
bq. You missed removing store.discardSSTables(System.currentTimeMillis()); in
testGetPositionsForRanges
Good catch.
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17078:
--
Fix Version/s: 4.0.x
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488275#comment-17488275
]
Josh McKenzie commented on CASSANDRA-17078:
---
bq. Should we backport them to 4.0 and 3.x branches?
I'll take a look; if the tests isn't flaking out there I'd say we hold off and
I'll just keep an eye on it and backport if it starts to misbehave later.
bq. You missed removing store.discardSSTables(System.currentTimeMillis()); in
testGetPositionsForRanges
Good catch.
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17353) Flatten guardrails configuration
Andres de la Peña created CASSANDRA-17353:
-
Summary: Flatten guardrails configuration
Key: CASSANDRA-17353
URL: https://issues.apache.org/jira/browse/CASSANDRA-17353
Project: Cassandra
Issue Type: Task
Components: Feature/Guardrails
Reporter: Andres de la Peña
Modify guardrails configuration at {{cassandra.yaml}} to have a flat format,
instead of the current nested format. This ticket comes from the discussion
around guardrails config on CASSANDRA-17292, CASSANDRA-17188 and
CASSANDRA-17212, and doesn't include any of the other nested properties on
{{cassandra.yaml}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremiah Jordan updated CASSANDRA-17078:
Reviewers: Aleksei Zotov, Jeremiah Jordan
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488260#comment-17488260
]
Jeremiah Jordan commented on CASSANDRA-17078:
-
{{You missed removing store.discardSSTables(System.currentTimeMillis()); in
}}{{{}testGetPositionsForRanges{}}}. Otherwise LGTM.
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488252#comment-17488252
]
Aleksei Zotov commented on CASSANDRA-17078:
---
The changes LGTM, +1
Should we backport them to 4.0 and 3.x branches?
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17240) CEP-19: Trie memtable implementation
[
https://issues.apache.org/jira/browse/CASSANDRA-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488240#comment-17488240
]
Branimir Lambov edited comment on CASSANDRA-17240 at 2/7/22, 4:37 PM:
--
Attached some performance data comparing the new trie memtable with the legacy
skip list one. The test we ran is a density test which runs a 90:10 write:read
workload with 100-byte payloads to over 1TB of data on an {{i3.4xlarge}}
instance with the following settings to remove some of the biggest throughput
bottlenecks:
{code:java}
memtable_allocation_type: offheap_objects
memtable_flush_writers: 8
memtable_heap_space_in_mb: 16384
memtable_offheap_space_in_mb: 16384
concurrent_reads: 256
concurrent_writes: 256
commitlog_total_space_in_mb: 51200
commitlog_segment_size_in_mb: 320
commitlog_compression:
class_name: LZ4Compressor
disk_access_mode: mmap_index_only
file_cache_size_in_mb: 8192
compaction_throughput_mb_per_sec: 0
concurrent_compactors: 30
{code}
The test is meant to measure sustained throughput, and with the current C* code
is quickly limited by the performance of compaction (compaction cannot keep up,
sstables accumulate, and reads start dominating the time). The throughput stage
graph looks like this:
!throughput_apache.png!
{{TrieMemtable}} (in red) starts off with double the performance of the legacy
{{SkipListMemtable}} (in orange), and maintains a significant lead throughout
the test. We have previously seen a significant improvement in throughput when
memtables are sharded, thus we also tested two sharded variations of the skip
list solution, with and without locking. Both versions lead over the unsharded
skip-list, but are far from the performance of the new solution. (Note: the
locking version (in green), which gives compaction threads more chances to run,
meets its performance towards the end of the test when it is completely
dominated by the effects of compaction.)
With improved and tuned compaction (using further improvements we intend to
port to C*), the trie memtable maintains ~2.3x better throughput:
!throughput_SG.png!
One interesting aspect of the comparison is the heap behavior, especially old
generation sizes, during the throughput stage.
{{{}SkipListMemtable{}}}:
!SkipListMemtable-OSS.png!
vs. {{{}TrieMemtable{}}}:
!TrieMemtable-OSS.png!
The total garbage collection time through all stages of the test is more than
halved.
Additionally, the new memtable is able to accept more data for the same memory
allocation, which results in 30% bigger L0 sstables, reducing the number of
sstables and the need for compaction and further improving performance.
was (Author: blambov):
Attached some performance data comparing the new trie memtable with the legacy
skip list one. The test we ran is a density test which runs a 90:10 write:read
workload with 100-byte payloads to over 1TB of data on an {{i3.4xlarge}}
instance with the following settings to remove some of the biggest throughput
bottlenecks:
{code:java}
memtable_allocation_type: offheap_objects
memtable_flush_writers: 8
memtable_heap_space_in_mb: 16384
memtable_offheap_space_in_mb: 16384
concurrent_reads: 256
concurrent_writes: 256
commitlog_total_space_in_mb: 51200
commitlog_segment_size_in_mb: 320
commitlog_compression:
class_name: LZ4Compressor
disk_access_mode: mmap_index_only
file_cache_size_in_mb: 8192
compaction_throughput_mb_per_sec: 0
concurrent_compactors: 30
{code}
The test is meant to measure sustained throughput, and with the current C* code
is quickly limited by the performance of compaction (compaction cannot keep up,
sstables accumulate, and reads start dominating the time). The throughput stage
graph looks like this:
!throughput_apache.png!
{{TrieMemtable}} (in red) starts off with double the performance of the legacy
{{SkipListMemtable}} (in orange), and maintains a significant lead throughout
the test. We have previously seen a significant improvement in throughput when
memtables are sharded, thus we also tested two sharded variations of the skip
list solution, with and without locking. Both versions lead over the unsharded
skip-list, but are far from the performance of the new solution. (Note: the
locking version (in green), which gives compaction threads more chances to run,
meets its performance towards the end of the test when it is completely
dominated by the effects of compaction.)
With improved and tuned compaction (using further improvements we intend to
port C*), the trie memtable maintains ~2.3x better throughput:
!throughput_SG.png!
One interesting aspect of the comparison is the heap behavior, especially old
generation sizes, during the throughput stage.
{{{}SkipListMemtable{}}}:
!SkipListMemtable-OSS.png!
vs. {{{}TrieMemtable{}}}:
!TrieMemtable-OSS.png!
The total garbage collection time through all stages of the test is more than
[jira] [Commented] (CASSANDRA-17240) CEP-19: Trie memtable implementation
[
https://issues.apache.org/jira/browse/CASSANDRA-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488240#comment-17488240
]
Branimir Lambov commented on CASSANDRA-17240:
-
Attached some performance data comparing the new trie memtable with the legacy
skip list one. The test we ran is a density test which runs a 90:10 write:read
workload with 100-byte payloads to over 1TB of data on an {{i3.4xlarge}}
instance with the following settings to remove some of the biggest throughput
bottlenecks:
{code:java}
memtable_allocation_type: offheap_objects
memtable_flush_writers: 8
memtable_heap_space_in_mb: 16384
memtable_offheap_space_in_mb: 16384
concurrent_reads: 256
concurrent_writes: 256
commitlog_total_space_in_mb: 51200
commitlog_segment_size_in_mb: 320
commitlog_compression:
class_name: LZ4Compressor
disk_access_mode: mmap_index_only
file_cache_size_in_mb: 8192
compaction_throughput_mb_per_sec: 0
concurrent_compactors: 30
{code}
The test is meant to measure sustained throughput, and with the current C* code
is quickly limited by the performance of compaction (compaction cannot keep up,
sstables accumulate, and reads start dominating the time). The throughput stage
graph looks like this:
!throughput_apache.png!
{{TrieMemtable}} (in red) starts off with double the performance of the legacy
{{SkipListMemtable}} (in orange), and maintains a significant lead throughout
the test. We have previously seen a significant improvement in throughput when
memtables are sharded, thus we also tested two sharded variations of the skip
list solution, with and without locking. Both versions lead over the unsharded
skip-list, but are far from the performance of the new solution. (Note: the
locking version (in green), which gives compaction threads more chances to run,
meets its performance towards the end of the test when it is completely
dominated by the effects of compaction.)
With improved and tuned compaction (using further improvements we intend to
port C*), the trie memtable maintains ~2.3x better throughput:
!throughput_SG.png!
One interesting aspect of the comparison is the heap behavior, especially old
generation sizes, during the throughput stage.
{{{}SkipListMemtable{}}}:
!SkipListMemtable-OSS.png!
vs. {{{}TrieMemtable{}}}:
!TrieMemtable-OSS.png!
The total garbage collection time through all stages of the test is more than
halved.
Additionally, the new memtable is able to accept more data for the same memory
allocation, which results in 30% bigger L0 sstables, reducing the number of
sstables and the need for compaction and further improving performance.
> CEP-19: Trie memtable implementation
>
>
> Key: CASSANDRA-17240
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17240
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Memtable
>Reporter: Branimir Lambov
>Priority: Normal
> Attachments: SkipListMemtable-OSS.png, TrieMemtable-OSS.png,
> density_SG.html.gz, density_test_with_sharding.html.gz, throughput_SG.png,
> throughput_apache.png
>
>
> Trie-based memtable implementation as described in CEP-19, built on top of
> CASSANDRA-17034 and CASSANDRA-6936.
> The implementation is available in this
> [branch|https://github.com/blambov/cassandra/tree/CASSANDRA-17240].
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17332) Add support for vnodes in jvm-dtest
[ https://issues.apache.org/jira/browse/CASSANDRA-17332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488227#comment-17488227 ] Josh McKenzie commented on CASSANDRA-17332: --- +1 > Add support for vnodes in jvm-dtest > --- > > Key: CASSANDRA-17332 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17332 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: 4.x > > > Right now python dtests need to keep running after being ported to jvm-dtests > as vnode support is not present, to fully deprecate the python dtests, we > need vnode support in jvm-dtest. > Sadly, to add support we need to break binary compatibility, but can maintain > source compatibility… so will need to bump every jar across every branch > (mostly due to TokenSupplier) -- This message was sent by Atlassian Jira (v8.20.1#820001) - 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 (dcfbd1c -> 30eca23)
This is an automated email from the ASF dual-hosted git repository.
blerer pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/cassandra-website.git.
discard dcfbd1c generate docs for 4ca2e248
add 03f4603 February 2022 blog "Tightening Security for Apache Cassandra
Part: 2"
add 30eca23 generate docs for 03f46031
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 (dcfbd1c)
\
N -- N -- N refs/heads/asf-site (30eca23)
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:
.../tightening-security-p2-unsplash-parado.jpg | Bin 0 -> 380748 bytes
content/_/blog.html| 24 +
...ning-Security-for-Apache-Cassandra-Part-2.html} | 175 +++
.../cassandra/configuration/cass_yaml_file.html| 577 +++--
content/doc/4.1/cassandra/operating/security.html | 6 +-
.../4.1/cassandra/tools/nodetool/bootstrap.html| 8 +-
.../tools/nodetool/getcompactionthroughput.html| 2 +-
.../tools/nodetool/getinterdcstreamthroughput.html | 2 +-
.../tools/nodetool/getstreamthroughput.html| 4 +-
.../doc/4.1/cassandra/tools/nodetool/nodetool.html | 22 +-
.../4.1/cassandra/tools/nodetool/repair_admin.html | 75 ++-
.../tools/nodetool/setbatchlogreplaythrottle.html | 2 +-
.../tools/nodetool/setcompactionthroughput.html| 4 +-
.../tools/nodetool/sethintedhandoffthrottlekb.html | 4 +-
.../tools/nodetool/setinterdcstreamthroughput.html | 4 +-
.../tools/nodetool/setstreamthroughput.html| 6 +-
.../cassandra/configuration/cass_yaml_file.html| 577 +++--
.../doc/latest/cassandra/operating/security.html | 6 +-
.../latest/cassandra/tools/nodetool/bootstrap.html | 8 +-
.../tools/nodetool/getcompactionthroughput.html| 2 +-
.../tools/nodetool/getinterdcstreamthroughput.html | 2 +-
.../tools/nodetool/getstreamthroughput.html| 4 +-
.../latest/cassandra/tools/nodetool/nodetool.html | 22 +-
.../cassandra/tools/nodetool/repair_admin.html | 75 ++-
.../tools/nodetool/setbatchlogreplaythrottle.html | 2 +-
.../tools/nodetool/setcompactionthroughput.html| 4 +-
.../tools/nodetool/sethintedhandoffthrottlekb.html | 4 +-
.../tools/nodetool/setinterdcstreamthroughput.html | 4 +-
.../tools/nodetool/setstreamthroughput.html| 6 +-
.../cassandra/configuration/cass_yaml_file.html| 577 +++--
.../doc/trunk/cassandra/operating/security.html| 6 +-
.../trunk/cassandra/tools/nodetool/bootstrap.html | 8 +-
.../tools/nodetool/getcompactionthroughput.html| 2 +-
.../tools/nodetool/getinterdcstreamthroughput.html | 2 +-
.../tools/nodetool/getstreamthroughput.html| 4 +-
.../trunk/cassandra/tools/nodetool/nodetool.html | 22 +-
.../cassandra/tools/nodetool/repair_admin.html | 75 ++-
.../tools/nodetool/setbatchlogreplaythrottle.html | 2 +-
.../tools/nodetool/setcompactionthroughput.html| 4 +-
.../tools/nodetool/sethintedhandoffthrottlekb.html | 4 +-
.../tools/nodetool/setinterdcstreamthroughput.html | 4 +-
.../tools/nodetool/setstreamthroughput.html| 6 +-
content/search-index.js| 2 +-
.../tightening-security-p2-unsplash-parado.jpg | Bin 0 -> 380748 bytes
site-content/source/modules/ROOT/pages/blog.adoc | 24 +
...ening-Security-for-Apache-Cassandra-Part-2.adoc | 96
site-ui/build/ui-bundle.zip| Bin 4740084 -> 4740084
bytes
47 files changed, 1310 insertions(+), 1159 deletions(-)
create mode 100644
content/_/_images/blog/tightening-security-p2-unsplash-parado.jpg
copy content/_/blog/{Reaper-Anti-entropy-Repair-Made-Easy.html =>
Tightening-Security-for-Apache-Cassandra-Part-2.html} (59%)
create mode 100644
site-content/source/modules/ROOT/images/blog/tightening-security-p2-unsplash-parado.jpg
create mode 100644
site-content/source/modules/ROOT/pages/blog/Tightening-Security-for-Apache-Cassandra-Part-2.adoc
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17078:
--
Test and Documentation Plan: Change to flaky test
Status: Patch Available (was: In Progress)
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17332) Add support for vnodes in jvm-dtest
[ https://issues.apache.org/jira/browse/CASSANDRA-17332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488207#comment-17488207 ] Alex Petrov commented on CASSANDRA-17332: - +1 ; the only thing I'd theoretically change is maybe return some structure that would avoid re-wrapping in array list every time we call for node id [here|https://github.com/apache/cassandra-in-jvm-dtest-api/pull/31/files#diff-41aeaeb3abc0a6c5541dbb4acf7e8ec4432fdf02ace61f5e7db00b7834f63729R56], but this is fairly minor, so I'll leave it for [~dcapwell]'s discresion > Add support for vnodes in jvm-dtest > --- > > Key: CASSANDRA-17332 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17332 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: 4.x > > > Right now python dtests need to keep running after being ported to jvm-dtests > as vnode support is not present, to fully deprecate the python dtests, we > need vnode support in jvm-dtest. > Sadly, to add support we need to break binary compatibility, but can maintain > source compatibility… so will need to bump every jar across every branch > (mostly due to TokenSupplier) -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17240) CEP-19: Trie memtable implementation
[ https://issues.apache.org/jira/browse/CASSANDRA-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Branimir Lambov updated CASSANDRA-17240: Attachment: density_SG.html.gz > CEP-19: Trie memtable implementation > > > Key: CASSANDRA-17240 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17240 > Project: Cassandra > Issue Type: Improvement > Components: Local/Memtable >Reporter: Branimir Lambov >Priority: Normal > Attachments: SkipListMemtable-OSS.png, TrieMemtable-OSS.png, > density_SG.html.gz, density_test_with_sharding.html.gz, throughput_SG.png, > throughput_apache.png > > > Trie-based memtable implementation as described in CEP-19, built on top of > CASSANDRA-17034 and CASSANDRA-6936. > The implementation is available in this > [branch|https://github.com/blambov/cassandra/tree/CASSANDRA-17240]. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17078) Fix failing test: SSTableReaderTest.testPersistentStatistics
[
https://issues.apache.org/jira/browse/CASSANDRA-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488204#comment-17488204
]
Josh McKenzie commented on CASSANDRA-17078:
---
|Item|Link|
|Branch|[Link|https://github.com/apache/cassandra/compare/trunk...josh-mckenzie:cassandra-17078?expand=1]|
|JDK8
repeat|[Link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/173/workflows/61a47fee-6514-41ab-a180-31534801b8ec]|
|JDK11
repeat|[Link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/173/workflows/0ec1e264-c0db-41aa-b5a7-01678d7237b2]|
> Fix failing test: SSTableReaderTest.testPersistentStatistics
>
>
> Key: CASSANDRA-17078
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17078
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Josh McKenzie
>Priority: Normal
> Fix For: 4.x
>
>
> JDK8 unit test failure
> See it on CircleCI but not on Jenkins ASF infra right now.
> {code:java}
> java.lang.RuntimeException: Failed importing sstables
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:164)
> at
> org.apache.cassandra.db.ColumnFamilyStore.loadNewSSTables(ColumnFamilyStore.java:734)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.clearAndLoad(SSTableReaderTest.java:222)
> at
> org.apache.cassandra.io.sstable.SSTableReaderTest.testPersistentStatistics(SSTableReaderTest.java:215)
> Caused by: java.lang.RuntimeException: Failed to rename
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> to
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:385)
> at org.apache.cassandra.io.util.File.move(File.java:227)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:704)
> at
> org.apache.cassandra.io.util.FileUtils.renameWithConfirm(FileUtils.java:698)
> at
> org.apache.cassandra.io.sstable.format.SSTableWriter.rename(SSTableWriter.java:337)
> at
> org.apache.cassandra.io.sstable.format.SSTableReader.moveAndOpenSSTable(SSTableReader.java:2339)
> at
> org.apache.cassandra.db.SSTableImporter.importNewSSTables(SSTableImporter.java:139)
> Caused by: java.nio.file.NoSuchFileException:
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-9-big-Digest.crc32
> ->
> /tmp/cassandra/build/test/cassandra/data/SSTableReaderTest/Standard1-da581e50380611ecaad41173773221f9/nb-13-big-Digest.crc32
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:396)
> at
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at
> org.apache.cassandra.io.util.PathUtils.atomicMoveWithFallback(PathUtils.java:396)
> at org.apache.cassandra.io.util.PathUtils.rename(PathUtils.java:377)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17240) CEP-19: Trie memtable implementation
[ https://issues.apache.org/jira/browse/CASSANDRA-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Branimir Lambov updated CASSANDRA-17240: Attachment: throughput_SG.png throughput_apache.png > CEP-19: Trie memtable implementation > > > Key: CASSANDRA-17240 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17240 > Project: Cassandra > Issue Type: Improvement > Components: Local/Memtable >Reporter: Branimir Lambov >Priority: Normal > Attachments: SkipListMemtable-OSS.png, TrieMemtable-OSS.png, > density_test_with_sharding.html.gz, throughput_SG.png, throughput_apache.png > > > Trie-based memtable implementation as described in CEP-19, built on top of > CASSANDRA-17034 and CASSANDRA-6936. > The implementation is available in this > [branch|https://github.com/blambov/cassandra/tree/CASSANDRA-17240]. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16262) 4.0 Quality: Coordination & Replication Fuzz Testing
[ https://issues.apache.org/jira/browse/CASSANDRA-16262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488192#comment-17488192 ] Alex Petrov commented on CASSANDRA-16262: - [~maedhroz] [~aratnofsky] i've pushed a new version and published harry release for vote. Would you be able to take another look? > 4.0 Quality: Coordination & Replication Fuzz Testing > > > Key: CASSANDRA-16262 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16262 > Project: Cassandra > Issue Type: Task > Components: Test/fuzz >Reporter: Caleb Rackliffe >Assignee: Alex Petrov >Priority: Normal > Labels: pull-request-available > Fix For: 4.x > > Time Spent: 9.5h > Remaining Estimate: 0h > > CASSANDRA-16180, CASSANDRA-16181, and CASSANDRA-15977 have largely focused on > auditing the existing tests around coordination, replication, and > read-repair, respectively. We've expanded existing test cases, added coverage > around components that we've refactored along the way, and added in-JVM dtest > upgrade tests where possible. > What remains is verifying the distributed read and write paths in the face of > common operational events, namely node restarts, bootstrapping, decommission, > and cleanup. If we can find a way to simulate these events, > [Harry|https://github.com/apache/cassandra-harry] seems like a good candidate > to host the verification logic itself. > To keep things simple initially, I would propose that we start by testing > simple read-only and write-only workloads (the former without read repair). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17342) Performance problem for node restart with incremental range repairs
[ https://issues.apache.org/jira/browse/CASSANDRA-17342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488183#comment-17488183 ] Paul Chandler commented on CASSANDRA-17342: --- Hi Marcus, Yes those changes look good. I am not sure where I my email address goes for the Author: field ? > Performance problem for node restart with incremental range repairs > --- > > Key: CASSANDRA-17342 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17342 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Repair >Reporter: Paul Chandler >Assignee: Paul Chandler >Priority: Normal > Fix For: 4.0.x > > Attachments: BulkRepairStateTest.java, > IncrementalRepairStartupTest.java, LocalSessions.java, RepairedState.java > > > There is a performance problem when restarting cassandra for clusters doing > incremental repairs with range repairs. > We have clusters with 16 vnodes per node, and are splitting each vnode into > 100 ranges, this causes a node to take over 30 minutes to process the data > stored in the system.repairs table before the node can restart. Even when we > reduce this to 10 ranges per vnode this still takes 2 minutes to process. The > cluster has 22 keyspaces and a rf of 3, this creates around 8100 records in > the system.repairs table. > > The problem seems to occur in the > org.apache.cassandra.repair.consistent.RepairState class where the add method > re processes the complete list, including sorting, every time a new Range is > added. This leads is an exponential growth in processing time, this is > demonstrated in the attached unit test. > > I have created a change, that collects the data read in from the > system.repairs table, in the > org.apache.cassandra.repair.consistent.LocalSessions class, before processing > it as a group at the end, this reduces the processing time to a couple of > seconds even for the 100 range version. > > This is my first attempt at changing the cassandra code, so I am in need of a > mentor to help me with the process, and validate what I have done. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17240) CEP-19: Trie memtable implementation
[ https://issues.apache.org/jira/browse/CASSANDRA-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Branimir Lambov updated CASSANDRA-17240: Attachment: density_test_with_sharding.html.gz > CEP-19: Trie memtable implementation > > > Key: CASSANDRA-17240 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17240 > Project: Cassandra > Issue Type: Improvement > Components: Local/Memtable >Reporter: Branimir Lambov >Priority: Normal > Attachments: SkipListMemtable-OSS.png, TrieMemtable-OSS.png, > density_test_with_sharding.html.gz > > > Trie-based memtable implementation as described in CEP-19, built on top of > CASSANDRA-17034 and CASSANDRA-6936. > The implementation is available in this > [branch|https://github.com/blambov/cassandra/tree/CASSANDRA-17240]. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17240) CEP-19: Trie memtable implementation
[ https://issues.apache.org/jira/browse/CASSANDRA-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Branimir Lambov updated CASSANDRA-17240: Attachment: TrieMemtable-OSS.png > CEP-19: Trie memtable implementation > > > Key: CASSANDRA-17240 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17240 > Project: Cassandra > Issue Type: Improvement > Components: Local/Memtable >Reporter: Branimir Lambov >Priority: Normal > Attachments: SkipListMemtable-OSS.png, TrieMemtable-OSS.png > > > Trie-based memtable implementation as described in CEP-19, built on top of > CASSANDRA-17034 and CASSANDRA-6936. > The implementation is available in this > [branch|https://github.com/blambov/cassandra/tree/CASSANDRA-17240]. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17240) CEP-19: Trie memtable implementation
[ https://issues.apache.org/jira/browse/CASSANDRA-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Branimir Lambov updated CASSANDRA-17240: Attachment: SkipListMemtable-OSS.png > CEP-19: Trie memtable implementation > > > Key: CASSANDRA-17240 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17240 > Project: Cassandra > Issue Type: Improvement > Components: Local/Memtable >Reporter: Branimir Lambov >Priority: Normal > Attachments: SkipListMemtable-OSS.png, TrieMemtable-OSS.png > > > Trie-based memtable implementation as described in CEP-19, built on top of > CASSANDRA-17034 and CASSANDRA-6936. > The implementation is available in this > [branch|https://github.com/blambov/cassandra/tree/CASSANDRA-17240]. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] branch release updated: [maven-release-plugin] prepare for next development iteration
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git The following commit(s) were added to refs/heads/release by this push: new 5570c25 [maven-release-plugin] prepare for next development iteration 5570c25 is described below commit 5570c254df4fd6495c864f4021970ae005a62ce5 Author: Alex Petrov AuthorDate: Mon Feb 7 15:40:24 2022 +0100 [maven-release-plugin] prepare for next development iteration --- harry-core/pom.xml | 2 +- harry-integration-external/pom.xml | 2 +- harry-integration/pom.xml | 2 +- pom.xml| 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/harry-core/pom.xml b/harry-core/pom.xml index 5bf7263..153251c 100755 --- a/harry-core/pom.xml +++ b/harry-core/pom.xml @@ -25,7 +25,7 @@ org.apache.cassandra harry-parent -0.0.1 +0.0.2-SNAPSHOT harry-core diff --git a/harry-integration-external/pom.xml b/harry-integration-external/pom.xml index 0dce783..9592b43 100755 --- a/harry-integration-external/pom.xml +++ b/harry-integration-external/pom.xml @@ -24,7 +24,7 @@ org.apache.cassandra -0.0.1 +0.0.2-SNAPSHOT harry-parent diff --git a/harry-integration/pom.xml b/harry-integration/pom.xml index 98a7ea5..0531e2d 100755 --- a/harry-integration/pom.xml +++ b/harry-integration/pom.xml @@ -24,7 +24,7 @@ org.apache.cassandra -0.0.1 +0.0.2-SNAPSHOT harry-parent diff --git a/pom.xml b/pom.xml index 58b6c54..5a34eac 100755 --- a/pom.xml +++ b/pom.xml @@ -38,7 +38,7 @@ org.apache.cassandra harry-parent -0.0.1 +0.0.2-SNAPSHOT Harry - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] annotated tag 0.0.1 created (now 521bbb6)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.1 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. at 521bbb6 (tag) tagging 40fb37ec8a4f08dc6a258a50cbdeab92e2894266 (commit) by Alex Petrov on Mon Feb 7 15:40:21 2022 +0100 - Log - [maven-release-plugin] copy for tag 0.0.1 --- 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
[cassandra-harry] branch release created (now 40fb37e)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. at 40fb37e [maven-release-plugin] prepare release 0.0.1 This branch includes the following new commits: new 66e93a3 Prepare for release. new 40fb37e [maven-release-plugin] prepare release 0.0.1 The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] 01/02: Prepare for release.
This is an automated email from the ASF dual-hosted git repository.
ifesdjeen pushed a commit to branch release
in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git
commit 66e93a37dc9d7c0a48ddd86beceb734aca796abd
Author: Alex Petrov
AuthorDate: Mon Feb 7 14:05:22 2022 +0100
Prepare for release.
---
README.md| 39
harry-core/src/harry/generators/PCGFastPure.java | 2 +-
pom.xml | 3 +-
3 files changed, 42 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 5c45c09..9c6b7bf 100644
--- a/README.md
+++ b/README.md
@@ -730,6 +730,45 @@ This list of improvements is incomplete, and should only
give the reader a rough
idea about the state of the project. Main goal for the initial release was to
make it
useful, now we can make it fast and feature-complete!
+# How to cut a release
+
+## Publishing snapshot
+
+Make sure `~/.m2/settings.xml` contains records for the following:
+
+```
+
+ apache.snapshots.https
+ username
+ password
+
+
+ apache.releases.https
+ username
+ password
+
+```
+
+```
+mvn versions:set -DnewVersion=0.0.2-`git rev-parse --short HEAD`-SNAPSHOT
+mvn deploy
+```
+
+# Releasing
+
+1. Prepare the release:
+
+```
+mvn release:clean
+CURRENT=0.0.CURRENT
+NEXT_DEV=0.0.NEXT
+mvn -DreleaseVersion=$CURRENT -Dtag=$CURRENT
-DdevelopmentVersion=$NEXT_DEV-SNAPSHOT release:prepare
+mvn release:perform
+```
+
+2. Close staging repository: https://repository.apache.org/#stagingRepositories
+3. Issue a vote on developers mailing list. Add your GPG key signature,
release SHA, and staged artifacts to release information.
+
# Contributors
* [Alex Petrov](https://github.com/ifesdjeen)
diff --git a/harry-core/src/harry/generators/PCGFastPure.java
b/harry-core/src/harry/generators/PCGFastPure.java
index 9e438dc..caed276 100644
--- a/harry-core/src/harry/generators/PCGFastPure.java
+++ b/harry-core/src/harry/generators/PCGFastPure.java
@@ -25,7 +25,7 @@ package harry.generators;
* https://github.com/imneme/pcg-c
* https://github.com/imneme/pcg-cpp
*
- * Original library developed by Melissa O'Neill
+ * Original library developed by Melissa O'Neill (one...@pcg-random.org)
*/
public class PCGFastPure
{
diff --git a/pom.xml b/pom.xml
index 276a670..fab3634 100755
--- a/pom.xml
+++ b/pom.xml
@@ -50,9 +50,10 @@
+true
1.8
0.0.1-SNAPSHOT
-4.1-58515c2de6
+4.0.1-1a05fcf52b
2.11.3
0.0.7
1.11.3
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] 02/02: [maven-release-plugin] prepare release 0.0.1
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git commit 40fb37ec8a4f08dc6a258a50cbdeab92e2894266 Author: Alex Petrov AuthorDate: Mon Feb 7 15:40:17 2022 +0100 [maven-release-plugin] prepare release 0.0.1 --- harry-core/pom.xml | 5 ++--- harry-integration-external/pom.xml | 5 ++--- harry-integration/pom.xml | 5 ++--- pom.xml| 5 ++--- 4 files changed, 8 insertions(+), 12 deletions(-) diff --git a/harry-core/pom.xml b/harry-core/pom.xml index d313e7a..5bf7263 100755 --- a/harry-core/pom.xml +++ b/harry-core/pom.xml @@ -17,8 +17,7 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 jar @@ -26,7 +25,7 @@ org.apache.cassandra harry-parent -0.0.1-SNAPSHOT +0.0.1 harry-core diff --git a/harry-integration-external/pom.xml b/harry-integration-external/pom.xml index 0b49f6d..0dce783 100755 --- a/harry-integration-external/pom.xml +++ b/harry-integration-external/pom.xml @@ -17,15 +17,14 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 jar org.apache.cassandra -0.0.1-SNAPSHOT +0.0.1 harry-parent diff --git a/harry-integration/pom.xml b/harry-integration/pom.xml index 0b2d131..98a7ea5 100755 --- a/harry-integration/pom.xml +++ b/harry-integration/pom.xml @@ -17,15 +17,14 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 jar org.apache.cassandra -0.0.1-SNAPSHOT +0.0.1 harry-parent diff --git a/pom.xml b/pom.xml index fab3634..58b6c54 100755 --- a/pom.xml +++ b/pom.xml @@ -17,8 +17,7 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> org.apache @@ -39,7 +38,7 @@ org.apache.cassandra harry-parent -0.0.1-SNAPSHOT +0.0.1 Harry - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] branch release deleted (was 89c7225)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. was 89c7225 [maven-release-plugin] prepare release 0.0.1 This change permanently discards the following revisions: discard 89c7225 [maven-release-plugin] prepare release 0.0.1 discard 66e93a3 Prepare for release. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] annotated tag 0.0.1 deleted (was 3272570)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.1 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. *** WARNING: tag 0.0.1 was deleted! *** tag was 3272570 The revisions that were on this annotated 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
[cassandra-harry] annotated tag 0.0.1 created (now 3272570)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.1 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. at 3272570 (tag) tagging 89c722500fba51bd02166fa5cdd70210b402cae5 (commit) by Alex Petrov on Mon Feb 7 15:38:34 2022 +0100 - Log - [maven-release-plugin] copy for tag 0.0.1 --- 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
[cassandra-harry] 02/02: [maven-release-plugin] prepare release 0.0.1
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git commit 89c722500fba51bd02166fa5cdd70210b402cae5 Author: Alex Petrov AuthorDate: Mon Feb 7 15:38:30 2022 +0100 [maven-release-plugin] prepare release 0.0.1 --- harry-core/pom.xml | 5 ++--- harry-integration-external/pom.xml | 5 ++--- harry-integration/pom.xml | 5 ++--- pom.xml| 5 ++--- 4 files changed, 8 insertions(+), 12 deletions(-) diff --git a/harry-core/pom.xml b/harry-core/pom.xml index d313e7a..5bf7263 100755 --- a/harry-core/pom.xml +++ b/harry-core/pom.xml @@ -17,8 +17,7 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 jar @@ -26,7 +25,7 @@ org.apache.cassandra harry-parent -0.0.1-SNAPSHOT +0.0.1 harry-core diff --git a/harry-integration-external/pom.xml b/harry-integration-external/pom.xml index 0b49f6d..0dce783 100755 --- a/harry-integration-external/pom.xml +++ b/harry-integration-external/pom.xml @@ -17,15 +17,14 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 jar org.apache.cassandra -0.0.1-SNAPSHOT +0.0.1 harry-parent diff --git a/harry-integration/pom.xml b/harry-integration/pom.xml index 0b2d131..98a7ea5 100755 --- a/harry-integration/pom.xml +++ b/harry-integration/pom.xml @@ -17,15 +17,14 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 jar org.apache.cassandra -0.0.1-SNAPSHOT +0.0.1 harry-parent diff --git a/pom.xml b/pom.xml index fab3634..58b6c54 100755 --- a/pom.xml +++ b/pom.xml @@ -17,8 +17,7 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> org.apache @@ -39,7 +38,7 @@ org.apache.cassandra harry-parent -0.0.1-SNAPSHOT +0.0.1 Harry - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] 01/02: Prepare for release.
This is an automated email from the ASF dual-hosted git repository.
ifesdjeen pushed a commit to branch release
in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git
commit 66e93a37dc9d7c0a48ddd86beceb734aca796abd
Author: Alex Petrov
AuthorDate: Mon Feb 7 14:05:22 2022 +0100
Prepare for release.
---
README.md| 39
harry-core/src/harry/generators/PCGFastPure.java | 2 +-
pom.xml | 3 +-
3 files changed, 42 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 5c45c09..9c6b7bf 100644
--- a/README.md
+++ b/README.md
@@ -730,6 +730,45 @@ This list of improvements is incomplete, and should only
give the reader a rough
idea about the state of the project. Main goal for the initial release was to
make it
useful, now we can make it fast and feature-complete!
+# How to cut a release
+
+## Publishing snapshot
+
+Make sure `~/.m2/settings.xml` contains records for the following:
+
+```
+
+ apache.snapshots.https
+ username
+ password
+
+
+ apache.releases.https
+ username
+ password
+
+```
+
+```
+mvn versions:set -DnewVersion=0.0.2-`git rev-parse --short HEAD`-SNAPSHOT
+mvn deploy
+```
+
+# Releasing
+
+1. Prepare the release:
+
+```
+mvn release:clean
+CURRENT=0.0.CURRENT
+NEXT_DEV=0.0.NEXT
+mvn -DreleaseVersion=$CURRENT -Dtag=$CURRENT
-DdevelopmentVersion=$NEXT_DEV-SNAPSHOT release:prepare
+mvn release:perform
+```
+
+2. Close staging repository: https://repository.apache.org/#stagingRepositories
+3. Issue a vote on developers mailing list. Add your GPG key signature,
release SHA, and staged artifacts to release information.
+
# Contributors
* [Alex Petrov](https://github.com/ifesdjeen)
diff --git a/harry-core/src/harry/generators/PCGFastPure.java
b/harry-core/src/harry/generators/PCGFastPure.java
index 9e438dc..caed276 100644
--- a/harry-core/src/harry/generators/PCGFastPure.java
+++ b/harry-core/src/harry/generators/PCGFastPure.java
@@ -25,7 +25,7 @@ package harry.generators;
* https://github.com/imneme/pcg-c
* https://github.com/imneme/pcg-cpp
*
- * Original library developed by Melissa O'Neill
+ * Original library developed by Melissa O'Neill (one...@pcg-random.org)
*/
public class PCGFastPure
{
diff --git a/pom.xml b/pom.xml
index 276a670..fab3634 100755
--- a/pom.xml
+++ b/pom.xml
@@ -50,9 +50,10 @@
+true
1.8
0.0.1-SNAPSHOT
-4.1-58515c2de6
+4.0.1-1a05fcf52b
2.11.3
0.0.7
1.11.3
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] branch release created (now 89c7225)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. at 89c7225 [maven-release-plugin] prepare release 0.0.1 This branch includes the following new commits: new 66e93a3 Prepare for release. new 89c7225 [maven-release-plugin] prepare release 0.0.1 The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] annotated tag 0.0.1 deleted (was 836e3cc)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.1 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. *** WARNING: tag 0.0.1 was deleted! *** tag was 836e3cc This change permanently discards the following revisions: discard 66e93a3 Prepare for release. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] branch release deleted (was cc4a178)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. was cc4a178 [maven-release-plugin] prepare for next development iteration This change permanently discards the following revisions: discard cc4a178 [maven-release-plugin] prepare for next development iteration - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] annotated tag 0.0.1 created (now 836e3cc)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.1 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. at 836e3cc (tag) tagging 66e93a37dc9d7c0a48ddd86beceb734aca796abd (commit) by Alex Petrov on Mon Feb 7 15:32:13 2022 +0100 - Log - [maven-release-plugin] copy for tag 0.0.1 --- This annotated tag includes the following new commits: new 66e93a3 Prepare for release. 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. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] 01/01: [maven-release-plugin] prepare for next development iteration
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a commit to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git commit cc4a178b806cdd7da9840a5519f81c31565894fe Author: Alex Petrov AuthorDate: Mon Feb 7 15:32:16 2022 +0100 [maven-release-plugin] prepare for next development iteration --- harry-core/pom.xml | 5 ++--- harry-integration-external/pom.xml | 5 ++--- harry-integration/pom.xml | 5 ++--- pom.xml| 5 ++--- 4 files changed, 8 insertions(+), 12 deletions(-) diff --git a/harry-core/pom.xml b/harry-core/pom.xml index d313e7a..a741862 100755 --- a/harry-core/pom.xml +++ b/harry-core/pom.xml @@ -17,8 +17,7 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 jar @@ -26,7 +25,7 @@ org.apache.cassandra harry-parent -0.0.1-SNAPSHOT +-SNAPSHOT harry-core diff --git a/harry-integration-external/pom.xml b/harry-integration-external/pom.xml index 0b49f6d..9a653e8 100755 --- a/harry-integration-external/pom.xml +++ b/harry-integration-external/pom.xml @@ -17,15 +17,14 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 jar org.apache.cassandra -0.0.1-SNAPSHOT +-SNAPSHOT harry-parent diff --git a/harry-integration/pom.xml b/harry-integration/pom.xml index 0b2d131..9ec3b14 100755 --- a/harry-integration/pom.xml +++ b/harry-integration/pom.xml @@ -17,15 +17,14 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> 4.0.0 jar org.apache.cassandra -0.0.1-SNAPSHOT +-SNAPSHOT harry-parent diff --git a/pom.xml b/pom.xml index fab3634..a672274 100755 --- a/pom.xml +++ b/pom.xml @@ -17,8 +17,7 @@ ~ limitations under the License. --> -http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> org.apache @@ -39,7 +38,7 @@ org.apache.cassandra harry-parent -0.0.1-SNAPSHOT +-SNAPSHOT Harry - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] branch release created (now cc4a178)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. at cc4a178 [maven-release-plugin] prepare for next development iteration This branch includes the following new commits: new cc4a178 [maven-release-plugin] prepare for next development iteration 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. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] 01/01: Prepare for release.
This is an automated email from the ASF dual-hosted git repository.
ifesdjeen pushed a commit to annotated tag 0.0.1
in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git
commit 66e93a37dc9d7c0a48ddd86beceb734aca796abd
Author: Alex Petrov
AuthorDate: Mon Feb 7 14:05:22 2022 +0100
Prepare for release.
---
README.md| 39
harry-core/src/harry/generators/PCGFastPure.java | 2 +-
pom.xml | 3 +-
3 files changed, 42 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 5c45c09..9c6b7bf 100644
--- a/README.md
+++ b/README.md
@@ -730,6 +730,45 @@ This list of improvements is incomplete, and should only
give the reader a rough
idea about the state of the project. Main goal for the initial release was to
make it
useful, now we can make it fast and feature-complete!
+# How to cut a release
+
+## Publishing snapshot
+
+Make sure `~/.m2/settings.xml` contains records for the following:
+
+```
+
+ apache.snapshots.https
+ username
+ password
+
+
+ apache.releases.https
+ username
+ password
+
+```
+
+```
+mvn versions:set -DnewVersion=0.0.2-`git rev-parse --short HEAD`-SNAPSHOT
+mvn deploy
+```
+
+# Releasing
+
+1. Prepare the release:
+
+```
+mvn release:clean
+CURRENT=0.0.CURRENT
+NEXT_DEV=0.0.NEXT
+mvn -DreleaseVersion=$CURRENT -Dtag=$CURRENT
-DdevelopmentVersion=$NEXT_DEV-SNAPSHOT release:prepare
+mvn release:perform
+```
+
+2. Close staging repository: https://repository.apache.org/#stagingRepositories
+3. Issue a vote on developers mailing list. Add your GPG key signature,
release SHA, and staged artifacts to release information.
+
# Contributors
* [Alex Petrov](https://github.com/ifesdjeen)
diff --git a/harry-core/src/harry/generators/PCGFastPure.java
b/harry-core/src/harry/generators/PCGFastPure.java
index 9e438dc..caed276 100644
--- a/harry-core/src/harry/generators/PCGFastPure.java
+++ b/harry-core/src/harry/generators/PCGFastPure.java
@@ -25,7 +25,7 @@ package harry.generators;
* https://github.com/imneme/pcg-c
* https://github.com/imneme/pcg-cpp
*
- * Original library developed by Melissa O'Neill
+ * Original library developed by Melissa O'Neill (one...@pcg-random.org)
*/
public class PCGFastPure
{
diff --git a/pom.xml b/pom.xml
index 276a670..fab3634 100755
--- a/pom.xml
+++ b/pom.xml
@@ -50,9 +50,10 @@
+true
1.8
0.0.1-SNAPSHOT
-4.1-58515c2de6
+4.0.1-1a05fcf52b
2.11.3
0.0.7
1.11.3
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] branch release deleted (was 7046288)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to branch release in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. was 7046288 [maven-release-plugin] prepare for next development iteration This change permanently discards the following revisions: discard 7046288 [maven-release-plugin] prepare for next development iteration discard 12e3f15 Prepare for release. - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-harry] annotated tag 0.0.1 deleted (was 4acbe66)
This is an automated email from the ASF dual-hosted git repository. ifesdjeen pushed a change to annotated tag 0.0.1 in repository https://gitbox.apache.org/repos/asf/cassandra-harry.git. *** WARNING: tag 0.0.1 was deleted! *** tag was 4acbe66 The revisions that were on this annotated 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
