[jira] [Commented] (CASSANDRA-17207) The process cannot access the file because it is being used by another process.
[ https://issues.apache.org/jira/browse/CASSANDRA-17207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468365#comment-17468365 ] shravansingh commented on CASSANDRA-17207: -- Hi [~jmckenzie], C* folder is already excluded in AV, still we are getting this. we are using Cassandra version 3.0.14, and it we are using it quite a long time(It is not recently installed). > The process cannot access the file because it is being used by another > process. > --- > > Key: CASSANDRA-17207 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17207 > Project: Cassandra > Issue Type: Bug >Reporter: shravansingh >Priority: Normal > > > ERROR [COMMIT-LOG-ALLOCATOR] 2021-12-11 17:02:00,989 > JVMStabilityInspector.java:140 - JVM state determined to be unstable. > Exiting forcefully due to: > org.apache.cassandra.io.FSWriteError: java.nio.file.FileSystemException: > \commitlog\CommitLog-6-1636406548826.log: The process cannot access > the file because it is being used by another process. > > at > org.apache.cassandra.io.util.FileUtils.deleteWithConfirm(FileUtils.java:138) > ~[apache-cassandra-3.0.14.jar:3.0.14] > at > org.apache.cassandra.io.util.FileUtils.deleteWithConfirm(FileUtils.java:155) > ~[apache-cassandra-3.0.14.jar:3.0.14] > at > org.apache.cassandra.db.commitlog.CommitLogSegment.discard(CommitLogSegment.java:342) > ~[apache-cassandra-3.0.14.jar:3.0.14] > at > org.apache.cassandra.db.commitlog.CommitLogSegmentManager$2.run(CommitLogSegmentManager.java:379) > ~[apache-cassandra-3.0.14.jar:3.0.14] > at > org.apache.cassandra.db.commitlog.CommitLogSegmentManager$1.runMayThrow(CommitLogSegmentManager.java:156) > ~[apache-cassandra-3.0.14.jar:3.0.14] > at > org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28) > [apache-cassandra-3.0.14.jar:3.0.14] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:79) > [apache-cassandra-3.0.14.jar:3.0.14] > at java.lang.Thread.run(Unknown Source) ~[na:1.8.0_301] > Caused by: java.nio.file.FileSystemException: > \commitlog\CommitLog-6-1636406548826.log: The process cannot access > the file because it is being used by another process. > > at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) > ~[na:1.8.0_301] > at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) > ~[na:1.8.0_301] > at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) > ~[na:1.8.0_301] > at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) > ~[na:1.8.0_301] > at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) > ~[na:1.8.0_301] > at java.nio.file.Files.delete(Unknown Source) ~[na:1.8.0_301] > at > org.apache.cassandra.io.util.FileUtils.deleteWithConfirm(FileUtils.java:132) > ~[apache-cassandra-3.0.14.jar:3.0.14] > ... 7 common frames omitted > It seems similar to https://issues.apache.org/jira/browse/CASSANDRA-8390, but > it was resolved in 2.2 beta, though I am facing this in version 3.0.14 > I am running this on windows server OS and in cassandra.yaml, > disk_access_mode is set to standard -- 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-17182) Add info how to test with your own CCM branch
[
https://issues.apache.org/jira/browse/CASSANDRA-17182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova reassigned CASSANDRA-17182:
---
Assignee: Ekaterina Dimitrova
> Add info how to test with your own CCM branch
> -
>
> Key: CASSANDRA-17182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17182
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Low
>
> In CASSANDRA-16688 we solved an issue with ccm and retagging.
> It required to remove the -e from the beginning of [this
> row|https://github.com/apache/cassandra-dtest/blob/trunk/requirements.txt#L9]
> But now if someone wants to test with their own ccm branch, they need to add
> back the -e during testing so that pip3 updates with their branch. Without
> it, it doesn't update.
> *Example:*
> {code:java}
> git+https://github.com/riptano/ccm.git@cassandra-test#egg=ccm
> {code}
> This is important information and I think we need to add it to at least:
> - our Testing page where dtest runs are mentioned on the website
> - Add a comment in requirements.txt in the dtest repo
> We can also update the README files of CCM and DTests but then if something
> changes we will need to update this info in 4 places which doesn't seem
> efficient to me.
--
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-17234) Workaround the need to use ant script task in build.xml
[ https://issues.apache.org/jira/browse/CASSANDRA-17234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17234: Description: In order to use ant script task in Java 17 we would need to introduce Graal js and other dependencies as Nashorn was removed. My plan is to try to workaround it by creating my own custom ant tasks and not introducing new dependencies to the project. was: In order to use ant script task in Java 17 we would need to introduce Graal js and other dependencies as Nashorn was removed. My plan is to try to workaround it by creating my own custom ant task and not introducing new dependencies to the project. > Workaround the need to use ant script task in build.xml > --- > > Key: CASSANDRA-17234 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17234 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > In order to use ant script task in Java 17 we would need to introduce Graal > js and other dependencies as Nashorn was removed. > My plan is to try to workaround it by creating my own custom ant tasks and > not introducing new dependencies to the project. -- 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-17234) Workaround the need to use ant script task in build.xml
[ https://issues.apache.org/jira/browse/CASSANDRA-17234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17234: Summary: Workaround the need to use ant script task in build.xml (was: Workaround the need of ant script task in build.xml) > Workaround the need to use ant script task in build.xml > --- > > Key: CASSANDRA-17234 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17234 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > In order to use ant script task in Java 17 we would need to introduce Graal > js and other dependencies as Nashorn was removed. > My plan is to try to workaround it by creating my own custom ant task and not > introducing new dependencies to the project. -- 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-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468309#comment-17468309 ] Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 1/4/22, 1:47 AM: -- I am all in for that, I will open a separate task and discussion thread to reach consensus around the scripted UDFs. Also, I just opened a task to get rid of the ant script tasks (CASSANDRA-17234) and as a consequence not to have to introduce more dependencies; as it was required in order to keep on using the ant script tasks after Java 17 migration. was (Author: e.dimitrova): I am all in for that, I will open a separate task and discussion thread to reach consensus around the scripted UDFs. Also, I just opened a task to get rid of the ant script tasks (CASSANDRA-17234) and as a consequence not to introduce more dependencies as required in order to keep on using the ant script tasks. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- 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-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468309#comment-17468309 ] Ekaterina Dimitrova commented on CASSANDRA-16895: - I am all in for that, I will open a separate task and discussion thread to reach consensus around the scripted UDFs. Also, I just opened a task to get rid of the ant script tasks (CASSANDRA-17234) and as a consequence not to introduce more dependencies as required in order to keep on using the ant script tasks. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- 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-17234) Workaround the need of ant script task in build.xml
[ https://issues.apache.org/jira/browse/CASSANDRA-17234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17234: Change Category: Operability Complexity: Normal Component/s: Build Status: Open (was: Triage Needed) > Workaround the need of ant script task in build.xml > --- > > Key: CASSANDRA-17234 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17234 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > In order to use ant script task in Java 17 we would need to introduce Graal > js and other dependencies as Nashorn was removed. > My plan is to try to workaround it by creating my own custom ant task and not > introducing new dependencies to the project. -- 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-17234) Workaround the need of ant script task in build.xml
[ https://issues.apache.org/jira/browse/CASSANDRA-17234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17234: Fix Version/s: 4.x > Workaround the need of ant script task in build.xml > --- > > Key: CASSANDRA-17234 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17234 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > In order to use ant script task in Java 17 we would need to introduce Graal > js and other dependencies as Nashorn was removed. > My plan is to try to workaround it by creating my own custom ant task and not > introducing new dependencies to the project. -- 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-17234) Workaround the need of ant script task in build.xml
Ekaterina Dimitrova created CASSANDRA-17234: --- Summary: Workaround the need of ant script task in build.xml Key: CASSANDRA-17234 URL: https://issues.apache.org/jira/browse/CASSANDRA-17234 Project: Cassandra Issue Type: Task Reporter: Ekaterina Dimitrova Assignee: Ekaterina Dimitrova In order to use ant script task in Java 17 we would need to introduce Graal js and other dependencies as Nashorn was removed. My plan is to try to workaround it by creating my own custom ant task and not introducing new dependencies to the project. -- 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-17218) Update ant
[ https://issues.apache.org/jira/browse/CASSANDRA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17218: Fix Version/s: 4.0.2 4.1 (was: 4.x) (was: 4.0.x) Source Control Link: https://github.com/apache/cassandra/commit/3ceaed125c3a01cfd0d318e6378ec94b2d84c9cc Resolution: Fixed Status: Resolved (was: Ready to Commit) > Update ant > -- > > Key: CASSANDRA-17218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17218 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.2, 4.1 > > -- 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-17218) Update ant
[ https://issues.apache.org/jira/browse/CASSANDRA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468303#comment-17468303 ] Ekaterina Dimitrova commented on CASSANDRA-17218: - Committed here: To https://github.com/apache/cassandra.git c420d754d8..3ceaed125c cassandra-4.0 -> cassandra-4.0 9b291f18ab..b83d722b99 trunk -> trunk > Update ant > -- > > Key: CASSANDRA-17218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17218 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.x > > -- 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 (c420d75 -> 3ceaed1)
This is an automated email from the ASF dual-hosted git repository. edimitrova pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from c420d75 CASSANDRA-16308: Add droppable tombstone metrics to nodetool tablestats add 3ceaed1 Update ant-junit to version 1.10.12 patch by Ekaterina Dimitrova; reviewed by Michael Semb Wever for CASSANDRA-17218 No new revisions were added by this update. Summary of changes: CHANGES.txt | 1 + build.xml | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0' into trunk
This is an automated email from the ASF dual-hosted git repository. edimitrova pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit b83d722b99de79d131f58512564b901b11907182 Merge: 9b291f1 3ceaed1 Author: Ekaterina Dimitrova AuthorDate: Mon Jan 3 20:33:19 2022 -0500 Merge branch 'cassandra-4.0' into trunk CHANGES.txt | 1 + build.xml | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --cc CHANGES.txt index eb773af,0fd51ec..983d9b6 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,78 -1,5 +1,79 @@@ -4.0.2 +4.1 + * Added startup check for read_ahead_kb setting (CASSANDRA-16436) + * Avoid unecessary array allocations and initializations when performing query checks (CASSANDRA-17209) + * Add guardrail for list operations that require read before write (CASSANDRA-17154) + * Migrate thresholds for number of keyspaces and tables to guardrails (CASSANDRA-17195) + * Remove self-reference in SSTableTidier (CASSANDRA-17205) + * Add guardrail for query page size (CASSANDRA-17189) + * Allow column_index_size_in_kb to be configurable through nodetool (CASSANDRA-17121) + * Emit a metric for number of local read and write calls + * Add non-blocking mode for CDC writes (CASSANDRA-17001) + * Add guardrails framework (CASSANDRA-17147) + * Harden resource management on SSTable components to prevent future leaks (CASSANDRA-17174) + * Make nodes more resilient to local unrelated files during startup (CASSANDRA-17082) + * repair prepare message would produce a wrong error message if network timeout happened rather than reply wait timeout (CASSANDRA-16992) + * Log queries that fail on timeout or unavailable errors up to once per minute by default (CASSANDRA-17159) + * Refactor normal/preview/IR repair to standardize repair cleanup and error handling of failed RepairJobs (CASSANDRA-17069) + * Log missing peers in StartupClusterConnectivityChecker (CASSANDRA-17130) + * Introduce separate rate limiting settings for entire SSTable streaming (CASSANDRA-17065) + * Implement Virtual Tables for Auth Caches (CASSANDRA-16914) + * Actively update auth cache in the background (CASSANDRA-16957) + * Add unix time conversion functions (CASSANDRA-17029) + * JVMStabilityInspector.forceHeapSpaceOomMaybe should handle all non-heap OOMs rather than only supporting direct only (CASSANDRA-17128) + * Forbid other Future implementations with checkstyle (CASSANDRA-17055) + * commit log was switched from non-daemon to daemon threads, which causes the JVM to exit in some case as no non-daemon threads are active (CASSANDRA-17085) + * Add a Denylist to block reads and writes on specific partition keys (CASSANDRA-12106) + * v4+ protocol did not clean up client warnings, which caused leaking the state (CASSANDRA-17054) + * Remove duplicate toCQLString in ReadCommand (CASSANDRA-17023) + * Ensure hint window is persistent across restarts of a node (CASSANDRA-14309) + * Allow to GRANT or REVOKE multiple permissions in a single statement (CASSANDRA-17030) + * Allow to grant permission for all tables in a keyspace (CASSANDRA-17027) + * Log time spent writing keys during compaction (CASSANDRA-17037) + * Make nodetool compactionstats and sstable_tasks consistent (CASSANDRA-16976) + * Add metrics and logging around index summary redistribution (CASSANDRA-17036) + * Add configuration options for minimum allowable replication factor and default replication factor (CASSANDRA-14557) + * Expose information about stored hints via a nodetool command and a virtual table (CASSANDRA-14795) + * Add broadcast_rpc_address to system.local (CASSANDRA-11181) + * Add support for type casting in WHERE clause components and in the values of INSERT/UPDATE statements (CASSANDRA-14337) + * add credentials file support to CQLSH (CASSANDRA-16983) + * Skip remaining bytes in the Envelope buffer when a ProtocolException is thrown to avoid double decoding (CASSANDRA-17026) + * Allow reverse iteration of resources during permissions checking (CASSANDRA-17016) + * Add feature to verify correct ownership of attached locations on disk at startup (CASSANDRA-16879) + * Make SSLContext creation pluggable/extensible (CASSANDRA-1) + * Add soft/hard limits to local reads to protect against reading too much data in a single query (CASSANDRA-16896) + * Avoid token cache invalidation for removing a non-member node (CASSANDRA-15290) + * Allow configuration of consistency levels on auth operations (CASSANDRA-12988) + * Add number of sstables in a compaction to compactionstats output (CASSANDRA-16844) + * Upgrade Caffeine to 2.9.2 (CASSANDRA-15153) + * Allow DELETE and TRUNCATE to work on Virtual Tables if the implementation allows it (CASSANDRA-16806) + * Include SASI components to snapshots (CASSANDRA-15134) + * Fix missed wait latencies in the output of `nodetool tpstats -F` (CASSANDRA-16938) + * Reduce native transport max frame size to 16MB
[cassandra] branch trunk updated (9b291f1 -> b83d722)
This is an automated email from the ASF dual-hosted git repository. edimitrova pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 9b291f1 Add startup check for read_ahead_kb setting add 3ceaed1 Update ant-junit to version 1.10.12 patch by Ekaterina Dimitrova; reviewed by Michael Semb Wever for CASSANDRA-17218 new b83d722 Merge branch 'cassandra-4.0' into trunk The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt | 1 + build.xml | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15230) Resizing window aborts cqlsh COPY: Interrupted system call
[
https://issues.apache.org/jira/browse/CASSANDRA-15230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468267#comment-17468267
]
František Maša commented on CASSANDRA-15230:
I encountered the same issue on several boxes.
[~weisslj] Is there anything I could do to help get the fixed merged?
> Resizing window aborts cqlsh COPY: Interrupted system call
> --
>
> Key: CASSANDRA-15230
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15230
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Johannes Weißl
>Priority: Normal
> Attachments: 15230-2.1.txt
>
>
> When resizing a terminal window running cqlsh COPY, the Python program aborts
> immediately with:
> {{:1:(4, 'Interrupted system call')}}
> This is very annoying, as COPY commands usually run for a long time, and e.g
> re-attaching to a screen session with a different terminal size aborts the
> command. This bug affects versions 2.1, 2.2, 3.0, 3.x, and trunk.
--
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-17218) Update ant
[ https://issues.apache.org/jira/browse/CASSANDRA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468238#comment-17468238 ] Ekaterina Dimitrova commented on CASSANDRA-17218: - Thanks [~mck] , 4.0 looks good (nothing new) but trunk has a lot of commitlog test failures. I just opened these tickets as I saw the failures also in trunk lately - CASSANDRA-17232 and CASSANDRA-17233. Also, I linked them in butler. I will commit the patch soon. > Update ant > -- > > Key: CASSANDRA-17218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17218 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.x > > -- 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-17218) Update ant
[ https://issues.apache.org/jira/browse/CASSANDRA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17218: Status: Ready to Commit (was: Review In Progress) > Update ant > -- > > Key: CASSANDRA-17218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17218 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.x > > -- 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-17218) Update ant
[ https://issues.apache.org/jira/browse/CASSANDRA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17218: Reviewers: Michael Semb Wever Status: Review In Progress (was: Patch Available) > Update ant > -- > > Key: CASSANDRA-17218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17218 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.x > > -- 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-17218) Update ant
[ https://issues.apache.org/jira/browse/CASSANDRA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17218: Test and Documentation Plan: [4.0|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:17218-4.0?expand=1] | [Jenkins|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1343/] [trunk|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:17218-trunk?expand=1] | [Jenkins|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/] Status: Patch Available (was: In Progress) > Update ant > -- > > Key: CASSANDRA-17218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17218 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.x > > -- 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-17233) Fix org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testNonblockingShouldMaintainSteadyDiskUsage
[ https://issues.apache.org/jira/browse/CASSANDRA-17233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17233: Fix Version/s: 4.x > Fix > org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testNonblockingShouldMaintainSteadyDiskUsage > --- > > Key: CASSANDRA-17233 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17233 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > Fails consistently on trunk: > https://ci-cassandra.apache.org/job/Cassandra-trunk/893/testReport/junit/org.apache.cassandra.db.commitlog/CommitLogSegmentManagerCDCTest/testNonblockingShouldMaintainSteadyDiskUsage/history/ -- 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-17233) Fix org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testNonblockingShouldMaintainSteadyDiskUsage
[ https://issues.apache.org/jira/browse/CASSANDRA-17233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17233: Bug Category: Parent values: Correctness(12982)Level 1 values: Test Failure(12990) Complexity: Normal Component/s: CI Discovered By: Unit Test Severity: Normal Status: Open (was: Triage Needed) > Fix > org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testNonblockingShouldMaintainSteadyDiskUsage > --- > > Key: CASSANDRA-17233 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17233 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > > Fails consistently on trunk: > https://ci-cassandra.apache.org/job/Cassandra-trunk/893/testReport/junit/org.apache.cassandra.db.commitlog/CommitLogSegmentManagerCDCTest/testNonblockingShouldMaintainSteadyDiskUsage/history/ -- 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-17233) Fix org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testNonblockingShouldMaintainSteadyDiskUsage
[ https://issues.apache.org/jira/browse/CASSANDRA-17233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17233: Description: Fails consistently on trunk: https://ci-cassandra.apache.org/job/Cassandra-trunk/893/testReport/junit/org.apache.cassandra.db.commitlog/CommitLogSegmentManagerCDCTest/testNonblockingShouldMaintainSteadyDiskUsage/history/ > Fix > org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testNonblockingShouldMaintainSteadyDiskUsage > --- > > Key: CASSANDRA-17233 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17233 > Project: Cassandra > Issue Type: Bug >Reporter: Ekaterina Dimitrova >Priority: Normal > > Fails consistently on trunk: > https://ci-cassandra.apache.org/job/Cassandra-trunk/893/testReport/junit/org.apache.cassandra.db.commitlog/CommitLogSegmentManagerCDCTest/testNonblockingShouldMaintainSteadyDiskUsage/history/ -- 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-17233) Fix org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testNonblockingShouldMaintainSteadyDiskUsage
Ekaterina Dimitrova created CASSANDRA-17233: --- Summary: Fix org.apache.cassandra.db.commitlog.CommitLogSegmentManagerCDCTest.testNonblockingShouldMaintainSteadyDiskUsage Key: CASSANDRA-17233 URL: https://issues.apache.org/jira/browse/CASSANDRA-17233 Project: Cassandra Issue Type: Bug Reporter: Ekaterina Dimitrova -- 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-17232) org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17232:
Fix Version/s: 4.x
> org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
> ---
>
> Key: CASSANDRA-17232
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17232
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> I saw
> [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3_/]
> and
> [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/881/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3__compression_3/]
> the same assertion failure:
>
> {code:java}
> org.apache.cassandra.db.commitlog.GroupCommitLogTest.replayWithDiscard[3]
> Error Message
> expected:<204> but was:<0>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<204> but was:<0> at
> org.apache.cassandra.db.commitlog.CommitLogTest.replayWithDiscard(CommitLogTest.java:883)
> {code}
>
> Then I find that there are many other tests from GroupCommitLogTest failing
> with No such file found.
> Example:
> https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/
--
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-17232) org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17232:
Bug Category: Parent values: Correctness(12982)Level 1 values: Test
Failure(12990)
Complexity: Normal
Component/s: CI
Discovered By: Unit Test
Severity: Normal
Status: Open (was: Triage Needed)
> org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
> ---
>
> Key: CASSANDRA-17232
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17232
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Priority: Normal
>
> I saw
> [here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3_/]
> and
> [here|https://ci-cassandra.apache.org/job/Cassandra-trunk/881/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3__compression_3/]
> the same assertion failure:
>
> {code:java}
> org.apache.cassandra.db.commitlog.GroupCommitLogTest.replayWithDiscard[3]
> Error Message
> expected:<204> but was:<0>
> Stacktrace
> junit.framework.AssertionFailedError: expected:<204> but was:<0> at
> org.apache.cassandra.db.commitlog.CommitLogTest.replayWithDiscard(CommitLogTest.java:883)
> {code}
>
> Then I find that there are many other tests from GroupCommitLogTest failing
> with No such file found.
> Example:
> https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/
--
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-17232) org.apache.cassandra.db.commitlog.GroupCommitLogTest tests failing on trunk
Ekaterina Dimitrova created CASSANDRA-17232:
---
Summary: org.apache.cassandra.db.commitlog.GroupCommitLogTest
tests failing on trunk
Key: CASSANDRA-17232
URL: https://issues.apache.org/jira/browse/CASSANDRA-17232
Project: Cassandra
Issue Type: Bug
Reporter: Ekaterina Dimitrova
I saw
[here|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3_/]
and
[here|https://ci-cassandra.apache.org/job/Cassandra-trunk/881/testReport/junit/org.apache.cassandra.db.commitlog/GroupCommitLogTest/replayWithDiscard_3__compression_3/]
the same assertion failure:
{code:java}
org.apache.cassandra.db.commitlog.GroupCommitLogTest.replayWithDiscard[3]
Error Message
expected:<204> but was:<0>
Stacktrace
junit.framework.AssertionFailedError: expected:<204> but was:<0> at
org.apache.cassandra.db.commitlog.CommitLogTest.replayWithDiscard(CommitLogTest.java:883)
{code}
Then I find that there are many other tests from GroupCommitLogTest failing
with No such file found.
Example:
https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/
--
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-16436) Add startup check for large read_ahead_kb setting
[
https://issues.apache.org/jira/browse/CASSANDRA-16436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-16436:
Fix Version/s: 4.1
Source Control Link:
https://github.com/apache/cassandra/commit/9b291f18abfc62ab45e725effe75a8ceb9163760
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed to trunk as {{9b291f18abfc62ab45e725effe75a8ceb9163760}} with updated
wording. Thanks all!
> Add startup check for large read_ahead_kb setting
> -
>
> Key: CASSANDRA-16436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16436
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Startup and Shutdown
>Reporter: Paulo Motta
>Assignee: Kanthi Subramanian
>Priority: Normal
> Labels: AdventCalendar2021, lhf
> Fix For: 4.1
>
>
> A well known production tuning recommendation is to dial back the
> {{read_ahead_kb}} Linux setting from the default of 4096 in most
> distributions as this can cause high IO usage and cache churn on
> read-intensive workloads.
> We should add a startup warning to detect when a high {{read_ahead_kb}} is
> used and recommend the user to dial back to a reasonable value, which varies
> according to the workload but a general guideline is to tune this to 8kb.
--
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 trunk updated: Add startup check for read_ahead_kb setting
This is an automated email from the ASF dual-hosted git repository.
paulo pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new 9b291f1 Add startup check for read_ahead_kb setting
9b291f1 is described below
commit 9b291f18abfc62ab45e725effe75a8ceb9163760
Author: Kanthi Subramanian
AuthorDate: Sun Dec 5 13:07:54 2021 -0500
Add startup check for read_ahead_kb setting
Patch by Kanthi Subramanian; Reviewed by Paulo Motta and Brandon Williams
for CASSANDRA-16436
Closes #1354
---
CHANGES.txt| 1 +
.../apache/cassandra/service/StartupChecks.java| 110 +
.../cassandra/service/StartupChecksTest.java | 25 +
3 files changed, 136 insertions(+)
diff --git a/CHANGES.txt b/CHANGES.txt
index f6918d9..eb773af 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
4.1
+ * Added startup check for read_ahead_kb setting (CASSANDRA-16436)
* Avoid unecessary array allocations and initializations when performing
query checks (CASSANDRA-17209)
* Add guardrail for list operations that require read before write
(CASSANDRA-17154)
* Migrate thresholds for number of keyspaces and tables to guardrails
(CASSANDRA-17195)
diff --git a/src/java/org/apache/cassandra/service/StartupChecks.java
b/src/java/org/apache/cassandra/service/StartupChecks.java
index b8fc082..0758dbc 100644
--- a/src/java/org/apache/cassandra/service/StartupChecks.java
+++ b/src/java/org/apache/cassandra/service/StartupChecks.java
@@ -31,7 +31,10 @@ import com.google.common.base.Joiner;
import com.google.common.base.Throwables;
import com.google.common.collect.ImmutableList;
import com.google.common.collect.Iterables;
+import org.apache.commons.lang3.StringUtils;
+
import org.apache.cassandra.io.util.File;
+
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
@@ -98,6 +101,7 @@ public class StartupChecks
checkNativeLibraryInitialization,
initSigarLibrary,
checkMaxMapCount,
+
checkReadAheadKbSetting,
checkDataDirs,
checkSSTablesFormat,
checkSystemKeyspaceState,
@@ -285,6 +289,86 @@ public class StartupChecks
}
};
+public static final StartupCheck checkReadAheadKbSetting = new
StartupCheck()
+{
+// This value is in KB.
+private static final long MAX_RECOMMENDED_READ_AHEAD_KB_SETTING = 128;
+
+/**
+ * Function to get the block device system path(Example: /dev/sda)
from the
+ * data directories defined in cassandra config.(cassandra.yaml)
+ * @param dataDirectories list of data directories from cassandra.yaml
+ * @return Map of block device path and data directory
+ */
+private Map getBlockDevices(String[] dataDirectories) {
+Map blockDevices = new HashMap();
+
+for (String dataDirectory : dataDirectories)
+{
+try
+{
+Path p = Paths.get(dataDirectory);
+FileStore fs = Files.getFileStore(p);
+
+String blockDirectory = fs.name();
+if(StringUtils.isNotEmpty(blockDirectory))
+{
+blockDevices.put(blockDirectory, dataDirectory);
+}
+}
+catch (IOException e)
+{
+logger.warn("IO exception while reading file {}.",
dataDirectory, e);
+}
+}
+return blockDevices;
+}
+
+@Override
+public void execute()
+{
+if (!FBUtilities.isLinux)
+return;
+
+String[] dataDirectories =
DatabaseDescriptor.getRawConfig().data_file_directories;
+Map blockDevices =
getBlockDevices(dataDirectories);
+
+for (Map.Entry entry: blockDevices.entrySet())
+{
+String blockDeviceDirectory = entry.getKey();
+String dataDirectory = entry.getValue();
+try
+{
+Path readAheadKBPath =
StartupChecks.getReadAheadKBPath(blockDeviceDirectory);
+
+if (readAheadKBPath == null ||
Files.notExists(readAheadKBPath))
+{
+logger.debug("No 'read_ahead_kb' setting found for
device {} of data directory {}.",
[jira] [Commented] (CASSANDRA-17218) Update ant
[ https://issues.apache.org/jira/browse/CASSANDRA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468215#comment-17468215 ] Michael Semb Wever commented on CASSANDRA-17218: +1 from me (haven't checked CI results) > Update ant > -- > > Key: CASSANDRA-17218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17218 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.x > > -- 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-16763) Create Cassandra documentation content for new website
[ https://issues.apache.org/jira/browse/CASSANDRA-16763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17467446#comment-17467446 ] Michael Semb Wever edited comment on CASSANDRA-16763 at 1/3/22, 9:17 PM: - Small PRs (to include into the existing patches) on cassandra [trunk|https://github.com/polandll/cassandra/pull/18], [cassandra-4.0|https://github.com/polandll/cassandra/pull/17], and [cassandra-3.11|https://github.com/polandll/cassandra/pull/19] (small fixes for `ant gen-doc`, and restoring CQL.css in 3.11). CI - trunk [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1337/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1337/] - 4.0 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1338/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1338/] - 3.11 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1339/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1339/] (all^ looks good) was (Author: michaelsembwever): Small PRs (to include into the existing patches) on cassandra [trunk|https://github.com/polandll/cassandra/pull/18], [cassandra-4.0|https://github.com/polandll/cassandra/pull/17], and [cassandra-3.11|https://github.com/polandll/cassandra/pull/19] (small fixes for `ant gen-doc`, and restoring CQL.css in 3.11). CI - trunk [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1337/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1337/] - 4.0 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1338/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1338/] - 3.11 [!https://ci-cassandra.apache.org/job/Cassandra-devbranch/1339/badge/icon!|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1339/] > Create Cassandra documentation content for new website > -- > > Key: CASSANDRA-16763 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16763 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > Time Spent: 3h 40m > Remaining Estimate: 0h > > We need create the content (asciidoc) to render the Cassandra documentation > using Antora. This work can commence once the following has happened: > * Website and documentation proof of concept is done - CASSANDRA-16029 > * Website design and concept is done - CASSANDRA-16115 > * Website and document tooling is done - CASSANDRA-16066 > * Website UI components are done - CASSANDRA-16762 -- 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-17231) Upgrade cassandra-driver-core to 4.X
[ https://issues.apache.org/jira/browse/CASSANDRA-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17231: - Bug Category: Parent values: Security(12985) Complexity: Normal Discovered By: User Report Severity: Normal Status: Open (was: Triage Needed) > Upgrade cassandra-driver-core to 4.X > > > Key: CASSANDRA-17231 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17231 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Phyllis Li >Assignee: Phyllis Li >Priority: Normal > Labels: security > Fix For: 4.x > > > The current Cassandra driver version is 3.11.0, which uses a vulnerable > version of jackson-databind. > We may want to switch to the re-branded com.datastax.oss:java-driver-core > 4.13.0. -- 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-15215) VIntCoding should read and write more efficiently
[ https://issues.apache.org/jira/browse/CASSANDRA-15215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie updated CASSANDRA-15215: -- Reviewers: Benedict Elliott Smith > VIntCoding should read and write more efficiently > - > > Key: CASSANDRA-15215 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15215 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction, Local/SSTable >Reporter: Benedict Elliott Smith >Assignee: Aleksandr Sorokoumov >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.x > > Attachments: testWriteRandomLongDOP_final.png, > writeUnsignedVInt_megamorphic_BB.png, writeUnsignedVInt_megamorphic_DOP.png > > Time Spent: 40m > Remaining Estimate: 0h > > Most vints occupy significantly fewer than 8 bytes, and most buffers have >= > 8 bytes spare, in which case we can construct the relevant bytes in a > register and memcpy them to the correct position. Since we read and write a > lot of vints, this waste is probably measurable, particularly during > compaction and flush, and can probably be considered a performance bug. -- 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-16843) List snapshots of dropped tables
[
https://issues.apache.org/jira/browse/CASSANDRA-16843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-16843:
Reviewers: Brandon Williams, Stefan Miklosovic
> List snapshots of dropped tables
>
>
> Key: CASSANDRA-16843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16843
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Snapshots
>Reporter: James Brown
>Assignee: Paulo Motta
>Priority: Normal
> Fix For: 3.11.x, 4.0.x
>
>
> Auto snapshots from dropped tables don't seem to show up in {{nodetool
> listsnapshots}} (even though they do get cleared by {{nodetool
> clearsnapshot}}). This makes them kind of annoying to clean up, since you
> need to muck about in the data directory to find them.
> Erick on the mailing list said that this seems to be an oversight and that
> clearsnapshot was fixed by
> [CASSANDRA-6418|https://issues.apache.org/jira/browse/CASSANDRA-6418].
> I reproduced this both on 3.11.11 and 4.0.0.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16843) List snapshots of dropped tables
[
https://issues.apache.org/jira/browse/CASSANDRA-16843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-16843:
Status: Open (was: Patch Available)
> List snapshots of dropped tables
>
>
> Key: CASSANDRA-16843
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16843
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Snapshots
>Reporter: James Brown
>Assignee: Paulo Motta
>Priority: Normal
> Fix For: 3.11.x, 4.0.x
>
>
> Auto snapshots from dropped tables don't seem to show up in {{nodetool
> listsnapshots}} (even though they do get cleared by {{nodetool
> clearsnapshot}}). This makes them kind of annoying to clean up, since you
> need to muck about in the data directory to find them.
> Erick on the mailing list said that this seems to be an oversight and that
> clearsnapshot was fixed by
> [CASSANDRA-6418|https://issues.apache.org/jira/browse/CASSANDRA-6418].
> I reproduced this both on 3.11.11 and 4.0.0.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16951) Dtest cluster reusage
[
https://issues.apache.org/jira/browse/CASSANDRA-16951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468163#comment-17468163
]
Josh McKenzie commented on CASSANDRA-16951:
---
[~bereng] Where did we land on this? Is CI back in a state where this can be
picked back up?
I've chipped away at this problem in the past a bit so could take review if you
get this into a state that's ready. Perhaps along with [~k-rus] as well?
> Dtest cluster reusage
> -
>
> Key: CASSANDRA-16951
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16951
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 4.0.x
>
>
> Dtests are very heavy but in some instances most of the time is spent
> restarting nodes in between test methods. Not all of them, but many seem
> could benefit form reusing a common cluster sparing the restarts. Obviously
> that is not the case for tests that manipulate the nodes itself during the
> test. The ones that follow a setup node/do test seem to benefit greatly in
> terms of time execution.
> Some classes run time can be cut form 10m to 1,5m. Others only from 30m to
> 25m. But taking a 5m shave and considering it will probably get ran *
> with/without vnodes * j8/j11/j8j11 * 4.0/trunk turns the 5m cut into a 60m
> cut. That should be a nice reduction in CI usage. Unfortunately run time will
> mostly remain the same until we have a majority of tests reusing nodes as the
> 'longest pole' will be the determining factor.
> How it works? It's an opt-in. Annotate the first test with
> {{@reuse_cluster(new_cluster=True)}} and the following ones with
> {{@reuse_cluster}}. Best effort to reuse the cluster will be made. Stop using
> the annotation at any test method and it will start a new one.
--
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-15968) nodetool drain fails in jvm dtest
[
https://issues.apache.org/jira/browse/CASSANDRA-15968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-15968:
--
Status: Patch Available (was: Review In Progress)
> nodetool drain fails in jvm dtest
> -
>
> Key: CASSANDRA-15968
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15968
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: David Capwell
>Priority: Normal
> Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x
>
>
> Drain fails since MessagingService doesn’t expect to be shutdown twice.
> {code}
> Caused by: java.lang.AssertionError
> at
> org.apache.cassandra.net.MessagingService.shutdown(MessagingService.java:766)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$parallelRun$28(Instance.java:805)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ... 3 more
> {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-15968) nodetool drain fails in jvm dtest
[
https://issues.apache.org/jira/browse/CASSANDRA-15968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-15968:
--
Status: Open (was: Patch Available)
> nodetool drain fails in jvm dtest
> -
>
> Key: CASSANDRA-15968
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15968
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: David Capwell
>Priority: Normal
> Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x
>
>
> Drain fails since MessagingService doesn’t expect to be shutdown twice.
> {code}
> Caused by: java.lang.AssertionError
> at
> org.apache.cassandra.net.MessagingService.shutdown(MessagingService.java:766)
> at
> org.apache.cassandra.distributed.impl.Instance.lambda$parallelRun$28(Instance.java:805)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ... 3 more
> {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-17063) Make capacity/validity/updateinterval/activeupdate for Auth Caches configurable via nodetool
[
https://issues.apache.org/jira/browse/CASSANDRA-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468155#comment-17468155
]
Josh McKenzie commented on CASSANDRA-17063:
---
Took review; left some notes (nits) on the PR but LGTM. +1.
> Make capacity/validity/updateinterval/activeupdate for Auth Caches
> configurable via nodetool
>
>
> Key: CASSANDRA-17063
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17063
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
>Reporter: Aleksei Zotov
>Assignee: Aleksei Zotov
>Priority: Normal
> Fix For: 4.x
>
>
> Currently Auth Caches configuration options
> (capacity/validity/updateinterval/activeupdate) exposed via JMX or yaml only.
> We need to introduce a _nodetool setauthcachecconfig_ and _nodetool
> getauthcachecconfig_ commands.
> Also we could think of some VT-based alternative to {_}nodetool{_}. But I
> feel there is no need to have a separate table for Auth Caches configs. It
> would be an overhead. Ideally we need to have a separate VT that shows/sets
> all the configs, but it is out of the scope.
--
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-17231) Upgrade cassandra-driver-core to 4.X
[ https://issues.apache.org/jira/browse/CASSANDRA-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phyllis Li updated CASSANDRA-17231: --- Summary: Upgrade cassandra-driver-core to 4.X (was: Usage of old dependencies which contains vulnerable dependencies.) > Upgrade cassandra-driver-core to 4.X > > > Key: CASSANDRA-17231 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17231 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Phyllis Li >Assignee: Phyllis Li >Priority: Normal > Labels: security > Fix For: 4.x > > > The current Cassandra driver version is 3.11.0, which uses a vulnerable > version of jackson-databind. > We may want to switch to the re-branded com.datastax.oss:java-driver-core > 4.13.0. -- 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-17231) Usage of old dependencies which contains vulnerable dependencies.
[ https://issues.apache.org/jira/browse/CASSANDRA-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phyllis Li updated CASSANDRA-17231: --- Labels: security (was: ) > Usage of old dependencies which contains vulnerable dependencies. > - > > Key: CASSANDRA-17231 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17231 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Phyllis Li >Assignee: Phyllis Li >Priority: Normal > Labels: security > Fix For: 4.x > > > The current Cassandra driver version is 3.11.0, which uses a vulnerable > version of jackson-databind. > We may want to switch to the re-branded com.datastax.oss:java-driver-core > 4.13.0. -- 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-17231) Usage of old dependencies which contains vulnerable dependencies.
[ https://issues.apache.org/jira/browse/CASSANDRA-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phyllis Li updated CASSANDRA-17231: --- Platform: (was: All) > Usage of old dependencies which contains vulnerable dependencies. > - > > Key: CASSANDRA-17231 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17231 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Phyllis Li >Assignee: Phyllis Li >Priority: Normal > Fix For: 4.x > > > The current Cassandra driver version is 3.11.0, which uses a vulnerable > version of jackson-databind. > We may want to switch to the re-branded com.datastax.oss:java-driver-core > 4.13.0. -- 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-17231) Usage of old dependencies which contains vulnerable dependencies.
[ https://issues.apache.org/jira/browse/CASSANDRA-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phyllis Li updated CASSANDRA-17231: --- Impacts: (was: None) > Usage of old dependencies which contains vulnerable dependencies. > - > > Key: CASSANDRA-17231 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17231 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Phyllis Li >Assignee: Phyllis Li >Priority: Normal > Fix For: 4.x > > > The current Cassandra driver version is 3.11.0, which uses a vulnerable > version of jackson-databind. > We may want to switch to the re-branded com.datastax.oss:java-driver-core > 4.13.0. -- 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-17231) Usage of old dependencies which contains vulnerable dependencies.
[ https://issues.apache.org/jira/browse/CASSANDRA-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phyllis Li reassigned CASSANDRA-17231: -- Assignee: Phyllis Li > Usage of old dependencies which contains vulnerable dependencies. > - > > Key: CASSANDRA-17231 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17231 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Phyllis Li >Assignee: Phyllis Li >Priority: Normal > > The current Cassandra driver version is 3.11.0, which uses a vulnerable > version of jackson-databind. > We may want to switch to the re-branded com.datastax.oss:java-driver-core > 4.13.0. -- 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-17231) Usage of old dependencies which contains vulnerable dependencies.
[ https://issues.apache.org/jira/browse/CASSANDRA-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phyllis Li updated CASSANDRA-17231: --- Fix Version/s: 4.x > Usage of old dependencies which contains vulnerable dependencies. > - > > Key: CASSANDRA-17231 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17231 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Phyllis Li >Assignee: Phyllis Li >Priority: Normal > Fix For: 4.x > > > The current Cassandra driver version is 3.11.0, which uses a vulnerable > version of jackson-databind. > We may want to switch to the re-branded com.datastax.oss:java-driver-core > 4.13.0. -- 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-17231) Usage of old dependencies which contains vulnerable dependencies.
Phyllis Li created CASSANDRA-17231: -- Summary: Usage of old dependencies which contains vulnerable dependencies. Key: CASSANDRA-17231 URL: https://issues.apache.org/jira/browse/CASSANDRA-17231 Project: Cassandra Issue Type: Bug Components: Dependencies Reporter: Phyllis Li The current Cassandra driver version is 3.11.0, which uses a vulnerable version of jackson-databind. We may want to switch to the re-branded com.datastax.oss:java-driver-core 4.13.0. -- 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-17063) Make capacity/validity/updateinterval/activeupdate for Auth Caches configurable via nodetool
[
https://issues.apache.org/jira/browse/CASSANDRA-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17063:
--
Status: Review In Progress (was: Needs Committer)
> Make capacity/validity/updateinterval/activeupdate for Auth Caches
> configurable via nodetool
>
>
> Key: CASSANDRA-17063
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17063
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
>Reporter: Aleksei Zotov
>Assignee: Aleksei Zotov
>Priority: Normal
> Fix For: 4.x
>
>
> Currently Auth Caches configuration options
> (capacity/validity/updateinterval/activeupdate) exposed via JMX or yaml only.
> We need to introduce a _nodetool setauthcachecconfig_ and _nodetool
> getauthcachecconfig_ commands.
> Also we could think of some VT-based alternative to {_}nodetool{_}. But I
> feel there is no need to have a separate table for Auth Caches configs. It
> would be an overhead. Ideally we need to have a separate VT that shows/sets
> all the configs, but it is out of the scope.
--
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-17063) Make capacity/validity/updateinterval/activeupdate for Auth Caches configurable via nodetool
[
https://issues.apache.org/jira/browse/CASSANDRA-17063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANDRA-17063:
--
Reviewers: Josh McKenzie
> Make capacity/validity/updateinterval/activeupdate for Auth Caches
> configurable via nodetool
>
>
> Key: CASSANDRA-17063
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17063
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
>Reporter: Aleksei Zotov
>Assignee: Aleksei Zotov
>Priority: Normal
> Fix For: 4.x
>
>
> Currently Auth Caches configuration options
> (capacity/validity/updateinterval/activeupdate) exposed via JMX or yaml only.
> We need to introduce a _nodetool setauthcachecconfig_ and _nodetool
> getauthcachecconfig_ commands.
> Also we could think of some VT-based alternative to {_}nodetool{_}. But I
> feel there is no need to have a separate table for Auth Caches configs. It
> would be an overhead. Ideally we need to have a separate VT that shows/sets
> all the configs, but it is out of the scope.
--
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-16436) Add startup check for large read_ahead_kb setting
[
https://issues.apache.org/jira/browse/CASSANDRA-16436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-16436:
Status: Ready to Commit (was: Review In Progress)
> Add startup check for large read_ahead_kb setting
> -
>
> Key: CASSANDRA-16436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16436
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Startup and Shutdown
>Reporter: Paulo Motta
>Assignee: Kanthi Subramanian
>Priority: Normal
> Labels: AdventCalendar2021, lhf
>
> A well known production tuning recommendation is to dial back the
> {{read_ahead_kb}} Linux setting from the default of 4096 in most
> distributions as this can cause high IO usage and cache churn on
> read-intensive workloads.
> We should add a startup warning to detect when a high {{read_ahead_kb}} is
> used and recommend the user to dial back to a reasonable value, which varies
> according to the workload but a general guideline is to tune this to 8kb.
--
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-16436) Add startup check for large read_ahead_kb setting
[
https://issues.apache.org/jira/browse/CASSANDRA-16436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-16436:
Reviewers: Brandon Williams, Paulo Motta (was: Paulo Motta)
Status: Review In Progress (was: Needs Committer)
> Add startup check for large read_ahead_kb setting
> -
>
> Key: CASSANDRA-16436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16436
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Startup and Shutdown
>Reporter: Paulo Motta
>Assignee: Kanthi Subramanian
>Priority: Normal
> Labels: AdventCalendar2021, lhf
>
> A well known production tuning recommendation is to dial back the
> {{read_ahead_kb}} Linux setting from the default of 4096 in most
> distributions as this can cause high IO usage and cache churn on
> read-intensive workloads.
> We should add a startup warning to detect when a high {{read_ahead_kb}} is
> used and recommend the user to dial back to a reasonable value, which varies
> according to the workload but a general guideline is to tune this to 8kb.
--
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-17198) Allow to filter using LIKE predicates
[
https://issues.apache.org/jira/browse/CASSANDRA-17198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468124#comment-17468124
]
Kanthi Subramanian commented on CASSANDRA-17198:
[~blerer] I removed the restrictions here, but the like query doesnt work as
expected for example 'John%' doesnt work, any thoughts on where I should be
looking into. I did add an index.
[https://github.com/apache/cassandra/pull/1373/files]
{code:java}
// code placeholder
cqlsh:tutorialspoint> select * from emp where emp_name like 'John Doe%' allow
filtering; emp_id | date | emp_name
+---+--
1 | 1564830182000 | John Doe(1 rows)
cqlsh:tutorialspoint> select * from emp where emp_name like 'John%' allow
filtering; emp_id | date | emp_name
+--+--
{code}
> Allow to filter using LIKE predicates
> -
>
> Key: CASSANDRA-17198
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17198
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Syntax
>Reporter: Benjamin Lerer
>Assignee: Kanthi Subramanian
>Priority: Normal
> Labels: AdventCalendar2021, lhf
> Fix For: 4.x
>
>
> {{LIKE}} predicates can only be used with the SASI indices. In several
> usecases (e.g. querying the {{settings}} virtual table) it makes sense to
> support them for filtering.
> + Additional information for newcomers:+
> There are some checks in the {{StatementRestrictions}} constructor and on
> {{LikeRestriction}} that need to be removed for allowing filtering using LIKE
> on clustering and regular columns.
> For filtering on partition columns the {{needFiltering}} methods in
> {{PartitionKeySingleRestrictionSet}} will need to be modified to return true
> when LIKE predicate are used.
> The unit tests should go in {{SelectTest}}.
--
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-16436) Add startup check for large read_ahead_kb setting
[
https://issues.apache.org/jira/browse/CASSANDRA-16436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468086#comment-17468086
]
Brandon Williams commented on CASSANDRA-16436:
--
Looks good, failures are not related. +1
A minor nit is it would be nice to add some "or lower" language to the
recommendations since that is generally the direction people should vary from
the recommendation if they do.
> Add startup check for large read_ahead_kb setting
> -
>
> Key: CASSANDRA-16436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16436
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Startup and Shutdown
>Reporter: Paulo Motta
>Assignee: Kanthi Subramanian
>Priority: Normal
> Labels: AdventCalendar2021, lhf
>
> A well known production tuning recommendation is to dial back the
> {{read_ahead_kb}} Linux setting from the default of 4096 in most
> distributions as this can cause high IO usage and cache churn on
> read-intensive workloads.
> We should add a startup warning to detect when a high {{read_ahead_kb}} is
> used and recommend the user to dial back to a reasonable value, which varies
> according to the workload but a general guideline is to tune this to 8kb.
--
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-17218) Update ant
[ https://issues.apache.org/jira/browse/CASSANDRA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468054#comment-17468054 ] Ekaterina Dimitrova commented on CASSANDRA-17218: - Thanks [~mck] CI runs: [4.0|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:17218-4.0?expand=1] | [Jenkins|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1343/] [trunk|https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:17218-trunk?expand=1] | [Jenkins|https://jenkins-cm4.apache.org/job/Cassandra-devbranch/1344/] > Update ant > -- > > Key: CASSANDRA-17218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17218 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.x > > -- 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-17218) Update ant
[ https://issues.apache.org/jira/browse/CASSANDRA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17218: Fix Version/s: (was: 4.0.x) > Update ant > -- > > Key: CASSANDRA-17218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17218 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > -- 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-17218) Update ant
[ https://issues.apache.org/jira/browse/CASSANDRA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17218: Fix Version/s: 4.0.x > Update ant > -- > > Key: CASSANDRA-17218 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17218 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0.x, 4.x > > -- 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-16308) Add droppable tombstone metrics to nodetool tablestats
[ https://issues.apache.org/jira/browse/CASSANDRA-16308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta updated CASSANDRA-16308: Fix Version/s: 4.0.2 4.1 Source Control Link: https://github.com/apache/cassandra/commit/c420d754d8571120e58b2fe4838c766d26169d7d Resolution: Fixed Status: Resolved (was: Ready to Commit) > Add droppable tombstone metrics to nodetool tablestats > -- > > Key: CASSANDRA-16308 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16308 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Paulo Motta >Assignee: Krishna Vadali >Priority: Low > Fix For: 4.0.2, 4.1 > > Time Spent: 20m > Remaining Estimate: 0h > > This is a useful metric to troubleshoot tombstone cleanup problems and is not > currently exposed on table stats. > While we're at it we should add the JMX metric to the table metrics > documentation because it's currently missing. -- 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 trunk updated (11952fa -> 481c103)
This is an automated email from the ASF dual-hosted git repository. paulo pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 11952fa Avoid unecessary array allocations and initializations when performing query checks new c420d75 CASSANDRA-16308: Add droppable tombstone metrics to nodetool tablestats new 481c103 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: CHANGES.txt| 1 + src/java/org/apache/cassandra/tools/NodeProbe.java | 5 + src/java/org/apache/cassandra/tools/nodetool/stats/StatsTable.java | 1 + .../apache/cassandra/tools/nodetool/stats/TableStatsHolder.java| 3 +++ .../apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java | 1 + .../cassandra/tools/nodetool/stats/TableStatsPrinterTest.java | 6 ++ .../apache/cassandra/tools/nodetool/stats/TableStatsTestBase.java | 7 +++ 7 files changed, 24 insertions(+) - 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: CASSANDRA-16308: Add droppable tombstone metrics to nodetool tablestats
This is an automated email from the ASF dual-hosted git repository.
paulo 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 c420d75 CASSANDRA-16308: Add droppable tombstone metrics to nodetool
tablestats
c420d75 is described below
commit c420d754d8571120e58b2fe4838c766d26169d7d
Author: tejavadali
AuthorDate: Sun Dec 12 22:31:15 2021 +0530
CASSANDRA-16308: Add droppable tombstone metrics to nodetool tablestats
patch by Krishna Vadali; reviewed by Paulo Motta and Brandon Williams for
CASSANDRA-16308
Closes #1359
---
CHANGES.txt| 1 +
src/java/org/apache/cassandra/tools/NodeProbe.java | 5 +
src/java/org/apache/cassandra/tools/nodetool/stats/StatsTable.java | 1 +
.../apache/cassandra/tools/nodetool/stats/TableStatsHolder.java| 3 +++
.../apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java | 1 +
.../cassandra/tools/nodetool/stats/TableStatsPrinterTest.java | 6 ++
.../apache/cassandra/tools/nodetool/stats/TableStatsTestBase.java | 7 +++
7 files changed, 24 insertions(+)
diff --git a/CHANGES.txt b/CHANGES.txt
index 77d2737..aa3b707 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
4.0.2
+ * Add droppable tombstone metrics to nodetool tablestats (CASSANDRA-16308)
* Fix disk failure triggered when enabling FQL on an unclean directory
(CASSANDRA-17136)
* Fixed broken classpath when multiple jars in build directory
(CASSANDRA-17129)
* DebuggableThreadPoolExecutor does not propagate client warnings
(CASSANDRA-17072)
diff --git a/src/java/org/apache/cassandra/tools/NodeProbe.java
b/src/java/org/apache/cassandra/tools/NodeProbe.java
index 9b221e9..101aab3 100644
--- a/src/java/org/apache/cassandra/tools/NodeProbe.java
+++ b/src/java/org/apache/cassandra/tools/NodeProbe.java
@@ -467,6 +467,11 @@ public class NodeProbe implements AutoCloseable
return result;
}
+public double getDroppableTombstoneRatio(String keyspace, String table) {
+ColumnFamilyStoreMBean cfsProxy = getCfsProxy(keyspace, table);
+return cfsProxy.getDroppableTombstoneRatio();
+}
+
public void invalidateCounterCache()
{
cacheService.invalidateCounterCache();
diff --git a/src/java/org/apache/cassandra/tools/nodetool/stats/StatsTable.java
b/src/java/org/apache/cassandra/tools/nodetool/stats/StatsTable.java
index d897eab..0859327 100644
--- a/src/java/org/apache/cassandra/tools/nodetool/stats/StatsTable.java
+++ b/src/java/org/apache/cassandra/tools/nodetool/stats/StatsTable.java
@@ -70,4 +70,5 @@ public class StatsTable
public String droppedMutations;
public List sstablesInEachLevel = new ArrayList<>();
public Boolean isInCorrectLocation = null; // null: option not active
+public double droppableTombstoneRatio;
}
diff --git
a/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsHolder.java
b/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsHolder.java
index b1685e6..a587738 100644
--- a/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsHolder.java
+++ b/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsHolder.java
@@ -161,6 +161,8 @@ public class TableStatsHolder implements StatsHolder
mpTable.put("maximum_tombstones_per_slice_last_five_minutes",
table.maximumTombstonesPerSliceLastFiveMinutes);
mpTable.put("dropped_mutations", table.droppedMutations);
+mpTable.put("droppable_tombstone_ratio",
+String.format("%01.5f", table.droppableTombstoneRatio));
if (locationCheck)
mpTable.put("sstables_in_correct_location",
table.isInCorrectLocation);
return mpTable;
@@ -345,6 +347,7 @@ public class TableStatsHolder implements StatsHolder
statsTable.averageTombstonesPerSliceLastFiveMinutes =
histogram.getMean();
statsTable.maximumTombstonesPerSliceLastFiveMinutes =
histogram.getMax();
statsTable.droppedMutations = format((Long)
probe.getColumnFamilyMetric(keyspaceName, tableName, "DroppedMutations"),
humanReadable);
+statsTable.droppableTombstoneRatio =
probe.getDroppableTombstoneRatio(keyspaceName, tableName);
statsKeyspace.tables.add(statsTable);
}
keyspaces.add(statsKeyspace);
diff --git
a/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
b/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
index f4188e4..d8e4d4a 100644
--- a/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
+++ b/src/java/org/apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java
@@ -126,6 +126,7 @@ public class TableStatsPrinter
out.println(indent + "Average tombstones per slice
[cassandra] 01/01: Merge branch 'cassandra-4.0' into trunk
This is an automated email from the ASF dual-hosted git repository. paulo pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 481c103951ef8caa74a27dd474c94d9c9e819a46 Merge: 11952fa c420d75 Author: Paulo Motta AuthorDate: Mon Jan 3 11:57:42 2022 -0300 Merge branch 'cassandra-4.0' into trunk CHANGES.txt| 1 + src/java/org/apache/cassandra/tools/NodeProbe.java | 5 + src/java/org/apache/cassandra/tools/nodetool/stats/StatsTable.java | 1 + .../apache/cassandra/tools/nodetool/stats/TableStatsHolder.java| 3 +++ .../apache/cassandra/tools/nodetool/stats/TableStatsPrinter.java | 1 + .../cassandra/tools/nodetool/stats/TableStatsPrinterTest.java | 6 ++ .../apache/cassandra/tools/nodetool/stats/TableStatsTestBase.java | 7 +++ 7 files changed, 24 insertions(+) diff --cc CHANGES.txt index 6208963,aa3b707..f6918d9 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,77 -1,5 +1,78 @@@ -4.0.2 +4.1 + * Avoid unecessary array allocations and initializations when performing query checks (CASSANDRA-17209) + * Add guardrail for list operations that require read before write (CASSANDRA-17154) + * Migrate thresholds for number of keyspaces and tables to guardrails (CASSANDRA-17195) + * Remove self-reference in SSTableTidier (CASSANDRA-17205) + * Add guardrail for query page size (CASSANDRA-17189) + * Allow column_index_size_in_kb to be configurable through nodetool (CASSANDRA-17121) + * Emit a metric for number of local read and write calls + * Add non-blocking mode for CDC writes (CASSANDRA-17001) + * Add guardrails framework (CASSANDRA-17147) + * Harden resource management on SSTable components to prevent future leaks (CASSANDRA-17174) + * Make nodes more resilient to local unrelated files during startup (CASSANDRA-17082) + * repair prepare message would produce a wrong error message if network timeout happened rather than reply wait timeout (CASSANDRA-16992) + * Log queries that fail on timeout or unavailable errors up to once per minute by default (CASSANDRA-17159) + * Refactor normal/preview/IR repair to standardize repair cleanup and error handling of failed RepairJobs (CASSANDRA-17069) + * Log missing peers in StartupClusterConnectivityChecker (CASSANDRA-17130) + * Introduce separate rate limiting settings for entire SSTable streaming (CASSANDRA-17065) + * Implement Virtual Tables for Auth Caches (CASSANDRA-16914) + * Actively update auth cache in the background (CASSANDRA-16957) + * Add unix time conversion functions (CASSANDRA-17029) + * JVMStabilityInspector.forceHeapSpaceOomMaybe should handle all non-heap OOMs rather than only supporting direct only (CASSANDRA-17128) + * Forbid other Future implementations with checkstyle (CASSANDRA-17055) + * commit log was switched from non-daemon to daemon threads, which causes the JVM to exit in some case as no non-daemon threads are active (CASSANDRA-17085) + * Add a Denylist to block reads and writes on specific partition keys (CASSANDRA-12106) + * v4+ protocol did not clean up client warnings, which caused leaking the state (CASSANDRA-17054) + * Remove duplicate toCQLString in ReadCommand (CASSANDRA-17023) + * Ensure hint window is persistent across restarts of a node (CASSANDRA-14309) + * Allow to GRANT or REVOKE multiple permissions in a single statement (CASSANDRA-17030) + * Allow to grant permission for all tables in a keyspace (CASSANDRA-17027) + * Log time spent writing keys during compaction (CASSANDRA-17037) + * Make nodetool compactionstats and sstable_tasks consistent (CASSANDRA-16976) + * Add metrics and logging around index summary redistribution (CASSANDRA-17036) + * Add configuration options for minimum allowable replication factor and default replication factor (CASSANDRA-14557) + * Expose information about stored hints via a nodetool command and a virtual table (CASSANDRA-14795) + * Add broadcast_rpc_address to system.local (CASSANDRA-11181) + * Add support for type casting in WHERE clause components and in the values of INSERT/UPDATE statements (CASSANDRA-14337) + * add credentials file support to CQLSH (CASSANDRA-16983) + * Skip remaining bytes in the Envelope buffer when a ProtocolException is thrown to avoid double decoding (CASSANDRA-17026) + * Allow reverse iteration of resources during permissions checking (CASSANDRA-17016) + * Add feature to verify correct ownership of attached locations on disk at startup (CASSANDRA-16879) + * Make SSLContext creation pluggable/extensible (CASSANDRA-1) + * Add soft/hard limits to local reads to protect against reading too much data in a single query (CASSANDRA-16896) + * Avoid token cache invalidation for removing a non-member node (CASSANDRA-15290) + * Allow configuration of consistency levels on auth operations (CASSANDRA-12988) + * Add number of sstables in a compaction to
[jira] [Commented] (CASSANDRA-17230) Trunk warnings: Unsafe is internal proprietary API and may be removed in a future release
[
https://issues.apache.org/jira/browse/CASSANDRA-17230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468032#comment-17468032
]
Benedict Elliott Smith commented on CASSANDRA-17230:
Hi Ekaterina,
I'm aware of this, but the only solution is to pass the quite expansive
{{-XDignore.symbol.file}} property to the compiler. This seems to be what we do
for our {{java/src}} builds, but I'm not sure if it's actually a sensible thing
to do or not, since it captures a lot more than {{sun.misc.Unsafe}}. I'm not
hugely fond of this kind of widespread warning suppression.
> Trunk warnings: Unsafe is internal proprietary API and may be removed in a
> future release
> -
>
> Key: CASSANDRA-17230
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17230
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Ekaterina Dimitrova
>Priority: Low
> Fix For: 4.x
>
>
> We see on trunk the following warnings:
>
> {code:java}
> _simulator-bootstrap_build:
> [mkdir] Created dir:
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/build/classes/simulator-bootstrap
> [javac] Compiling 1 source file to
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/build/classes/simulator-bootstrap
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:29:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] import sun.misc.Unsafe;
> [javac] ^
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:192:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] public static Unsafe getUnsafe()
> [javac] ^
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:196:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] Field field =
> Unsafe.class.getDeclaredField("theUnsafe");
> [javac] ^
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:198:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] return (Unsafe) field.get(null);
> [javac] ^
>
> [javac] 4 warnings
> {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-17230) Trunk warnings: Unsafe is internal proprietary API and may be removed in a future release
[
https://issues.apache.org/jira/browse/CASSANDRA-17230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468019#comment-17468019
]
Ekaterina Dimitrova commented on CASSANDRA-17230:
-
CC [~benedict]
> Trunk warnings: Unsafe is internal proprietary API and may be removed in a
> future release
> -
>
> Key: CASSANDRA-17230
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17230
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Ekaterina Dimitrova
>Priority: Low
> Fix For: 4.x
>
>
> We see on trunk the following warnings:
>
> {code:java}
> _simulator-bootstrap_build:
> [mkdir] Created dir:
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/build/classes/simulator-bootstrap
> [javac] Compiling 1 source file to
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/build/classes/simulator-bootstrap
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:29:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] import sun.misc.Unsafe;
> [javac] ^
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:192:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] public static Unsafe getUnsafe()
> [javac] ^
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:196:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] Field field =
> Unsafe.class.getDeclaredField("theUnsafe");
> [javac] ^
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:198:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] return (Unsafe) field.get(null);
> [javac] ^
>
> [javac] 4 warnings
> {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-17230) Trunk warnings: Unsafe is internal proprietary API and may be removed in a future release
[
https://issues.apache.org/jira/browse/CASSANDRA-17230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-17230:
Change Category: Code Clarity
Complexity: Low Hanging Fruit
Component/s: Build
Fix Version/s: 4.x
Priority: Low (was: Normal)
Status: Open (was: Triage Needed)
> Trunk warnings: Unsafe is internal proprietary API and may be removed in a
> future release
> -
>
> Key: CASSANDRA-17230
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17230
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Ekaterina Dimitrova
>Priority: Low
> Fix For: 4.x
>
>
> We see on trunk the following warnings:
>
> {code:java}
> _simulator-bootstrap_build:
> [mkdir] Created dir:
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/build/classes/simulator-bootstrap
> [javac] Compiling 1 source file to
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/build/classes/simulator-bootstrap
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:29:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] import sun.misc.Unsafe;
> [javac] ^
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:192:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] public static Unsafe getUnsafe()
> [javac] ^
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:196:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] Field field =
> Unsafe.class.getDeclaredField("theUnsafe");
> [javac] ^
> [javac]
> /Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:198:
> warning: Unsafe is internal proprietary API and may be removed in a future
> release
> [javac] return (Unsafe) field.get(null);
> [javac] ^
>
> [javac] 4 warnings
> {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-17230) Trunk warnings: Unsafe is internal proprietary API and may be removed in a future release
Ekaterina Dimitrova created CASSANDRA-17230:
---
Summary: Trunk warnings: Unsafe is internal proprietary API and
may be removed in a future release
Key: CASSANDRA-17230
URL: https://issues.apache.org/jira/browse/CASSANDRA-17230
Project: Cassandra
Issue Type: Task
Reporter: Ekaterina Dimitrova
We see on trunk the following warnings:
{code:java}
_simulator-bootstrap_build:
[mkdir] Created dir:
/Users/ekaterina.dimitri/IdeaProjects/april/cassandra/build/classes/simulator-bootstrap
[javac] Compiling 1 source file to
/Users/ekaterina.dimitri/IdeaProjects/april/cassandra/build/classes/simulator-bootstrap
[javac]
/Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:29:
warning: Unsafe is internal proprietary API and may be removed in a future
release
[javac] import sun.misc.Unsafe;
[javac] ^
[javac]
/Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:192:
warning: Unsafe is internal proprietary API and may be removed in a future
release
[javac] public static Unsafe getUnsafe()
[javac] ^
[javac]
/Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:196:
warning: Unsafe is internal proprietary API and may be removed in a future
release
[javac] Field field =
Unsafe.class.getDeclaredField("theUnsafe");
[javac] ^
[javac]
/Users/ekaterina.dimitri/IdeaProjects/april/cassandra/test/simulator/bootstrap/org/apache/cassandra/simulator/systems/InterceptorOfSystemMethods.java:198:
warning: Unsafe is internal proprietary API and may be removed in a future
release
[javac] return (Unsafe) field.get(null);
[javac] ^
[javac] 4 warnings
{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-16308) Add droppable tombstone metrics to nodetool tablestats
[ https://issues.apache.org/jira/browse/CASSANDRA-16308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta updated CASSANDRA-16308: Reviewers: Brandon Williams, Paulo Motta (was: Paulo Motta) Status: Review In Progress (was: Needs Committer) > Add droppable tombstone metrics to nodetool tablestats > -- > > Key: CASSANDRA-16308 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16308 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Paulo Motta >Assignee: Krishna Vadali >Priority: Low > Time Spent: 10m > Remaining Estimate: 0h > > This is a useful metric to troubleshoot tombstone cleanup problems and is not > currently exposed on table stats. > While we're at it we should add the JMX metric to the table metrics > documentation because it's currently missing. -- 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-16308) Add droppable tombstone metrics to nodetool tablestats
[ https://issues.apache.org/jira/browse/CASSANDRA-16308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta updated CASSANDRA-16308: Status: Ready to Commit (was: Review In Progress) > Add droppable tombstone metrics to nodetool tablestats > -- > > Key: CASSANDRA-16308 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16308 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Paulo Motta >Assignee: Krishna Vadali >Priority: Low > Time Spent: 10m > Remaining Estimate: 0h > > This is a useful metric to troubleshoot tombstone cleanup problems and is not > currently exposed on table stats. > While we're at it we should add the JMX metric to the table metrics > documentation because it's currently missing. -- 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-16308) Add droppable tombstone metrics to nodetool tablestats
[ https://issues.apache.org/jira/browse/CASSANDRA-16308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468003#comment-17468003 ] Brandon Williams commented on CASSANDRA-16308: -- LGTM too, test failures are unrelated, +1. > Add droppable tombstone metrics to nodetool tablestats > -- > > Key: CASSANDRA-16308 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16308 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Paulo Motta >Assignee: Krishna Vadali >Priority: Low > Time Spent: 10m > Remaining Estimate: 0h > > This is a useful metric to troubleshoot tombstone cleanup problems and is not > currently exposed on table stats. > While we're at it we should add the JMX metric to the table metrics > documentation because it's currently missing. -- 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-10023) Emit a metric for number of local read and write calls
[ https://issues.apache.org/jira/browse/CASSANDRA-10023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-10023: - Resolution: Fixed Status: Resolved (was: Open) This was commited in 0a6fbe47678d304bd43af0c644ece8ec58646a7a > Emit a metric for number of local read and write calls > -- > > Key: CASSANDRA-10023 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10023 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Metrics >Reporter: Sankalp Kohli >Assignee: Stefan Miklosovic >Priority: Low > Labels: 4.0-feature-freeze-review-requested, lhf > Fix For: 4.1 > > Attachments: 10023-trunk-dtests.txt, 10023-trunk.txt, > CASSANDRA-10023.patch > > > Many C* drivers have feature to be replica aware and chose the co-ordinator > which is a replica. We should add a metric which tells us whether all calls > to the co-ordinator are replica aware. > We have seen issues where client thinks they are replica aware when they > forget to add routing key at various places in the 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
