[
https://issues.apache.org/jira/browse/CASSANDRA-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538528#comment-14538528
]
Ariel Weisberg commented on CASSANDRA-9235:
-------------------------------------------
[~krummas] This is the second integer overflow in 2.1.5. Kind of a painful
thing to test for in a blackbox way, but we have documented limits that are
greater than what we are apparently testing for things like sstable size. I
suppose size in bytes > Integer is something that can happen now. Size in units
(where units are multi-byte things) is probably a ways off.
My take away is that we should probably have a ticket off of 9012 to test with
all the compaction strategies and with and without compression tables and
partitions > Integer?
> Max sstable size in leveled manifest is an int, creating large sstables
> overflows this and breaks LCS
> -----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-9235
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9235
> Project: Cassandra
> Issue Type: Bug
> Components: API, Core
> Environment: CentOS 6.2 x64, Cassandra 2.1.4
> Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)
> Reporter: Sergey Maznichenko
> Assignee: Marcus Eriksson
> Fix For: 2.2 beta 1, 2.0.15, 2.1.5
>
> Attachments: 0001-9235.patch
>
>
> nodetool compactionstats
> pending tasks: -222222228
> I can see negative numbers in 'pending tasks' on all 8 nodes
> it looks like -222222228 + real number of pending tasks
> for example -222222128 for 100 real pending tasks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
