cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-5562) sstablescrub should respect MAX_HEAP_SIZE
Date Tue, 14 May 2013 19:13:18 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brandon Williams reassigned CASSANDRA-5562:
-------------------------------------------

    Assignee: Mina Naguib
    
> sstablescrub should respect MAX_HEAP_SIZE
> -----------------------------------------
>
>                 Key: CASSANDRA-5562
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5562
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Mina Naguib
>            Assignee: Mina Naguib
>            Priority: Minor
>              Labels: MAX_HEAP_SIZE, heap, oom, sstablescrub, xmx
>             Fix For: 1.2.5
>
>         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
defined)

--
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

Mime
View raw message