[jira] [Commented] (CASSANDRA-6092) Leveled Compaction after ALTER TABLE creates pending but does not actually begin
[
https://issues.apache.org/jira/browse/CASSANDRA-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367809#comment-14367809
]
Philip Thompson commented on CASSANDRA-6092:
Is this behavior still an issue, and if so, do we still want to apply the
original patch?
> Leveled Compaction after ALTER TABLE creates pending but does not actually
> begin
>
>
> Key: CASSANDRA-6092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6092
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 1.2.10
> Oracle Java 1.7.0_u40
> RHEL6.4
>Reporter: Karl Mueller
>Priority: Minor
> Attachments: 6092.txt
>
>
> Running Cassandra 1.2.10. N=5, RF=3
> On this Column Family (ProductGenomeDev/Node), it's been major compacted into
> a single, large sstable.
> There's no activity on the table at the time of the ALTER command. I changed
> it to Leveled Compaction with the command below.
> cqlsh:ProductGenomeDev> alter table "Node" with compaction = { 'class' :
> 'LeveledCompactionStrategy', 'sstable_size_in_mb' : 160 };
> Log entries confirm the change happened.
> [...]column_metadata={},compactionStrategyClass=class
> org.apache.cassandra.db.compaction.LeveledCompactionStrategy,compactionStrategyOptions={sstable_size_in_mb=160}
> [...]
> nodetool compactionstats shows pending compactions, but there's no activity:
> pending tasks: 750
> 12 hours later, nothing has still happened, same number pending. The
> expectation would be that compactions would proceed immediately to convert
> everything to Leveled Compaction as soon as the ALTER TABLE command goes.
> I try a simple write into the CF, and then flush the nodes. This kicks off
> compaction on 3 nodes. (RF=3)
> cqlsh:ProductGenomeDev> insert into "Node" (key, column1, value) values
> ('test123', 'test123', 'test123');
> cqlsh:ProductGenomeDev> select * from "Node" where key = 'test123';
> key | column1 | value
> -+-+-
> test123 | test123 | test123
> cqlsh:ProductGenomeDev> delete from "Node" where key = 'test123';
> After a flush on every node, now I see:
> [cassandra@dev-cass00 ~]$ cas exec nt compactionstats
> *** dev-cass00 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass04 (0) ***
> pending tasks: 752
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 341881
> 643290447928 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass01 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass02 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3374975141
> 642764512481 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass03 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3591320948
> 643017643573 bytes 0.56%
> Active compaction remaining time :n/a
> After inserting and deleting more columns, enough that all nodes have new
> data, and flushing, now compactions are proceeding on all nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-6092) Leveled Compaction after ALTER TABLE creates pending but does not actually begin
[
https://issues.apache.org/jira/browse/CASSANDRA-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793717#comment-13793717
]
Yuki Morishita commented on CASSANDRA-6092:
---
So we are not adding functionality to break up huge single SSTable when
switching to LCS, right?
(I'm not a huge fan of it since it adds complexity to picking LCS candidates
imho.)
> Leveled Compaction after ALTER TABLE creates pending but does not actually
> begin
>
>
> Key: CASSANDRA-6092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6092
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 1.2.10
> Oracle Java 1.7.0_u40
> RHEL6.4
>Reporter: Karl Mueller
>Assignee: Jonathan Ellis
> Fix For: 1.2.11
>
> Attachments: 6092.txt
>
>
> Running Cassandra 1.2.10. N=5, RF=3
> On this Column Family (ProductGenomeDev/Node), it's been major compacted into
> a single, large sstable.
> There's no activity on the table at the time of the ALTER command. I changed
> it to Leveled Compaction with the command below.
> cqlsh:ProductGenomeDev> alter table "Node" with compaction = { 'class' :
> 'LeveledCompactionStrategy', 'sstable_size_in_mb' : 160 };
> Log entries confirm the change happened.
> [...]column_metadata={},compactionStrategyClass=class
> org.apache.cassandra.db.compaction.LeveledCompactionStrategy,compactionStrategyOptions={sstable_size_in_mb=160}
> [...]
> nodetool compactionstats shows pending compactions, but there's no activity:
> pending tasks: 750
> 12 hours later, nothing has still happened, same number pending. The
> expectation would be that compactions would proceed immediately to convert
> everything to Leveled Compaction as soon as the ALTER TABLE command goes.
> I try a simple write into the CF, and then flush the nodes. This kicks off
> compaction on 3 nodes. (RF=3)
> cqlsh:ProductGenomeDev> insert into "Node" (key, column1, value) values
> ('test123', 'test123', 'test123');
> cqlsh:ProductGenomeDev> select * from "Node" where key = 'test123';
> key | column1 | value
> -+-+-
> test123 | test123 | test123
> cqlsh:ProductGenomeDev> delete from "Node" where key = 'test123';
> After a flush on every node, now I see:
> [cassandra@dev-cass00 ~]$ cas exec nt compactionstats
> *** dev-cass00 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass04 (0) ***
> pending tasks: 752
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 341881
> 643290447928 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass01 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass02 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3374975141
> 642764512481 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass03 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3591320948
> 643017643573 bytes 0.56%
> Active compaction remaining time :n/a
> After inserting and deleting more columns, enough that all nodes have new
> data, and flushing, now compactions are proceeding on all nodes.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6092) Leveled Compaction after ALTER TABLE creates pending but does not actually begin
[
https://issues.apache.org/jira/browse/CASSANDRA-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793012#comment-13793012
]
Tomas Salfischberger commented on CASSANDRA-6092:
-
Update: The workaround to call "nodetool compact" only works when there is at
least some activity, causing there to be more than 1 sstable. I've just tested
with a cluster that was not receiving any reads nor writes. In that case
calling "nodetool compact" does not do anything, so there is no way to work
around this when there are no writes at all. Maybe it's worth adding a special
case of ignoring the tombstone ratio threshold for single sstable compaction in
the case of explicitly calling nodetool compact?
> Leveled Compaction after ALTER TABLE creates pending but does not actually
> begin
>
>
> Key: CASSANDRA-6092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6092
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 1.2.10
> Oracle Java 1.7.0_u40
> RHEL6.4
>Reporter: Karl Mueller
>Assignee: Daniel Meyer
>
> Running Cassandra 1.2.10. N=5, RF=3
> On this Column Family (ProductGenomeDev/Node), it's been major compacted into
> a single, large sstable.
> There's no activity on the table at the time of the ALTER command. I changed
> it to Leveled Compaction with the command below.
> cqlsh:ProductGenomeDev> alter table "Node" with compaction = { 'class' :
> 'LeveledCompactionStrategy', 'sstable_size_in_mb' : 160 };
> Log entries confirm the change happened.
> [...]column_metadata={},compactionStrategyClass=class
> org.apache.cassandra.db.compaction.LeveledCompactionStrategy,compactionStrategyOptions={sstable_size_in_mb=160}
> [...]
> nodetool compactionstats shows pending compactions, but there's no activity:
> pending tasks: 750
> 12 hours later, nothing has still happened, same number pending. The
> expectation would be that compactions would proceed immediately to convert
> everything to Leveled Compaction as soon as the ALTER TABLE command goes.
> I try a simple write into the CF, and then flush the nodes. This kicks off
> compaction on 3 nodes. (RF=3)
> cqlsh:ProductGenomeDev> insert into "Node" (key, column1, value) values
> ('test123', 'test123', 'test123');
> cqlsh:ProductGenomeDev> select * from "Node" where key = 'test123';
> key | column1 | value
> -+-+-
> test123 | test123 | test123
> cqlsh:ProductGenomeDev> delete from "Node" where key = 'test123';
> After a flush on every node, now I see:
> [cassandra@dev-cass00 ~]$ cas exec nt compactionstats
> *** dev-cass00 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass04 (0) ***
> pending tasks: 752
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 341881
> 643290447928 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass01 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass02 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3374975141
> 642764512481 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass03 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3591320948
> 643017643573 bytes 0.56%
> Active compaction remaining time :n/a
> After inserting and deleting more columns, enough that all nodes have new
> data, and flushing, now compactions are proceeding on all nodes.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6092) Leveled Compaction after ALTER TABLE creates pending but does not actually begin
[
https://issues.apache.org/jira/browse/CASSANDRA-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792400#comment-13792400
]
Karl Mueller commented on CASSANDRA-6092:
-
This doesn't make sense. You change a compaction strategy, it should start to
take effect. You shouldn't have to do anything else. This is a bug, plain and
simple.
For one thing, the most likely users who want to use leveled compaction are
people like me who compact nightly to get rid of old update rows. We're the
most likely ones to have a single sstable.
This is not a bizarre corner case, but basic functionality!
> Leveled Compaction after ALTER TABLE creates pending but does not actually
> begin
>
>
> Key: CASSANDRA-6092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6092
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 1.2.10
> Oracle Java 1.7.0_u40
> RHEL6.4
>Reporter: Karl Mueller
>Assignee: Daniel Meyer
>
> Running Cassandra 1.2.10. N=5, RF=3
> On this Column Family (ProductGenomeDev/Node), it's been major compacted into
> a single, large sstable.
> There's no activity on the table at the time of the ALTER command. I changed
> it to Leveled Compaction with the command below.
> cqlsh:ProductGenomeDev> alter table "Node" with compaction = { 'class' :
> 'LeveledCompactionStrategy', 'sstable_size_in_mb' : 160 };
> Log entries confirm the change happened.
> [...]column_metadata={},compactionStrategyClass=class
> org.apache.cassandra.db.compaction.LeveledCompactionStrategy,compactionStrategyOptions={sstable_size_in_mb=160}
> [...]
> nodetool compactionstats shows pending compactions, but there's no activity:
> pending tasks: 750
> 12 hours later, nothing has still happened, same number pending. The
> expectation would be that compactions would proceed immediately to convert
> everything to Leveled Compaction as soon as the ALTER TABLE command goes.
> I try a simple write into the CF, and then flush the nodes. This kicks off
> compaction on 3 nodes. (RF=3)
> cqlsh:ProductGenomeDev> insert into "Node" (key, column1, value) values
> ('test123', 'test123', 'test123');
> cqlsh:ProductGenomeDev> select * from "Node" where key = 'test123';
> key | column1 | value
> -+-+-
> test123 | test123 | test123
> cqlsh:ProductGenomeDev> delete from "Node" where key = 'test123';
> After a flush on every node, now I see:
> [cassandra@dev-cass00 ~]$ cas exec nt compactionstats
> *** dev-cass00 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass04 (0) ***
> pending tasks: 752
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 341881
> 643290447928 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass01 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass02 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3374975141
> 642764512481 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass03 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3591320948
> 643017643573 bytes 0.56%
> Active compaction remaining time :n/a
> After inserting and deleting more columns, enough that all nodes have new
> data, and flushing, now compactions are proceeding on all nodes.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6092) Leveled Compaction after ALTER TABLE creates pending but does not actually begin
[
https://issues.apache.org/jira/browse/CASSANDRA-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792376#comment-13792376
]
Jeremiah Jordan commented on CASSANDRA-6092:
Don't know if that is really worth a special case. The first time a flush
happens it should trigger compacting everything. So its only going to sit like
this while you aren't doing any inserts. And it is easy enough to work around
by calling "nodetool compact" to trigger compaction. Or even "nodetool flush"
if there is any data in the memtable.
> Leveled Compaction after ALTER TABLE creates pending but does not actually
> begin
>
>
> Key: CASSANDRA-6092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6092
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 1.2.10
> Oracle Java 1.7.0_u40
> RHEL6.4
>Reporter: Karl Mueller
>Assignee: Daniel Meyer
>
> Running Cassandra 1.2.10. N=5, RF=3
> On this Column Family (ProductGenomeDev/Node), it's been major compacted into
> a single, large sstable.
> There's no activity on the table at the time of the ALTER command. I changed
> it to Leveled Compaction with the command below.
> cqlsh:ProductGenomeDev> alter table "Node" with compaction = { 'class' :
> 'LeveledCompactionStrategy', 'sstable_size_in_mb' : 160 };
> Log entries confirm the change happened.
> [...]column_metadata={},compactionStrategyClass=class
> org.apache.cassandra.db.compaction.LeveledCompactionStrategy,compactionStrategyOptions={sstable_size_in_mb=160}
> [...]
> nodetool compactionstats shows pending compactions, but there's no activity:
> pending tasks: 750
> 12 hours later, nothing has still happened, same number pending. The
> expectation would be that compactions would proceed immediately to convert
> everything to Leveled Compaction as soon as the ALTER TABLE command goes.
> I try a simple write into the CF, and then flush the nodes. This kicks off
> compaction on 3 nodes. (RF=3)
> cqlsh:ProductGenomeDev> insert into "Node" (key, column1, value) values
> ('test123', 'test123', 'test123');
> cqlsh:ProductGenomeDev> select * from "Node" where key = 'test123';
> key | column1 | value
> -+-+-
> test123 | test123 | test123
> cqlsh:ProductGenomeDev> delete from "Node" where key = 'test123';
> After a flush on every node, now I see:
> [cassandra@dev-cass00 ~]$ cas exec nt compactionstats
> *** dev-cass00 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass04 (0) ***
> pending tasks: 752
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 341881
> 643290447928 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass01 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass02 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3374975141
> 642764512481 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass03 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3591320948
> 643017643573 bytes 0.56%
> Active compaction remaining time :n/a
> After inserting and deleting more columns, enough that all nodes have new
> data, and flushing, now compactions are proceeding on all nodes.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6092) Leveled Compaction after ALTER TABLE creates pending but does not actually begin
[
https://issues.apache.org/jira/browse/CASSANDRA-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791980#comment-13791980
]
Karl Mueller commented on CASSANDRA-6092:
-
I'll try this work-around. A lot easier than what I did by inserting, deleting,
flushing data!
> Leveled Compaction after ALTER TABLE creates pending but does not actually
> begin
>
>
> Key: CASSANDRA-6092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6092
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 1.2.10
> Oracle Java 1.7.0_u40
> RHEL6.4
>Reporter: Karl Mueller
>Assignee: Daniel Meyer
>
> Running Cassandra 1.2.10. N=5, RF=3
> On this Column Family (ProductGenomeDev/Node), it's been major compacted into
> a single, large sstable.
> There's no activity on the table at the time of the ALTER command. I changed
> it to Leveled Compaction with the command below.
> cqlsh:ProductGenomeDev> alter table "Node" with compaction = { 'class' :
> 'LeveledCompactionStrategy', 'sstable_size_in_mb' : 160 };
> Log entries confirm the change happened.
> [...]column_metadata={},compactionStrategyClass=class
> org.apache.cassandra.db.compaction.LeveledCompactionStrategy,compactionStrategyOptions={sstable_size_in_mb=160}
> [...]
> nodetool compactionstats shows pending compactions, but there's no activity:
> pending tasks: 750
> 12 hours later, nothing has still happened, same number pending. The
> expectation would be that compactions would proceed immediately to convert
> everything to Leveled Compaction as soon as the ALTER TABLE command goes.
> I try a simple write into the CF, and then flush the nodes. This kicks off
> compaction on 3 nodes. (RF=3)
> cqlsh:ProductGenomeDev> insert into "Node" (key, column1, value) values
> ('test123', 'test123', 'test123');
> cqlsh:ProductGenomeDev> select * from "Node" where key = 'test123';
> key | column1 | value
> -+-+-
> test123 | test123 | test123
> cqlsh:ProductGenomeDev> delete from "Node" where key = 'test123';
> After a flush on every node, now I see:
> [cassandra@dev-cass00 ~]$ cas exec nt compactionstats
> *** dev-cass00 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass04 (0) ***
> pending tasks: 752
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 341881
> 643290447928 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass01 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass02 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3374975141
> 642764512481 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass03 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3591320948
> 643017643573 bytes 0.56%
> Active compaction remaining time :n/a
> After inserting and deleting more columns, enough that all nodes have new
> data, and flushing, now compactions are proceeding on all nodes.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6092) Leveled Compaction after ALTER TABLE creates pending but does not actually begin
[
https://issues.apache.org/jira/browse/CASSANDRA-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791974#comment-13791974
]
Tomas Salfischberger commented on CASSANDRA-6092:
-
I have accidentally reproduced this on a test-cluster, N=3 and RF=3 with
1.2.10. The CF I was testing with started out as LCS with sstable_size of 5mb
(original default in 1.0) which created 30.000+ files. I switched it to
SizeTieredCompactionStrategy, which made it compact everything to a single
sstable.
My initial goal was to use sstablesplit on this, but then I realized I could
just try to switch back to LCS and see what it would do. This exhibited exactly
the behavior described in this issue. It created a set of pending tasks and
never tried to execute them.
Then I ran "nodetool compact" on the CF and that started the compaction process
(visible in both the logs and nodetool compactionstats). After a few hours the
compact-command returned, all pending tasks were cleared and the sstables were
nicely split in the configured sizes. Checking the json metadata for LCS shows
the files all ended up in L1.
So to summarize: 1. I've reprocuded the issue and 2. running "nodetool compact"
seems a good workaround.
> Leveled Compaction after ALTER TABLE creates pending but does not actually
> begin
>
>
> Key: CASSANDRA-6092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6092
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 1.2.10
> Oracle Java 1.7.0_u40
> RHEL6.4
>Reporter: Karl Mueller
>Assignee: Daniel Meyer
>
> Running Cassandra 1.2.10. N=5, RF=3
> On this Column Family (ProductGenomeDev/Node), it's been major compacted into
> a single, large sstable.
> There's no activity on the table at the time of the ALTER command. I changed
> it to Leveled Compaction with the command below.
> cqlsh:ProductGenomeDev> alter table "Node" with compaction = { 'class' :
> 'LeveledCompactionStrategy', 'sstable_size_in_mb' : 160 };
> Log entries confirm the change happened.
> [...]column_metadata={},compactionStrategyClass=class
> org.apache.cassandra.db.compaction.LeveledCompactionStrategy,compactionStrategyOptions={sstable_size_in_mb=160}
> [...]
> nodetool compactionstats shows pending compactions, but there's no activity:
> pending tasks: 750
> 12 hours later, nothing has still happened, same number pending. The
> expectation would be that compactions would proceed immediately to convert
> everything to Leveled Compaction as soon as the ALTER TABLE command goes.
> I try a simple write into the CF, and then flush the nodes. This kicks off
> compaction on 3 nodes. (RF=3)
> cqlsh:ProductGenomeDev> insert into "Node" (key, column1, value) values
> ('test123', 'test123', 'test123');
> cqlsh:ProductGenomeDev> select * from "Node" where key = 'test123';
> key | column1 | value
> -+-+-
> test123 | test123 | test123
> cqlsh:ProductGenomeDev> delete from "Node" where key = 'test123';
> After a flush on every node, now I see:
> [cassandra@dev-cass00 ~]$ cas exec nt compactionstats
> *** dev-cass00 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass04 (0) ***
> pending tasks: 752
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 341881
> 643290447928 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass01 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass02 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3374975141
> 642764512481 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass03 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3591320948
> 643017643573 bytes 0.56%
> Active compaction remaining time :n/a
> After inserting and deleting more columns, enough that all nodes have new
> data, and flushing, now compactions are proceeding on all nodes.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6092) Leveled Compaction after ALTER TABLE creates pending but does not actually begin
[
https://issues.apache.org/jira/browse/CASSANDRA-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779014#comment-13779014
]
Jonathan Ellis commented on CASSANDRA-6092:
---
Oh, good point.
Do you think we should add a special case for this?
> Leveled Compaction after ALTER TABLE creates pending but does not actually
> begin
>
>
> Key: CASSANDRA-6092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6092
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 1.2.10
> Oracle Java 1.7.0_u40
> RHEL6.4
>Reporter: Karl Mueller
>Assignee: Daniel Meyer
>
> Running Cassandra 1.2.10. N=5, RF=3
> On this Column Family (ProductGenomeDev/Node), it's been major compacted into
> a single, large sstable.
> There's no activity on the table at the time of the ALTER command. I changed
> it to Leveled Compaction with the command below.
> cqlsh:ProductGenomeDev> alter table "Node" with compaction = { 'class' :
> 'LeveledCompactionStrategy', 'sstable_size_in_mb' : 160 };
> Log entries confirm the change happened.
> [...]column_metadata={},compactionStrategyClass=class
> org.apache.cassandra.db.compaction.LeveledCompactionStrategy,compactionStrategyOptions={sstable_size_in_mb=160}
> [...]
> nodetool compactionstats shows pending compactions, but there's no activity:
> pending tasks: 750
> 12 hours later, nothing has still happened, same number pending. The
> expectation would be that compactions would proceed immediately to convert
> everything to Leveled Compaction as soon as the ALTER TABLE command goes.
> I try a simple write into the CF, and then flush the nodes. This kicks off
> compaction on 3 nodes. (RF=3)
> cqlsh:ProductGenomeDev> insert into "Node" (key, column1, value) values
> ('test123', 'test123', 'test123');
> cqlsh:ProductGenomeDev> select * from "Node" where key = 'test123';
> key | column1 | value
> -+-+-
> test123 | test123 | test123
> cqlsh:ProductGenomeDev> delete from "Node" where key = 'test123';
> After a flush on every node, now I see:
> [cassandra@dev-cass00 ~]$ cas exec nt compactionstats
> *** dev-cass00 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass04 (0) ***
> pending tasks: 752
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 341881
> 643290447928 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass01 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass02 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3374975141
> 642764512481 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass03 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3591320948
> 643017643573 bytes 0.56%
> Active compaction remaining time :n/a
> After inserting and deleting more columns, enough that all nodes have new
> data, and flushing, now compactions are proceeding on all nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-6092) Leveled Compaction after ALTER TABLE creates pending but does not actually begin
[
https://issues.apache.org/jira/browse/CASSANDRA-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778991#comment-13778991
]
Yuki Morishita commented on CASSANDRA-6092:
---
bq. it's been major compacted into a single, large sstable.
Single SSTable compaction only happens when tombstone ratio is above threshold.
> Leveled Compaction after ALTER TABLE creates pending but does not actually
> begin
>
>
> Key: CASSANDRA-6092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6092
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 1.2.10
> Oracle Java 1.7.0_u40
> RHEL6.4
>Reporter: Karl Mueller
>Assignee: Daniel Meyer
>
> Running Cassandra 1.2.10. N=5, RF=3
> On this Column Family (ProductGenomeDev/Node), it's been major compacted into
> a single, large sstable.
> There's no activity on the table at the time of the ALTER command. I changed
> it to Leveled Compaction with the command below.
> cqlsh:ProductGenomeDev> alter table "Node" with compaction = { 'class' :
> 'LeveledCompactionStrategy', 'sstable_size_in_mb' : 160 };
> Log entries confirm the change happened.
> [...]column_metadata={},compactionStrategyClass=class
> org.apache.cassandra.db.compaction.LeveledCompactionStrategy,compactionStrategyOptions={sstable_size_in_mb=160}
> [...]
> nodetool compactionstats shows pending compactions, but there's no activity:
> pending tasks: 750
> 12 hours later, nothing has still happened, same number pending. The
> expectation would be that compactions would proceed immediately to convert
> everything to Leveled Compaction as soon as the ALTER TABLE command goes.
> I try a simple write into the CF, and then flush the nodes. This kicks off
> compaction on 3 nodes. (RF=3)
> cqlsh:ProductGenomeDev> insert into "Node" (key, column1, value) values
> ('test123', 'test123', 'test123');
> cqlsh:ProductGenomeDev> select * from "Node" where key = 'test123';
> key | column1 | value
> -+-+-
> test123 | test123 | test123
> cqlsh:ProductGenomeDev> delete from "Node" where key = 'test123';
> After a flush on every node, now I see:
> [cassandra@dev-cass00 ~]$ cas exec nt compactionstats
> *** dev-cass00 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass04 (0) ***
> pending tasks: 752
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 341881
> 643290447928 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass01 (0) ***
> pending tasks: 750
> Active compaction remaining time :n/a
> *** dev-cass02 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3374975141
> 642764512481 bytes 0.53%
> Active compaction remaining time :n/a
> *** dev-cass03 (0) ***
> pending tasks: 751
> compaction typekeyspace column family completed
> total unit progress
>CompactionProductGenomeDevNode 3591320948
> 643017643573 bytes 0.56%
> Active compaction remaining time :n/a
> After inserting and deleting more columns, enough that all nodes have new
> data, and flushing, now compactions are proceeding on all nodes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
