[
https://issues.apache.org/jira/browse/CASSANDRA-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams resolved CASSANDRA-5466.
-----------------------------------------
Resolution: Cannot Reproduce
Resolving as cantrepro, though I suspect CASSANDRA-5677 may have solved it.
> Compaction task eats 100% CPU for a long time for tables with collection
> typed columns
> --------------------------------------------------------------------------------------
>
> Key: CASSANDRA-5466
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5466
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.4
> Environment: ubuntu 12.10, sun-6-java 1.6.0.37, Core-i7, 8GB RAM
> Reporter: Alexey Tereschenko
> Assignee: Alex Zarutin
> Attachments: CASSANDRA-5466.txt, Cassandra_JDBC_Updater.tar.gz,
> logs-system-cass-5466-output-30-threads-1386752-req-Default-LCS.log,
> logs-system-cass-5466-output-30-threads-1578752-req-LeveledCompactionStrategy.log,
>
> nodetool-compactionstats-cass-5466-output-30-threads-1386752-req-Default-LCS.log,
>
> nodetool-compactionstats-cass-5466-output-30-threads-1578752-req-LeveledCompactionStrategy.log
>
>
> For the table:
> {code:sql}
> create table test (
> user_id bigint,
> first_list list<bigint>,
> second_list list<bigint>,
> third_list list<bigint>,
> PRIMARY KEY (user_id)
> );
> {code}
> I do thousands of updates like the following:
> {code:sql}
> UPDATE test SET first_list = [1], second_list = [2], third_list = [3] WHERE
> user_id = ?;
> {code}
> In several minutes a compaction task starts running. {{nodetool
> compactionstats}} shows that remaining time is 2 seconds but in fact it can
> take hours to really complete the compaction tasks. And during that time
> Cassandra consumes 100% of CPU and slows down so significally that it gives
> connection timeout exceptions to any client code trying to establish
> connection with Cassandra. This happens only with tables with collection
> typed columns.
--
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
