You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2015/11/19 11:15:11 UTC

[jira] [Commented] (CASSANDRA-10188) sstableloader does not use MAX_HEAP_SIZE env parameter

    [ https://issues.apache.org/jira/browse/CASSANDRA-10188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013279#comment-15013279 ] 

Robert Stupp commented on CASSANDRA-10188:
------------------------------------------

+1

Committed as 4f2337f6d04669f2032f612ff556c025c85fadb0

> sstableloader does not use MAX_HEAP_SIZE env parameter
> ------------------------------------------------------
>
>                 Key: CASSANDRA-10188
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10188
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Dan Hable
>            Assignee: Michael Shuler
>            Priority: Minor
>             Fix For: 2.1.12, 2.2.4, 3.0.1, 3.1, 3.2
>
>         Attachments: CASSANDRA-10188.txt
>
>
> Currently the sstableloader script hard codes java's max heap size parameter to 256MB. The issue was discussed in CASSANDRA-7385 and it looks like the agreed solution was to allow the value to change through parameters that were going to be introduced as part of CASSANDRA-5969. This parameter wasn't added to sstableloader, making it inconsistent with the other utilities and provides a problem loading large files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)