[
https://issues.apache.org/jira/browse/CASSANDRA-14649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586017#comment-16586017
]
Branimir Lambov commented on CASSANDRA-14649:
---------------------------------------------
CircleCI doesn't seem to like the new test but AFAICT is otherwise fine:
[2.2|https://circleci.com/gh/blambov/workflows/cassandra/tree/14649-2.2]
[3.0|https://circleci.com/gh/blambov/workflows/cassandra/tree/14649-3.0]
[3.11|https://circleci.com/gh/blambov/workflows/cassandra/tree/14649-3.11]
[trunk|https://circleci.com/gh/blambov/workflows/cassandra/tree/14649-trunk]
Should I remove the >2G test, or is there something I need to set up to be able
to run tests needing more memory?
> Index summaries fail when their size gets > 2G and use more space than
> necessary
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-14649
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14649
> Project: Cassandra
> Issue Type: Bug
> Reporter: Branimir Lambov
> Assignee: Branimir Lambov
> Priority: Major
>
> After building a summary, {{IndexSummaryBuilder}} tries to trim the memory
> writers by calling {{SafeMemoryWriter.setCapacity(capacity())}}. Instead of
> trimming, this ends up allocating at least as much extra space and failing
> the {{Buffer.position()}} call when the size is greater than
> {{Integer.MAX_VALUE}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
