[jira] [Comment Edited] (CASSANDRA-18642) cqlsh on Cassandra 4.1.2 fails on Amazon Linux

[ https://issues.apache.org/jira/browse/CASSANDRA-18642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868131#comment-17868131 ] Scott Carey edited comment on CASSANDRA-18642 at 7/23/24 5:19 PM:

[jira] [Commented] (CASSANDRA-18642) cqlsh on Cassandra 4.1.2 fails on Amazon Linux

[ https://issues.apache.org/jira/browse/CASSANDRA-18642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868131#comment-17868131 ] Scott Carey commented on CASSANDRA-18642: - This affects AlmaLinux 9 as far a

[jira] [Comment Edited] (CASSANDRA-16772) User Defined nodetool cleanup only processes one SSTable per table

[ https://issues.apache.org/jira/browse/CASSANDRA-16772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371574#comment-17371574 ] Scott Carey edited comment on CASSANDRA-16772 at 6/29/21, 6:39 PM: ---

[jira] [Comment Edited] (CASSANDRA-16772) User Defined nodetool cleanup only processes one SSTable per table

[ https://issues.apache.org/jira/browse/CASSANDRA-16772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371574#comment-17371574 ] Scott Carey edited comment on CASSANDRA-16772 at 6/29/21, 6:36 PM: ---

[jira] [Commented] (CASSANDRA-16772) User Defined nodetool cleanup only processes one SSTable per table

[ https://issues.apache.org/jira/browse/CASSANDRA-16772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371574#comment-17371574 ] Scott Carey commented on CASSANDRA-16772: - Looking at the code more closely

[jira] [Updated] (CASSANDRA-16772) User Defined nodetool cleanup only processes one SSTable per table

[ https://issues.apache.org/jira/browse/CASSANDRA-16772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Carey updated CASSANDRA-16772: Fix Version/s: 3.11.x > User Defined nodetool cleanup only processes one SSTable per t

[jira] [Updated] (CASSANDRA-16772) User Defined nodetool cleanup only processes one SSTable per table

[ https://issues.apache.org/jira/browse/CASSANDRA-16772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Carey updated CASSANDRA-16772: Description: User defined nodetool cleanup uses a HashMap instead of a MultiMap to gro

[jira] [Created] (CASSANDRA-16772) User Defined nodetool cleanup only processes one SSTable per table

Scott Carey created CASSANDRA-16772: --- Summary: User Defined nodetool cleanup only processes one SSTable per table Key: CASSANDRA-16772 URL: https://issues.apache.org/jira/browse/CASSANDRA-16772 Proj

[jira] [Commented] (CASSANDRA-16769) Add an option to nodetool garbagecollect that collects only a fraction of the data

[ https://issues.apache.org/jira/browse/CASSANDRA-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370368#comment-17370368 ] Scott Carey commented on CASSANDRA-16769: - Pull request: [https://github.com

[jira] [Updated] (CASSANDRA-16769) Add an option to nodetool garbagecollect that collects only a fraction of the data

[ https://issues.apache.org/jira/browse/CASSANDRA-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Carey updated CASSANDRA-16769: Description: nodetool garbagecollect can currently only run across an entire table. F

[jira] [Updated] (CASSANDRA-16769) Add an option to nodetool garbagecollect that collects only a fraction of the data

[ https://issues.apache.org/jira/browse/CASSANDRA-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Carey updated CASSANDRA-16769: Description: nodetool garbagecollect can currently only run across an entire table. {

[jira] [Commented] (CASSANDRA-16768) Add user defined SSTables optoin for nodetool scrub

[ https://issues.apache.org/jira/browse/CASSANDRA-16768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370184#comment-17370184 ] Scott Carey commented on CASSANDRA-16768: - Pull request: [https://github.com

[jira] [Commented] (CASSANDRA-16767) Add user defined SSTables option for nodetool garbagecollect

[ https://issues.apache.org/jira/browse/CASSANDRA-16767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370160#comment-17370160 ] Scott Carey commented on CASSANDRA-16767: - Pull request here: [https://githu

[jira] [Created] (CASSANDRA-16769) Add an option to nodetool garbagecollect that collects only a fraction of the data

Scott Carey created CASSANDRA-16769: --- Summary: Add an option to nodetool garbagecollect that collects only a fraction of the data Key: CASSANDRA-16769 URL: https://issues.apache.org/jira/browse/CASSANDRA-16769

[jira] [Created] (CASSANDRA-16768) Add user defined SSTables optoin for nodetool scrub

Scott Carey created CASSANDRA-16768: --- Summary: Add user defined SSTables optoin for nodetool scrub Key: CASSANDRA-16768 URL: https://issues.apache.org/jira/browse/CASSANDRA-16768 Project: Cassandra

[jira] [Created] (CASSANDRA-16767) Add user defined SSTables option for nodetool garbagecollect

Scott Carey created CASSANDRA-16767: --- Summary: Add user defined SSTables option for nodetool garbagecollect Key: CASSANDRA-16767 URL: https://issues.apache.org/jira/browse/CASSANDRA-16767 Project: C

[jira] [Commented] (CASSANDRA-13677) Make SASI timeouts easier to debug

[ https://issues.apache.org/jira/browse/CASSANDRA-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340437#comment-17340437 ] Scott Carey commented on CASSANDRA-13677: - It would be fantastic if this wer

[jira] [Commented] (CASSANDRA-16634) Garbagecollect should not output all tables to L0 with LeveledCompactionStrategy

[ https://issues.apache.org/jira/browse/CASSANDRA-16634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17334450#comment-17334450 ] Scott Carey commented on CASSANDRA-16634: - Excellent.  Thanks!     > Garb

[jira] [Commented] (CASSANDRA-16634) Garbagecollect should not output all tables to L0 with LeveledCompactionStrategy

[ https://issues.apache.org/jira/browse/CASSANDRA-16634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332803#comment-17332803 ] Scott Carey commented on CASSANDRA-16634: - [https://github.com/apache/cassan

[jira] [Commented] (CASSANDRA-16634) Garbagecollect should not output all tables to L0 with LeveledCompactionStrategy

[ https://issues.apache.org/jira/browse/CASSANDRA-16634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332793#comment-17332793 ] Scott Carey commented on CASSANDRA-16634: - I need some minor guidance on the

[jira] [Created] (CASSANDRA-16634) Garbagecollect should not output all tables to L0 with LeveledCompactionStrategy

Scott Carey created CASSANDRA-16634: --- Summary: Garbagecollect should not output all tables to L0 with LeveledCompactionStrategy Key: CASSANDRA-16634 URL: https://issues.apache.org/jira/browse/CASSANDRA-16634

[jira] [Comment Edited] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes

[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244553#comment-17244553 ] Scott Carey edited comment on CASSANDRA-16071 at 12/5/20, 5:52 PM: ---

[jira] [Commented] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes

[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244553#comment-17244553 ] Scott Carey commented on CASSANDRA-16071: - [~mck] Thank you for the update

[jira] [Comment Edited] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes

[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235006#comment-17235006 ] Scott Carey edited comment on CASSANDRA-16071 at 11/18/20, 9:15 PM: --

[jira] [Commented] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes

[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235006#comment-17235006 ] Scott Carey commented on CASSANDRA-16071: - On the other hand, maybe I'm the

[jira] [Commented] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes

[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235004#comment-17235004 ] Scott Carey commented on CASSANDRA-16071: - I still have to do a rolling re-i

[jira] [Comment Edited] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes

[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232194#comment-17232194 ] Scott Carey edited comment on CASSANDRA-16071 at 11/15/20, 3:15 AM: --

[jira] [Commented] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes

[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232194#comment-17232194 ] Scott Carey commented on CASSANDRA-16071: - Its worse than I remembered.   Up

[jira] [Commented] (CASSANDRA-16071) max_compaction_flush_memory_in_mb is interpreted as bytes

[ https://issues.apache.org/jira/browse/CASSANDRA-16071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197916#comment-17197916 ] Scott Carey commented on CASSANDRA-16071: - Heads-up for anyone currently wor

[jira] [Comment Edited] (CASSANDRA-12662) OOM when using SASI index

[ https://issues.apache.org/jira/browse/CASSANDRA-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070055#comment-17070055 ] Scott Carey edited comment on CASSANDRA-12662 at 3/28/20, 10:25 PM: --

[jira] [Commented] (CASSANDRA-12662) OOM when using SASI index

[ https://issues.apache.org/jira/browse/CASSANDRA-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070055#comment-17070055 ] Scott Carey commented on CASSANDRA-12662: - I have had a similar issue, with

[jira] [Created] (CASSANDRA-14533) Frozen Collections should allow TTL and WRITETIME access

Scott Carey created CASSANDRA-14533: --- Summary: Frozen Collections should allow TTL and WRITETIME access Key: CASSANDRA-14533 URL: https://issues.apache.org/jira/browse/CASSANDRA-14533 Project: Cassan