You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paulo Motta (JIRA)" <ji...@apache.org> on 2016/02/10 16:26:18 UTC

[jira] [Commented] (CASSANDRA-7238) Nodetool Status performance is much slower with VNodes On

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

Paulo Motta commented on CASSANDRA-7238:
----------------------------------------

Sorry, this review fall of my radar. Patch and tests look good, marking as ready to commit! Thanks!

> Nodetool Status performance is much slower with VNodes On
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-7238
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7238
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>         Environment: 1000 M1.Large Ubuntu 12.04
>            Reporter: Russell Alexander Spitzer
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 2.1.x, 2.2.x, 3.0.x, 3.x
>
>
> Nodetool status on a 1000 Node cluster without vnodes returns in several seconds. With vnodes on (256) there are OOM errors with the default XMX of 32. Adjusting the XMX to 128 allows nodetool status to complete but the execution takes roughly 10 minutes.
> Tested
> {code}
> XMX    |      Status
> 32     |    OOM
> 64     |    OOM: GC Overhead
> 128    |    Finishes in ~10 minutes
> 500    |    Finishes in ~10 minutes
> 1000   |    Finishes in ~10 minutes
> {code}



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