cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-5562) sstablescrub should respect MAX_HEAP_SIZE
Date Mon, 13 May 2013 19:39:17 GMT


Jonathan Ellis updated CASSANDRA-5562:

          Component/s:     (was: Core)
    Affects Version/s:     (was: 1.1.11)
             Assignee: Brandon Williams
> sstablescrub should respect MAX_HEAP_SIZE
> -----------------------------------------
>                 Key: CASSANDRA-5562
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Mina Naguib
>            Assignee: Brandon Williams
>            Priority: Minor
>              Labels: MAX_HEAP_SIZE, heap, oom, sstablescrub, xmx
>         Attachments: CASSANDRA-5562-sstablescrub_max_heap_size.patch
> sstablescrub has Xmx hardcoded to 256MB.  This is not enough in my installation and causes
an OOM.
> Since it's meant to be run offline, the memory usually allocated to the daemon can be
safely given to the tool.
> Attached is a patch that makes it respect $MAX_HEAP_SIZE (with fallback to 256MB if not

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:

View raw message